[jira] Closed: (MEAR-143) Plugin does not respect transitive dependency scopes properly

["Laird Nelson (JIRA)" <ji...@codehaus.org>]

     [ https://jira.codehaus.org/browse/MEAR-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Laird Nelson closed MEAR-143.
-----------------------------

    Resolution: Not A Bug

[This StackOverflow answer|http://stackoverflow.com/questions/7588492/maven-dependency-resolution-and-scope-overriding-not-just-another-newbie-questio/7597596#7597596] helped educate me on the fact that dependency management trumps dependency mediation even for scope, which I had not realized.

> Plugin does not respect transitive dependency scopes properly
> -------------------------------------------------------------
>
>                 Key: MEAR-143
>                 URL: https://jira.codehaus.org/browse/MEAR-143
>             Project: Maven 2.x Ear Plugin
>          Issue Type: Bug
>    Affects Versions: 2.6
>            Reporter: Laird Nelson
>         Attachments: mear-143.zip
>
>
> The [Introduction to the Dependency Mechanism page|http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Scope] has a handy table for deciding what to do with transitive dependencies and various scopes.  The Maven ear plugin does not honor it in all cases.
> Suppose I have a {{.jar}} file.  Its name is {{b.jar}}.  It declares a {{runtime}} dependency on {{a.jar}}.
> Suppose now I have an {{.ear}} project.  It declares a {{compile}} scope dependency on {{b.jar}}.
> By the rules of the chart, {{a.jar}} should end up being a {{runtime}} dependency (transitively) of the {{.ear}}, and should be included in the {{lib}} directory.  It is not.

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