I'm not really sure how this will work, but my thinking is that the existing BootstrapInstaller should only be responsible for loading Launchpad Installer and its dependencies and then Launchpad Installer will handle everything else. So whats in resources/bundles will be handled by OSGi installer and the bundles truly used to bootstrap (log, osgi install, launchpad install, maybe one or two others, but hopefully not many) would be in something like resources/bootstrap.
Justin On Fri, Apr 15, 2011 at 1:22 AM, Carsten Ziegeler <[email protected]> wrote: > Hi, > > I just came across another feature I need: bundles under > resources/bundles are installed by Sling itself and not by the OSGi > installer. But I would use the Sling OSGi installer for installing > additional bundles and other types of artifacts. If I remember correctly > these are under resources/install. > > So, we need to distinguish between those two directories somehow. If we > follow my proposal: > > <launchpad> > <includes> > <!-- Add list artifacts here, together with exclusions -> > </includes> > <bundles> > <!-- the same as the current list.xml --> > </bundles> > <resources> > <!-- additional resources --> > </resources> > </launchpad> > > Then both sections, bundles and resources, could be dividied by start > level elements - so everything from bundles goes into resources/bundles > as is right now , and everything from resources goes into > resources/install. Both supporting start levels. > > WDYT? > > Carsten > -- > Carsten Ziegeler > [email protected] >
