[
http://jira.codehaus.org/browse/MWAR-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90320
]
Frank Cornelis commented on MWAR-83:
------------------------------------
If A has scope provided, shouldn't that mean that A and everything that comes
with it, is provided, including B? It's how I would expect it to behave. Thus B
would also be marked as provided somehow? Or am I interpreting the scope
transitivity wrong?
> transitive dependency on POM artifact not respected
> ---------------------------------------------------
>
> Key: MWAR-83
> URL: http://jira.codehaus.org/browse/MWAR-83
> Project: Maven 2.x War Plugin
> Issue Type: Bug
> Affects Versions: 2.0.1
> Reporter: Frank Cornelis
>
> When I build a WAR with the following dependencies:
> A (scope provided, type pom) -> B (scope compile, type jar)
> C (scope runtime, type jar) -> B (scope compile, type jar)
> then B gets included under WEB-INF/lib which I think it should not be. I use
> the provided pom artifact A to represent the dependencies provided by my
> container.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
