Hi Ok, according to an off-line discussion, this is really related to the question of how to make sure Sling starts in the correct runmode after having migrated the JCR repository from, say, Jackrabbit 2 to Oak.
First I think, the migration of the persistence is an explicit and different step from the upgrade of the Sling application (keeping the persistence). So, I think to migrate the persistence, a special tool is needed in any case. I thus think, that this standalone tool changing the persistence should be extended to go into the runmode persistence file and update the respective flag. Such that from a POV of Sling, the persistence is just there as expected. WDYT ? Regards Felix > Am 08.01.2015 um 10:51 schrieb Bertrand Delacretaz <bdelacre...@apache.org>: > > Hi, > > On Thursday, January 8, 2015, Carsten Ziegeler <cziege...@apache.org> wrote: > >> ...The stickyness of the options is, >> there for a good reason as usually switching is not working. If we now >> provide an easy way to do exactly that, people will use it and run into >> trouble.... > > Ok, I agree that this shouldn't be too easy but creating a separate tool as > you suggest won't work for my use case. I need to do this in automated > testing and locating and running external tools is a pain in that context. >> >> > How about using a framework property such as > sling.remove.runmodes=foo,someOtherRunmode ? > This clearly exposes what's happening and we can log a warning to expose > the potential issues. > > If we don't implement something like this people will just delete the > sling.options.file which is worse IMO. > > -Bertrand
