So what is the best practice for re-installing features?

Some of us are using feature:uninstall, others say they have problems with
it and use bundle:uninstall.

Also, is it considered best practice to embed features and bundles in the
same feature.xml?  thx.


jbonofre wrote
> Yes especially with different versions of the features.
> 
> 
> Sent from my Samsung Galaxy smartphone.
> 
> 
> -------- Original message --------
> From: asookazian2 <

> asookazian@

> > 
> Date:03/12/2014  22:30  (GMT+01:00) 
> To: 

> [email protected]

>  
> Cc:  
> Subject: Re: Karaf skipping feature install 
> 
> This envmt is using only one karaf.
> 
> I was able to reproduce this behavior with a new Karaf install and latest
> of
> our software. 
> 
> However, it behaved normally on the 1st install attempt (i.e. component1
> and
> component2 were both installed and "active").  However, on the 2nd install
> attempt, the behavior reproduced.  Maybe it's possible I am not
> uninstalling
> both features using "feature:uninstall foo" before the re-install and that
> is causing this problem/behavior?
> 
> 
> jbonofre wrote
>> Do you have the obr feature installed on one Karaf ?
>> 
>> Regards
>> JB
>> 
>> On 12/03/2014 09:25 PM, asookazian2 wrote:
>>> We have a feature install as follows:
>>>
>>> 
>> 
> <feature name="myFeature" version="1.0.0-SNAPSHOT" resolver="(obr)"
>>
>>
>>  start-level="90" description="description">
>>>
>>>          
>> 
> <feature version="1.0.0-SNAPSHOT">
>> feature1
>> 
> </feature>
>>>          
>> 
> <feature version="1.0.0-SNAPSHOT">
>> feature2
>> 
> </feature>
>>>
>>>          
>> 
> <bundle>
>> mvn:com.foo.bar/component1/1.0.0-SNAPSHOT
>> 
> </bundle>
>>>      
>> 
> </feature>
>>>
>>> 
>> 
> <feature name="feature2" version="1.0.0-SNAPSHOT" resolver="(obr)"
>>
>>
>>  start-level="90" description="description">
>>>
>>>          
>> 
> <feature version="1.0.0-SNAPSHOT">
>> feature1
>> 
> </feature>
>>>
>>>          
>> 
> <bundle>
>> mvn:com.foo.bar/component2/1.0.0-SNAPSHOT
>> 
> </bundle>
>>>      
>> 
> </feature>
>>>
>>> In a particular Karaf 3.0.2 server (with older versions of our
>>> software),
>>> component1 is being installed successfully but component2 is not.
>>>
>>> In a different Karaf 3.0.2 server (with latest versions of our
>>> software),
>>> component1 and component2 is being installed successfully.
>>>
>>> In the former case, I did not see any exceptions in the karaf log so it
>>> seems as if karaf is skipping the compononent2 install.  I verified that
>>> the
>>> JAR does indeed exist in the karaf/data/repo directory structure.
>>>
>>> Has anybody else seen this and can you provide an explanation?
>>>
>>> I verified in the Karaf cmd line console using 'list | grep -i
>>> 
>> 
> <componentName>
>> ' that the bundle was not already installed...
>>>
>>>
>>>
>>> --
>>> View this message in context:
>>> http://karaf.922171.n3.nabble.com/Karaf-skipping-feature-install-tp4036927.html
>>> Sent from the Karaf - User mailing list archive at Nabble.com.
>>>
>> 
>> -- 
>> Jean-Baptiste Onofré
> 
>> jbonofre@
> 
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
> 
> 
> 
> 
> 
> --
> View this message in context:
> http://karaf.922171.n3.nabble.com/Karaf-skipping-feature-install-tp4036927p4036931.html
> Sent from the Karaf - User mailing list archive at Nabble.com.





--
View this message in context: 
http://karaf.922171.n3.nabble.com/Karaf-skipping-feature-install-tp4036927p4036937.html
Sent from the Karaf - User mailing list archive at Nabble.com.

Reply via email to