Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
1.7.1
-
None
Description
For example, uk feature has the following definition:
<feature name='jclouds-rackspace-cloudblockstorage-uk' description='Racksapce Cloud Block Storage UK' version='${project.version}' resolver='(obr)'> <feature version='${project.version}'>jclouds-api-openstack-cinder</feature> <feature version='${project.version}'>jclouds-api-rackspace-cloudidentity</feature> <bundle>mvn:org.apache.jclouds.provider/rackspace-cloudblockstorage-uk/${jclouds.version}</bundle> </feature>
and jclouds-api-rackspace-cloudidentity:
<feature name="jclouds-api-rackspace-cloudidentity" description="Rackspace Cloud Identity API" version="${project.version}" resolver="(obr)"> <feature version='${project.version}'>jclouds-compute</feature> <feature version='${project.version}'>jclouds-api-openstack-keystone</feature> <bundle dependency='true'>mvn:org.apache.jclouds.api/rackspace-cloudidentity/${jclouds.version}</bundle> </feature>
However, with current Karaf there's no way the bundle "mvn:org.apache.jclouds.api/rackspace-cloudidentity/${jclouds.version}" will get installed. Bundles with
{dependency="true"}are taken into account only during resolution of other bundles from the same feature - not of the upper feature which uses other features. In other words - <bundle dependency="true" /> doesn't bubble up.