karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Grzegorz Grzybek (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KARAF-2764) Use transitive bundle dependencies during feature installation
Date Fri, 28 Feb 2014 13:07:19 GMT

    [ https://issues.apache.org/jira/browse/KARAF-2764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13915755#comment-13915755
] 

Grzegorz Grzybek commented on KARAF-2764:
-----------------------------------------

But when I think again, I'm pretty sure that the feature
{code:xml}
    <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>
{code}
is broken, because when someone installs it, the bundle {{mvn:org.apache.jclouds.api/rackspace-cloudidentity/1.6.2-incubating}}
*won't* be installed. So I think it's better to correct the feature. I think that feature
with *all* bundles using {{dependency="true"}} are just incorrect...

> Use transitive bundle dependencies during feature installation
> --------------------------------------------------------------
>
>                 Key: KARAF-2764
>                 URL: https://issues.apache.org/jira/browse/KARAF-2764
>             Project: Karaf
>          Issue Type: Improvement
>          Components: karaf-feature
>    Affects Versions: 3.0.0
>            Reporter: Grzegorz Grzybek
>
> I have such case:
> feature one:
> {code:xml}
>     <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>
> {code}
> which depends on feature two:
> {code:xml}
>     <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>
> {code}
> 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...



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message