Hello
I have such case:
feature one:
<feature name='jclouds-rackspace-cloudblockstorage-us' resolver='(obr)'>
<feature
version='1.6.2-incubating'>jclouds-api-openstack-cinder</feature>
<feature
version='1.6.2-incubating'>jclouds-api-rackspace-cloudidentity</feature>
<bundle>mvn:org.apache.jclouds.provider/rackspace-cloudblockstorage-us/1.6.2-incubating</bundle>
</feature>
which depends on feature two:
<feature name="jclouds-api-rackspace-cloudidentity"
description="Rackspace Cloud Identity API" version="1.6.2-incubating"
resolver="(obr)">
<feature version='1.6.2-incubating'>jclouds-compute</feature>
<feature
version='1.6.2-incubating'>jclouds-api-openstack-keystone</feature>
<bundle
dependency='true'>mvn:org.apache.jclouds.api/rackspace-cloudidentity/1.6.2-incubating</bundle>
</feature>
the problem is that when I install feature one, then:
- when it comes to installing "jclouds-api-rackspace-cloudidentity",
bundle "rackspace-cloudidentity" isn't installed because the feature has
@resolver set and the bundle is dependency="true"
- when it returns to installing "jclouds-rackspace-cloudblockstorage-us",
the feature isn't correctly resolved because it's bundle
"rackspace-cloudblockstorage-us" requires (by package) bundle
"rackspace-cloudidentity"
I think that the dependency="true" bundles should be available "up the
chain", so the bundles from "upper features" are correctly resolved.
This should be easy to propagate these dependencies... Any problems? I
could provide a patch.
regards
Grzegorz Grzybek
