Because launchpad:run and launchpad:start actually run Launchpad (using org.apache.sling.launchpad.base.impl.Sling). It also implement a custom ResourceProvider to load bundles directly from the local Maven repository.
In the same way that Cargo depends upon Jetty, Launchpad depends upon Launchpad Base. Justin On 4/16/10 10:06 AM, Carsten Ziegeler wrote: > I haven't yet looked at the launchpad plugin, so I'm just curious :) Why > does it depend on launchpad base? > > Regards > Carsten > > Justin Edelson wrote >> m-l-p has a dependency upon Launchpad Base 2.1.1-SNAPSHOT (which I think >> is really going to be 2.2.0). So these issues either need to be resolved >> or moved to 2.3.0: >> SLING-1273 - Fragile timestamp comparsion >> SLING-1481 - JRE package versions are wrong >> >> Bertrand/Felix - can you take a look at these? >> >> I still think m-l-p could handle in-situ integration testing better, but >> I'm happy to postpone that until the next version. >> >> Justin >> >> >> On 4/16/10 6:13 AM, Bertrand Delacretaz wrote: >>> Hi, >>> >>> Thanks Justin for the latest enhancements, the integration tests start >>> much faster than with cargo, way to go! >>> >>> I have started using the plugin in FISE [1] to create a simple OSGi >>> launcher [2], could we release a first version of the plugin soon? >>> >>> Or are there outstanding issues before we do that? >>> >>> -Bertrand >>> >>> [1] http://wiki.iks-project.eu/index.php/FISE >>> [2] >>> https://iks-project.googlecode.com/svn/sandbox/fise/trunk/launchers/sling >> >> > >
