You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Christian Schneider (JIRA)" <ji...@apache.org> on 2012/06/15 14:41:42 UTC
[jira] [Created] (KARAF-1552) Support kars that will not be auto
started
Christian Schneider created KARAF-1552:
------------------------------------------
Summary: Support kars that will not be auto started
Key: KARAF-1552
URL: https://issues.apache.org/jira/browse/KARAF-1552
Project: Karaf
Issue Type: Improvement
Reporter: Christian Schneider
Fix For: 3.0.0
While autostarting kars is a good idea for kars representing an application it is not good for kars representing a repository.
For example if you create a kar from all camel features to use camel offline then it makes no sense to start all the camel features when this kar is deployed.
So I propose to add a Manifest entry for the kar file like:
Karaf-Features-Start: false
If this entry is found then the feature repo files are installed but not started. If the entry is missing then all features are started.
--
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] [Resolved] (KARAF-1552) Support kars that will not be auto
started
Posted by "Christian Schneider (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Schneider resolved KARAF-1552.
----------------------------------------
Resolution: Fixed
Assignee: Christian Schneider
> Support kars that will not be auto started
> ------------------------------------------
>
> Key: KARAF-1552
> URL: https://issues.apache.org/jira/browse/KARAF-1552
> Project: Karaf
> Issue Type: Improvement
> Reporter: Christian Schneider
> Assignee: Christian Schneider
> Fix For: 3.0.0
>
>
> While autostarting kars is a good idea for kars representing an application it is not good for kars representing a repository.
> For example if you create a kar from all camel features to use camel offline then it makes no sense to start all the camel features when this kar is deployed.
> So I propose to add a Manifest entry for the kar file like:
> Karaf-Features-Start: false
> If this entry is found then the feature repo files are installed but not started. If the entry is missing then all features are started.
--
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] [Commented] (KARAF-1552) Support kars that will not be auto
started
Posted by "Andreas Pieber (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13396084#comment-13396084 ]
Andreas Pieber commented on KARAF-1552:
---------------------------------------
+1 from me to
> Support kars that will not be auto started
> ------------------------------------------
>
> Key: KARAF-1552
> URL: https://issues.apache.org/jira/browse/KARAF-1552
> Project: Karaf
> Issue Type: Improvement
> Reporter: Christian Schneider
> Assignee: Christian Schneider
> Fix For: 3.0.0
>
>
> While autostarting kars is a good idea for kars representing an application it is not good for kars representing a repository.
> For example if you create a kar from all camel features to use camel offline then it makes no sense to start all the camel features when this kar is deployed.
> So I propose to add a Manifest entry for the kar file like:
> Karaf-Features-Start: false
> If this entry is found then the feature repo files are installed but not started. If the entry is missing then all features are started.
--
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] [Comment Edited] (KARAF-1552) Support kars that will not be
auto started
Posted by "Andreas Pieber (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13396084#comment-13396084 ]
Andreas Pieber edited comment on KARAF-1552 at 6/18/12 6:02 PM:
----------------------------------------------------------------
+1 from me too
was (Author: pieber):
+1 from me to
> Support kars that will not be auto started
> ------------------------------------------
>
> Key: KARAF-1552
> URL: https://issues.apache.org/jira/browse/KARAF-1552
> Project: Karaf
> Issue Type: Improvement
> Reporter: Christian Schneider
> Assignee: Christian Schneider
> Fix For: 3.0.0
>
>
> While autostarting kars is a good idea for kars representing an application it is not good for kars representing a repository.
> For example if you create a kar from all camel features to use camel offline then it makes no sense to start all the camel features when this kar is deployed.
> So I propose to add a Manifest entry for the kar file like:
> Karaf-Features-Start: false
> If this entry is found then the feature repo files are installed but not started. If the entry is missing then all features are started.
--
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] [Commented] (KARAF-1552) Support kars that will not be auto
started
Posted by "Achim Nierbeck (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13295772#comment-13295772 ]
Achim Nierbeck commented on KARAF-1552:
---------------------------------------
yeah, this sound like a reasonable proposal for repositories +1
> Support kars that will not be auto started
> ------------------------------------------
>
> Key: KARAF-1552
> URL: https://issues.apache.org/jira/browse/KARAF-1552
> Project: Karaf
> Issue Type: Improvement
> Reporter: Christian Schneider
> Fix For: 3.0.0
>
>
> While autostarting kars is a good idea for kars representing an application it is not good for kars representing a repository.
> For example if you create a kar from all camel features to use camel offline then it makes no sense to start all the camel features when this kar is deployed.
> So I propose to add a Manifest entry for the kar file like:
> Karaf-Features-Start: false
> If this entry is found then the feature repo files are installed but not started. If the entry is missing then all features are started.
--
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