[
https://jira.codehaus.org/browse/MEAR-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Laird Nelson updated MEAR-143:
------------------------------
Attachment: mear-143.zip
A test case demonstrating the problem, or demonstrating my misunderstanding
(one or the other).
Unzip and run mvn clean install and then look at the resulting .ear project
(and study the pom.xml files).
Note that the .ear project does not contain mear-143-leaf.jar. It is my
understanding that it should.
When dependency management of mear-143-leaf.jar is eliminated, this works as
expected. Is this a bug or a misunderstanding on my part about how dependency
management works?
> 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
