Unsubscribe --
Ryan D. Lunka On Nov 26, 2012, at 5:20 AM, Carsten Ziegeler (JIRA) <[email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/SLING-2674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > ] > > Carsten Ziegeler resolved SLING-2674. > ------------------------------------- > > Resolution: Fixed > > Rewrite the implementation to use the startup handler service > >> SlingSettingsServiceImpl should detect and handle upgrades >> ---------------------------------------------------------- >> >> Key: SLING-2674 >> URL: https://issues.apache.org/jira/browse/SLING-2674 >> Project: Sling >> Issue Type: Bug >> Components: Extensions >> Affects Versions: Extensions Settings 1.2.0 >> Reporter: Bertrand Delacretaz >> Assignee: Carsten Ziegeler >> Fix For: Extensions Settings 1.2.2 >> >> >> With the recent run modes handling changes, starting a Sling instance as an >> upgrade (i.e. on an existing sling folder) might define new default run >> modes that were not present in the old instance but need to be active on the >> upgraded instance. >> In this case, the SlingSettingsServiceImpl needs to evaluate the run mode >> options against the existing run modes, in a similar way to an "install" >> startup. > > -- > This message is automatically generated by JIRA. > If you think it was sent incorrectly, please contact your JIRA administrators > For more information on JIRA, see: http://www.atlassian.com/software/jira
