Details
-
Type:
Improvement
-
Status: Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 3.0.0
-
Component/s: None
-
Labels:None
Description
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.
Attachments
Issue Links
- relates to
-
KARAF-657 kar deployer should start the feature
-
- Closed
-