[KARAF-884] karaf-maven-plugin should more closely map to POMs

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.0
• Fix Version/s: 4.1.0, 4.0.6, 3.0.8
• Component/s: karaf
• Assignee: Jean-Baptiste Onofré
• Reporter: Brian Topping
• Created: 21/Sep/11 04:31
• Updated: 16/Sep/18 04:34
• Resolved: 25/Jun/16 04:14

Description

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.

Issue Links

• is related to: KARAF-510 maven dependency structure should match feature contents
• is related to: KARAF-1530 Create integration tests for karaf-maven-plugin
• links to: GitHub Pull Request #194
• links to: GitHub Pull Request #195