On Thu, Jan 8, 2015 at 12:10 PM, Felix Meschberger wrote:
> ...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
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
Hi,
On Thursday, January 8, 2015, Carsten Ziegeler 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 to
Am 07.01.15 um 18:26 schrieb Bertrand Delacretaz:
> Hi,
>
> In some upgrade cases I need to be able to force an install runmode to
> change - for example with this:
>
> sling.run.mode.install.options = foo,bar
>
> which makes foo and bar mutually exclusive. I have an existing
> instance with a
Hi,
In some upgrade cases I need to be able to force an install runmode to
change - for example with this:
sling.run.mode.install.options = foo,bar
which makes foo and bar mutually exclusive. I have an existing
instance with a foo run mode that needs to be switched to bar at
startup.
IIUC thi
