Community
Participate
Working Groups
i20050308 Should support running on a read-only file system. The configuration would have to be primed beforehand, because no bundles could be installed afterwards. This is related to eliminating any location-specific paths from the metadata stored at the configuration location (bug 72851).
Some support for this has been released.
At the framework/adaptor/runtime registry level, things are working fine (we start/ryun/shut down without ever trying to write anything). Don't know what else we want to do for 3.1 here. Suggestions?
Created attachment 19666 [details] patch for org.eclipse.osgi Further changes: the following operations won't do any work when in read-only mode: - AbstractFramework#compactStorage() - DefaultAdaptor#save() - EclipseAdaptor#save() Tom, can you review?
The changes proposed are less comprehensive and overlap the ones proposed in bug 64479. Tom, I suggest we address that one first.
Comment on attachment 19666 [details] patch for org.eclipse.osgi Marking patch as obsolete. Will attach a new patch to bug 64479.
I ended up releasing the changes described in comment 3. Will update the patch for bug 64479 to not include these changes.