Since we've upgrade our project (Cytoscape) to Karaf 3.0.2, we've discovered that Karaf is apparently writing to its own etc/config.properties the first time a new installation starts up. If the user happens to not have write permission to this file, Karaf will terminate with an error like the following:
C:\Program Files\Cytoscape_v3.3.0-SNAPSHOT\framework\etc\config.properties (Access is denied) This presents a problem on many end-user systems - if a user doesn't have write permission to the install directory, it is impossible to run after the initial install. We have noticed that it does seem to work after running it as administrator once - apparently it only needs to write the file on the first startup. Though that may be a workaround, this still creates a very undesirable situation for the end user. Is there a way to disable writing to the config.properties, or at least allow it to fail quietly rather than terminating? It is a bit odd to see Karaf rewriting its own config files - not sure why this is being done in Karaf 3.... -- View this message in context: http://karaf.922171.n3.nabble.com/Karaf-3-0-2-tries-to-write-to-etc-config-properties-terminates-on-failure-tp4037973.html Sent from the Karaf - User mailing list archive at Nabble.com.
