OK, if the two bundles provide the same capabilities, it's normal: the resolver detects that the first bundle provides the caps, so it doesn't install the second one.
If you really want to install both, you can flag using prerequisite feature. Regards JB On 01/29/2018 08:15 PM, Seth Leger wrote: > On 1/29/18 12:49 PM, Jean-Baptiste Onofré wrote: >> If you try to install the bundle by hand using: >> >> bundle:install -s mvn:hello/world/1.0/jar/special >> >> does it work ? > > Yes. And if I put the bundle in the feature like this (without the other > artifact with the same groupId/artifactId/version): > > <feature name="hello" version="1.0"> > <bundle>mvn:hello/world/1.0/jar/special</bundle> > </feature> > > that works as expected as well. > >> I'm surprised as we use such kind of URL in features, like in Camel for >> instance. > > I don't see any other features in Karaf's standard features, Karaf's > Spring features, or Camel's features that have two bundles with > identical groupId/artifactId/version inside the same feature. The > closest is the 'camel-kubernetes' which has several bundles with > classifiers but they all have unique artifactIds: > > https://github.com/apache/camel/blob/camel-2.20.2/platforms/karaf/features/src/main/resources/features.xml#L1306 > > That's why I think it's a feature resolver issue and not an Aether issue. > > Seth Leger > The OpenNMS Group > -- Jean-Baptiste Onofré [email protected] http://blog.nanthrax.net Talend - http://www.talend.com
