[
https://issues.apache.org/jira/browse/KARAF-884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348312#comment-15348312
]
ASF subversion and git services commented on KARAF-884:
-------------------------------------------------------
Commit 2d96f914382423762f86c3432587510247beb955 in karaf's branch
refs/heads/karaf-4.0.x from [~skitt]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=2d96f91 ]
[KARAF-884] Generate feature dependencies
Currently, POMs containing feature dependencies (classifier "features"
and type "xml") produce features listing all the required bundles.
This patch causes feature generation to represent feature dependencies
using <feature/> elements instead.
As a side-effect, aggregate features produce a new aggregate feature
containing all the generated features.
Signed-off-by: Stephen Kitt <[email protected]>
> karaf-maven-plugin should more closely map to POMs
> --------------------------------------------------
>
> Key: KARAF-884
> URL: https://issues.apache.org/jira/browse/KARAF-884
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-tooling
> Affects Versions: 3.0.0
> Reporter: Brian Topping
> Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.6, 3.0.8
>
>
> If karaf-maven-plugin is run against a set of POMs, the output of a feature
> generated for a given project seems to be the transitive closure of the
> dependencies in the form of a <bundle> entry for each dependency of the
> project. This seems incorrect though. Consider if a parent project P builds
> A and B where A depends on X, B depends on A and Y. Currently, the feature
> for A will be a single bundle entry for X and the feature for B will be three
> bundle entries for A, X & Y.
> It seems to make more sense that the feature for B would actually be one
> <feature> entry for A and a <bundle> entry for Y. The <bundle> for X would
> be transitively found through the feature definition for A.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
