karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré (JIRA) <j...@apache.org>
Subject [jira] [Updated] (KARAF-1584) karaf-maven-plugin ignores provided scope on dependency
Date Tue, 25 Feb 2014 07:45:25 GMT

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

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

    Fix Version/s: 3.1.0
                   3.0.1

> karaf-maven-plugin ignores provided scope on dependency
> -------------------------------------------------------
>
>                 Key: KARAF-1584
>                 URL: https://issues.apache.org/jira/browse/KARAF-1584
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-tooling
>    Affects Versions: 3.0.0.RC1
>            Reporter: Brian Topping
>            Assignee: Jean-Baptiste Onofré
>             Fix For: 3.0.1, 3.1.0
>
>
> A dependency expressed in a project POM with {{provided}} scope should not be rendered
in a features.xml by {{karaf-maven-plugin:features-generate-descriptor}}.  
> A good example of this is slf4j-api.  A generated feature that lists that dependency
will not load for some reason that doesn't particularly matter, but there needs to be a way
to both express the dependency for compilation as well as not have the dependency listed in
the feature.  {{provided}} scope seems to be the most accurate way to do that.
> The IT test in KARAF-1537 named test-aggregate-features demonstrates what I am talking
about.
> I'll submit a patch after KARAF-1537 is applied.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message