Maybe the issue is with what we're trying to do. We have a fragment host in the foo feature (following your example). When installing feature A or B, we need to restart that fragment host to see the new fragment. I don't know if this is the correct way to do it, perhaps it is not.
<feature name="A" version="1.0"> <feature>foo</feature> <bundle fragment A> <bundle existing fragment host in feature foo/> </feature> <feature name="B" version="1.0"> <feature>foo</feature> <bundle fragment B> <bundle existing fragment host in feature foo/> </feature> On Aug 14, 2013, at 5:21 PM, Jean-Baptiste Onofré wrote: > Hi Marcos, > > if the feature is already installed, nothing is performed by Karaf. > > Let me take an example. I have the following features: > > <feature name="A" version="1.0"> > <feature>foo</feature> > </feature> > <feature name="B" version="1.0"> > <feature>foo</feature> > </feature> > > you install feature A, so it will install foo "first". > Now you install feature B, Karaf will check that foo is installed: > - if it is (which is actually the case), it won't do anything on foo (and its > bundles) > - if it is not, it will install foo > > Regards > JB > > On 08/14/2013 08:55 PM, Marcos Mendez wrote: >> so we have like 5 features, they all use the same dependent feature >> which has the common things. what happens when a dependent feature is >> installed? are all the bundles restarted? any way to control that? >> >> <feature name="jbi"> >> <feature>nmr</feature> >> ... >> </feature> >> >> >> >> - Marcos >> > > -- > Jean-Baptiste Onofré > [email protected] > http://blog.nanthrax.net > Talend - http://www.talend.com
