Hi,
bundle:watch can use filtering to decide which bundle you update. It
also triggers a refresh when required (and it's the case for the
features resolver).
On Karaf 4 you can update feature as well but it's up to you to trigger it.
Regards
JB
On 08/27/2015 12:42 PM, sreeraaman wrote:
hi JB,
Thanks for the quick update. Just to elaborate,
Our application is packaged as a set of features .
For third party dependencies, there is a separate feature.
For utility bundles, there is a separate feature.
For the application, there is a separate feature.
A change in any of these features should trigger an auto update.
bundle:watch would be painful to do for all the bundles inside the above
three features. Also, if a new bundle gets added to the above feature, then
again, we will have to track it by entering the bundle:watch command from
the karaf console.
We want to avoid the end users from logging in via the karaf console and do
something.
Hope this clarifies.
best regards
Sriraman.
--
View this message in context:
http://karaf.922171.n3.nabble.com/Karaf-Feature-autoupdate-tp4042069p4042092.html
Sent from the Karaf - User mailing list archive at Nabble.com.
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
