On Friday 19 June 2015 17:37:43 Carsten Ziegeler wrote: > Am 19.06.15 um 17:06 schrieb Bertrand Delacretaz: [...] > >> ...10. Support of the launchpad api startup mode (install, update, > >> restart)...> > > We might need to refactor some code out of the launchpad to reuse it > > but that sounds useful. I would add an option to fail in all modes > > except INSTALL if one wants to enforce immutable Sling instances. > > Ok > > > A few more comments: > > > > Do you think we still need the launchpad's "incremental startup" that > > raises start levels sequentially with a pause between each? Or was > > that a workaround for some bugs that are gone today? > > I think we still need them - otherwise you end up at the final start > level but content packages are not installed. With pure Sling and no > content packages I guess the incremental startup is not needed.
Launchpad Karaf doesn't use startlevels (though supported by Karaf's features) and Sling works fine here. > I once started to move this stuff into a separate module but failed to > implement some detail; in retrospect I think I did a mistake while > implementing it. So it should be possible to move this to a bundle. > But maybe with crankstart we can do this more intelligent as I assume > crankstart is in full control of the startup/installation? Can we create a Lauchpad Startup bundle implementing the Lauchpad API which can be used by all launchers (and dropping the naive implementation in org.apache.sling.launchpad.karaf - which is also used in Bertrand's and Artyom's Sling Devops Experiments by Crankstart)? Does Crankstart support the startup modes install/restart/update at all? [...] > > Carsten Regards, O.
