You are viewing a plain text version of this content. The canonical link for it is here.

Posted to user@karaf.apache.org by Nick Baker <nb...@pentaho.com> on 2016/10/03 16:49:29 UTC

Behavior of feature dependencies in 3.0.x

Hey All,


We're seeing something strange where a feature has a dependency on another and has a bundle which counts on that other feature being available. However, we're seeing that bundle fail on package imports from this other feature's bundles. It almost seems like this dependent feature isn't being installed fully before this bundle starts.


<feature name="a">

 <bundle>x</bundle>

</feature>


<feature name="b">

  <feature>a</feature>

  <bundle>y</bundle> <- depends-on 'x'

</feature>


If I manually feature:install "a" before "b" the "y" bundle is fine. However, if feature "a" isn't installed before-hand it fails.


I know that the 4.x codeline has a prerequisite=true flag. What's the significance of this? Would it help in this scenario?


Thanks,

Nick

Re: Behavior of feature dependencies in 3.0.x

Posted by Nick Baker <nb...@pentaho.com>.

Thanks JB,


Unfortunately, I cannot share the xml. The names definitely match. I'll try to troll through the debug output. This is a large feature with 8 dependent features and 20 bundles. No other features should be declaring this bundle, but I'll make sure that's the case. That's about the only scenario I can think of.


-Nick

________________________________
From: Jean-Baptiste Onofré <jb...@nanthrax.net>
Sent: Monday, October 3, 2016 1:35:53 PM
To: user@karaf.apache.org
Subject: Re: Behavior of feature dependencies in 3.0.x

Hi Nick,

I confirm that feature:install b should install a (by transitivity).

Can you share your actually features XML ? Are you sure the feature
names match ?

Regards
JB

On 10/03/2016 06:49 PM, Nick Baker wrote:
> Hey All,
>
>
> We're seeing something strange where a feature has a dependency on
> another and has a bundle which counts on that other feature being
> available. However, we're seeing that bundle fail on package imports
> from this other feature's bundles. It almost seems like this dependent
> feature isn't being installed fully before this bundle starts.
>
>
> <feature name="a">
>
>  <bundle>x</bundle>
>
> </feature>
>
>
> <feature name="b">
>
>   <feature>a</feature>
>
>   <bundle>y</bundle> <- depends-on 'x'
>
> </feature>
>
>
> If I manually feature:install "a" before "b" the "y" bundle is fine.
> However, if feature "a" isn't installed before-hand it fails.
>
>
> I know that the 4.x codeline has a prerequisite=true flag. What's the
> significance of this? Would it help in this scenario?
>
>
> Thanks,
>
> Nick
>

--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: Behavior of feature dependencies in 3.0.x

Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.

Hi Nick,

I confirm that feature:install b should install a (by transitivity).

Can you share your actually features XML ? Are you sure the feature 
names match ?

Regards
JB

On 10/03/2016 06:49 PM, Nick Baker wrote:
> Hey All,
>
>
> We're seeing something strange where a feature has a dependency on
> another and has a bundle which counts on that other feature being
> available. However, we're seeing that bundle fail on package imports
> from this other feature's bundles. It almost seems like this dependent
> feature isn't being installed fully before this bundle starts.
>
>
> <feature name="a">
>
>  <bundle>x</bundle>
>
> </feature>
>
>
> <feature name="b">
>
>   <feature>a</feature>
>
>   <bundle>y</bundle> <- depends-on 'x'
>
> </feature>
>
>
> If I manually feature:install "a" before "b" the "y" bundle is fine.
> However, if feature "a" isn't installed before-hand it fails.
>
>
> I know that the 4.x codeline has a prerequisite=true flag. What's the
> significance of this? Would it help in this scenario?
>
>
> Thanks,
>
> Nick
>

-- 
Jean-Baptiste Onofr
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com