You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2011/01/17 16:21:43 UTC
[jira] Created: (KARAF-400) Support features lifecycle
Support features lifecycle
--------------------------
Key: KARAF-400
URL: https://issues.apache.org/jira/browse/KARAF-400
Project: Karaf
Issue Type: Improvement
Reporter: Jean-Baptiste Onofré
Fix For: 2.2.0, 3.0.0
Currently, we don't really manage the lifecycles of features.
We can know if a feature is installed or not, but not if a feature is started or stopped.
As we want to be able to upgrade features (with refreshing some features part), we have to know the current features state.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (KARAF-400) Support features lifecycle
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guillaume Nodet updated KARAF-400:
----------------------------------
Fix Version/s: (was: 2.2.0)
> Support features lifecycle
> --------------------------
>
> Key: KARAF-400
> URL: https://issues.apache.org/jira/browse/KARAF-400
> Project: Karaf
> Issue Type: Improvement
> Reporter: Jean-Baptiste Onofré
> Fix For: 3.0.0
>
>
> Currently, we don't really manage the lifecycles of features.
> We can know if a feature is installed or not, but not if a feature is started or stopped.
> As we want to be able to upgrade features (with refreshing some features part), we have to know the current features state.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KARAF-400) Support features lifecycle
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré updated KARAF-400:
---------------------------------------
Component/s: karaf-features
> Support features lifecycle
> --------------------------
>
> Key: KARAF-400
> URL: https://issues.apache.org/jira/browse/KARAF-400
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-features
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Fix For: 3.1.0
>
>
> Currently, we don't really manage the lifecycles of features.
> We can know if a feature is installed or not, but not if a feature is started or stopped.
> As we want to be able to upgrade features (with refreshing some features part), we have to know the current features state.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KARAF-400) Support features lifecycle
Posted by "Christian Schneider (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13061397#comment-13061397 ]
Christian Schneider commented on KARAF-400:
-------------------------------------------
The status of a feature is a bit difficult.
For example you have feature feat1 consisting of bundle A and B
If you start the feature and then stop bundle A what is the status?
So the proposal is to add start and stop commands for features in this issue and leave the status tracking / display open for the moment.
> Support features lifecycle
> --------------------------
>
> Key: KARAF-400
> URL: https://issues.apache.org/jira/browse/KARAF-400
> Project: Karaf
> Issue Type: Improvement
> Reporter: Jean-Baptiste Onofré
> Fix For: 3.0.0
>
>
> Currently, we don't really manage the lifecycles of features.
> We can know if a feature is installed or not, but not if a feature is started or stopped.
> As we want to be able to upgrade features (with refreshing some features part), we have to know the current features state.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (KARAF-400) Support features lifecycle
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré reassigned KARAF-400:
------------------------------------------
Assignee: (was: Jean-Baptiste Onofré)
> Support features lifecycle
> --------------------------
>
> Key: KARAF-400
> URL: https://issues.apache.org/jira/browse/KARAF-400
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-feature
> Reporter: Jean-Baptiste Onofré
> Fix For: 3.1.0
>
>
> Currently, we don't really manage the lifecycles of features.
> We can know if a feature is installed or not, but not if a feature is started or stopped.
> As we want to be able to upgrade features (with refreshing some features part), we have to know the current features state.
--
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
[jira] [Updated] (KARAF-400) Support features lifecycle
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré updated KARAF-400:
---------------------------------------
Fix Version/s: (was: 3.0.0)
3.1.0
> Support features lifecycle
> --------------------------
>
> Key: KARAF-400
> URL: https://issues.apache.org/jira/browse/KARAF-400
> Project: Karaf
> Issue Type: Improvement
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Fix For: 3.1.0
>
>
> Currently, we don't really manage the lifecycles of features.
> We can know if a feature is installed or not, but not if a feature is started or stopped.
> As we want to be able to upgrade features (with refreshing some features part), we have to know the current features state.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (KARAF-400) Support features lifecycle
Posted by "Christian Schneider (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Schneider reassigned KARAF-400:
-----------------------------------------
Assignee: Christian Schneider
> Support features lifecycle
> --------------------------
>
> Key: KARAF-400
> URL: https://issues.apache.org/jira/browse/KARAF-400
> Project: Karaf
> Issue Type: Improvement
> Reporter: Jean-Baptiste Onofré
> Assignee: Christian Schneider
> Fix For: 3.0.0
>
>
> Currently, we don't really manage the lifecycles of features.
> We can know if a feature is installed or not, but not if a feature is started or stopped.
> As we want to be able to upgrade features (with refreshing some features part), we have to know the current features state.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (KARAF-400) Support features lifecycle
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré reassigned KARAF-400:
------------------------------------------
Assignee: Jean-Baptiste Onofré (was: Christian Schneider)
> Support features lifecycle
> --------------------------
>
> Key: KARAF-400
> URL: https://issues.apache.org/jira/browse/KARAF-400
> Project: Karaf
> Issue Type: Improvement
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Fix For: 3.0.0
>
>
> Currently, we don't really manage the lifecycles of features.
> We can know if a feature is installed or not, but not if a feature is started or stopped.
> As we want to be able to upgrade features (with refreshing some features part), we have to know the current features state.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira