This looks promising!!. So to confirm - I need to package file installer bundle explicitly at boot level. Or I just need to pass on the directory path via system property as Bertrand suggested
- When the installer merges the two list what constitutes as a latest version. Does it compares the timestamp (as both are snapshots) Chetan Mehrotra On Mon, Aug 20, 2012 at 2:18 PM, Carsten Ziegeler <[email protected]>wrote: > Hi, > > if you're using the Sling launchpad, then all the bundles are > installed by launchpad and not the OSGi installer. > We(=Adobe)'re using this configuration for the launchpad plugin instead: > <bundlesDirectory>install</bundlesDirectory> > <bootDirectory>bundles</bootDirectory> > Now only bundles marked as boot level bundles are installed by > launchpad, everything else is installed by the OSGi installer. Of > course this requires the OSGi installer and some other bundles to be > in the boot level. If you now put the file installer bundle there as > well and point it to a directory like Bertrand suggested, the OSGi > installer will get two bundles lists, one from the launchpad and one > from the file installer, merges it and installs the latest versions. > > Carsten > > 2012/8/20 Chetan Mehrotra <[email protected]>: > > Hi Bertrand, > > > > In current setup the bundles I am working are related to Oak and I need > to > > start the system from a clean state to validate some changes. So the > > updated bundles has to be picked up at the first launch itself. > > > > The method you suggest works fine for already running system or restarts > > but for fresh install I need a way to update the existing bundle present > in > > the standalone jar/resources/install folder. > > > > Chetan Mehrotra > > > > > > On Mon, Aug 20, 2012 at 1:40 PM, Bertrand Delacretaz < > [email protected] > >> wrote: > > > >> Hi Chetan, > >> > >> On Mon, Aug 20, 2012 at 7:31 AM, Chetan Mehrotra > >> <[email protected]> wrote: > >> ... > >> > 4. Update certain bundles in resources/install folder based on #2. For > >> this > >> > install them in Maven first > >> > 5. Clean existing sling home directory > >> > 6. Repackage Sling standalone so that updated bundle from #4 gets > picked > >> up... > >> > >> Can't you just copy your new/modified bundles to an install folder on > >> the filesystem, that's picked up by the file installer? > >> > >> You can specify the name of that folder with > >> -Dsling.fileinstall.dir=/path-to-that-folder on the JVM command line. > >> > >> You could also install them directly via the OSGi console or the > >> maven-sling-plugin. > >> > >> -Bertrand > >> > > > > -- > Carsten Ziegeler > [email protected] >
