[
https://issues.apache.org/jira/browse/KARAF-5204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16289291#comment-16289291
]
Jean-Baptiste Onofré commented on KARAF-5204:
---------------------------------------------
It could work if the provided features repository cleanly provides
{{<repository/>}}. Then, we can iterate in the inner defined {{<repository/>}}
and create the corresponding kar files.
However, unfortunately, in the case of the Aries RSA, it doesn't define
{{<repository/>}} for the SCR feature (which is basically wrong).
> Create dependant feature KAR files when KAR:Create find external feature
> dependancy
> -----------------------------------------------------------------------------------
>
> Key: KARAF-5204
> URL: https://issues.apache.org/jira/browse/KARAF-5204
> 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.5
>
>
> It would be nice if the KAR:Create command could create additional KAR files
> to capture all the listed dependencies for the requested feature. Currently
> you have to manually review the feature that you are exporting to a KAR and
> look for feature references that are external to the feature. This external
> feature review then has to be performed recursively on each external feature.
> A good example of this is the aries-rsa repo which references the feature
> "scr", which is defined in the "standard" repository. After I exported
> aries-rsa, and tried to start it, it was missing the bundle
> org.apache.karaf.scr:org.apache.karaf.scr.management. Manually created the
> "standard" KAR to include the "scr" feature and aries-rsa-core feature then
> started successfully.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
