You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "David Jencks (JIRA)" <ji...@apache.org> on 2011/09/21 08:38:08 UTC
[jira] [Commented] (KARAF-884) karaf-maven-plugin should more
closely map to POMs
[ https://issues.apache.org/jira/browse/KARAF-884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13109299#comment-13109299 ]
David Jencks commented on KARAF-884:
------------------------------------
I don't understand what you want, there seem to be a lot of possiblities. Can you try playing with stuff like this:
<features>
<feature>declarative-services</feature>
<feature>core</feature>
</features>
<aggregateFeatures>true</aggregateFeatures>
and see if you can get the effect you want? If not a project showing the relationships you want would be helpful.
> 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
>
> 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 is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira