karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KARAF-884) karaf-maven-plugin should more closely map to POMs
Date Fri, 03 Jun 2016 15:49:59 GMT

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

ASF GitHub Bot commented on KARAF-884:
--------------------------------------

Github user skitt closed the pull request at:

    https://github.com/apache/karaf/pull/194


> 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 was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message