[
https://issues.apache.org/jira/browse/KARAF-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294251#comment-13294251
]
Christian Schneider commented on KARAF-399:
-------------------------------------------
I have an idea how to implement this. As features are grouped into feature repo
files I think it only makes sense to upgrade these.
So a console session could look like this:
# Initial installation
>feature:repo-add camel 2.9.0
>feature:install camel-core camel-jms
# Variant 1 : Upgrade command
>feature:repo-upgrade camel-2.9.0 2.9.1
# Variant 2: Add command with option to upgrade exisiting
>feature:repo-add -u camel 2.9.1
Both variants would do the following:
1. Determine which features are installed from the feature repo
2. Uninstall these features
3. Remove the old repo url
4. Add the new repo url
5. Install the features that were started and report on name changes / errors
> Support features upgrade
> ------------------------
>
> Key: KARAF-399
> URL: https://issues.apache.org/jira/browse/KARAF-399
> Project: Karaf
> Issue Type: Improvement
> Reporter: Jean-Baptiste Onofré
> Fix For: 3.1.0
>
>
> Currently, updating a feature means uninstall/install.
> It's not efficient as the bundle caches are lost, etc.
> I wonder how to manage the feature upgrade.
> For instance, if I have:
> <feature name="A" version="1.0">
> <bundle>A/1.0</bundle>
> <bundle>A/1.1</bundle>
> </feature>
> and
> <feature name="A" version="2.0">
> <bundle>A/2.0</bundle>
> <bundle>A/2.1</bundle>
> </feature>
> how can I know which bundle is the update of the other ?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
