[ 
https://issues.apache.org/jira/browse/KARAF-5198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16359295#comment-16359295
 ] 

Jean-Baptiste Onofré commented on KARAF-5198:
---------------------------------------------

That's good idea, the {{kar:create}} command could use a releases set 
optionally to define the feature started automatically (using the {{install}} 
flag).

> KAR:Create update feature file based on list of features provided
> -----------------------------------------------------------------
>
>                 Key: KARAF-5198
>                 URL: https://issues.apache.org/jira/browse/KARAF-5198
>             Project: Karaf
>          Issue Type: Improvement
>          Components: karaf-kar
>         Environment: N/A
>            Reporter: George McCone
>            Assignee: Jean-Baptiste Onofré
>            Priority: Minor
>             Fix For: 4.2.0, 4.1.6
>
>
> When you create a KAR file using the kar:create command, you can give it a 
> list of features of the specified repo to include in the KAR file.
> It appears that the feature file that is included in the KAR is copied 
> straight out of the repo and includes all the features regardless of the 
> those specified.
> When the KAR is deployed, it is starting all the features in the feature 
> file. In many cases this is resulting in the starting of numerous other 
> features.
> One good example of this is the cxf-dosgi repo's feature "cxf-dosgi-base" 
> which has a feature defined for libs needed when running outside Karaf (or at 
> least that is what the description says for the feature). It references a 
> bunch of bundles that come with core Karaf and when this feature tries to 
> install, it hangs the KAR deployer and Karaf won't shutdown correctly.
> It would be nice if the feature file either removed those features that were 
> not exported, or mark the feature with install="manual", assuming KARAF-5197 
> adds this capability.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to