> On 4/21/10 11:14 AM, Vidar Ramdal wrote: >> [...] >> Also, the values of the sling.properties is overwritten on each >> startup, by values from the launchpad base bundle. Is there an easy >> way to avoid that, without hacking launchpad base?
On Wed, Apr 21, 2010 at 5:27 PM, Justin Edelson <[email protected]> wrote: > This shouldn't be the case. What happens is that: > 1) an empty properties map is created > 2) the default properties are loaded (from the base bundle) > 3) anything in ${sling.home}/sling.properties is overlaid on the > properties map > 4) if system properties aren't be excluded, they're overlaid on the > properties map > 5) the properties map is written to ${sling.home}/sling.properties > > then the actual properties map used by Sling is created by resolving any > variable substitution in the properties map. > > (see http://bit.ly/8XmHpT) > > In other words, you can manually edit ${sling.home}/sling.properties at > any time and the updates will be seen the next time Sling starts. Ah, I was running the 2.0.4-incubator version of launchpad.base. When updating to the current 2.0.5 snapshot, the sling.properties file is no longer reverted (but rewritten with the desired properties). Thanks for your help! -- Vidar S. Ramdal <[email protected]> - http://www.idium.no Sommerrogata 13-15, N-0255 Oslo, Norway + 47 22 00 84 00 / +47 21 531941, ext 2070
