geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dain Sundstrom (JIRA)" <...@geronimo.apache.org>
Subject [jira] Closed: (GERONIMO-1227) please re-allow read-only repositories
Date Sat, 03 Dec 2005 03:42:32 GMT
     [ http://issues.apache.org/jira/browse/GERONIMO-1227?page=all ]
     
Dain Sundstrom closed GERONIMO-1227:
------------------------------------

    Fix Version: 1.0
     Resolution: Fixed

Sending        trunk/modules/system/src/java/org/apache/geronimo/system/repository/FileSystemRepository.java
Transmitting file data .
Committed revision 351882.


> please re-allow read-only repositories
> --------------------------------------
>
>          Key: GERONIMO-1227
>          URL: http://issues.apache.org/jira/browse/GERONIMO-1227
>      Project: Geronimo
>         Type: Wish
>   Components: core
>     Versions: Wish List
>  Environment: fedora core 2
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_06-b03)
> Geronimo source At revision 348532.
>     Reporter: toby cabot
>     Assignee: Dain Sundstrom
>     Priority: Minor
>      Fix For: 1.0
>  Attachments: readonly-repo-patch.txt
>
> In our application we build Geronimo and deploy our app on a read/write filesystem but
run it on a read-only filesystem.  This used to work, but I upgraded our Geronimo recently
and found that it checks if the repo is writeable and bails out if it isn't.  I disabled that
check and then Geronimo runs fine on a read-only filesystem (after hacking various xml files
to put logs, etc on a read/write partition).
> Please consider removing the read/write repository check - I'll attach a patch that does
this.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message