You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2011/07/11 10:56:00 UTC

[jira] [Updated] (KARAF-510) maven dependency structure should match feature contents

     [ https://issues.apache.org/jira/browse/KARAF-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Baptiste Onofré updated KARAF-510:
---------------------------------------

    Fix Version/s:     (was: 3.0.0)
                   3.1.0
                   3.0.1

> maven dependency structure should match feature contents
> --------------------------------------------------------
>
>                 Key: KARAF-510
>                 URL: https://issues.apache.org/jira/browse/KARAF-510
>             Project: Karaf
>          Issue Type: Improvement
>          Components: tooling
>    Affects Versions: 3.0.0
>            Reporter: David Jencks
>            Assignee: David Jencks
>             Fix For: 3.0.1, 3.1.0
>
>
> In general the dependency structure of the maven projects should agree with the features.xml descriptors or karaf base server contents.  For instance if we use maven-bundle-plugin to include some dependencies into a bundle then these dependencies should be marked <scope>provided</scope> in the pom.  Similarly if we expect a bundle B1 that is a dependency of bundle B2 in feature F2 and we expect B1 to be provided by a different feature F1 then B1 should be marked provided in B2's pom.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira