You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Jamie goodyear (Updated) (JIRA)" <ji...@apache.org> on 2012/03/07 15:22:58 UTC

[jira] [Updated] (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:all-tabpanel ]

Jamie goodyear updated KARAF-884:
---------------------------------

    Fix Version/s:     (was: 3.0.0)
                   3.1.0
    
> 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
>             Fix For: 3.1.0
>
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira