I agree, I think the feature is broken, as the bundle should not be flagged
as dependency = true if it's supposed to be installed.
Currently, the resolvers we have always resolve bundles feature by feature,
i.e. the resolver is only used to compute the bundles needed for a given
feature, and not a
Hello
I come to conclusion, that rather the feature definition below is
incorrect, not the feature:install command:
If someone wants to install this feature *alone*, he/she would end up with
installed feature, but *not* with installed bundle:
jclouds-compute
jclouds-api-open
I think that the original intention was not to have the dependency
attribute on jclouds-api-rackspace-cloudidentity. Most probably this
was a side effect of splitting a feature into multiple features.
Of course, the problem that you describe may apply to other cases too.
So, I think that the chang
Hello
I have such case:
feature one:
jclouds-api-openstack-cinder
jclouds-api-rackspace-cloudidentity
mvn:org.apache.jclouds.provider/rackspace-cloudblockstorage-us/1.6.2-incubating
which depends on feature two:
jclouds-compute
jclouds-api-openst
