Hi,
the tooling we have (launchpad, Sling's OSGi installer) both don't support multiple versions of a bundle. You can workaround the launchpad restriction by using a different artifact or group id, this will include the bundle in the launchpad. However, the OSGi installer always installs only the highest version of a bundle - you can workaround this by using different symbolic names. Or in other words, you would need to repackage one of the bundles and deploy it under different maven coordinates into your repository. We received a lot of feedback over the past years and people always stumbled across these restrictions, so maybe it would make sense to support bundles with different major versions in our tooling. Carsten 2014-02-28 8:57 GMT+01:00 Rupert Westenthaler <[email protected]>: > Hi all, > > I cam around a problem I am not sure how to solve. Maybe someone can > here knows an workaround. > > The ServiceMix Bundle for JDOM2 [1] imports packages provides by the > ServiceMix Bundle for JDOM 1.1 [2]. So to use JDOM I would need to > have the bundles of both versions included in my Launcher. > > However the Maven Launchpad Plugin does not allow to BundleLists to > include different versions for the same Bundle as clearly stated by > [3]. > > Is there any possibility to tell the Launchpad Plugin to include both > JDOM bundles? > > best > Rupert > > > [1] > http://search.maven.org/#artifactdetails|org.apache.servicemix.bundles|org.apache.servicemix.bundles.jdom|2.0.2_1|bundle > [2] > http://search.maven.org/#artifactdetails|org.apache.servicemix.bundles|org.apache.servicemix.bundles.jdom|1.1.2_1|bundle > ] > [3] > > -- > | Rupert Westenthaler [email protected] > | Bodenlehenstraße 11 ++43-699-11108907 > | A-5500 Bischofshofen > -- Carsten Ziegeler [email protected]
