Thanks Bertrand, Yeap, agreed with you this is the easiest way. In fact, has been my first try. Although, IMHO Sling should let users add bundles on startup without any code or additonal maven projects.
WDYT? BR, Juanjo. On Tue, Jul 29, 2008 at 12:27 PM, Bertrand Delacretaz < [EMAIL PROTECTED]> wrote: > Hi, > > On Tue, Jul 29, 2008 at 12:22 PM, Juanjo Vázquez <[EMAIL PROTECTED]> > wrote: > > ...* Launch the platform running a launchpad webapp instance. > > * Preserve the genuine Sling launchpad webapp without modifications > (except > > improvements, of course). > > * Include the additional bundles on startup. > > * Not include specific sling bundles on startup (i.e. include > > org.apache.sling.jcr.jackrabbit.client instead of > > org.apache.sling.jcr.jackrabbit.server). > > * Use the local maven repository as OBR.... > > The easiest by far seems to create your own pom.xml based on the > launchpad/webapp pom, and add/remove bundle dependencies as needed to > create a custom webapp with the bundles that you need. > > You won't lose anything, as the launchpad webapp has no specific code > (apart from the integration tests, but we're planning to move those to > their own test-only module), it's just an assembly of bundles. The > actual launcher code is in launchpad/base. > > HTH, > -Bertrand >
