[
http://jira.codehaus.org/browse/MNG-2686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann reopened MNG-2686:
------------------------------------
Assignee: (was: Brett Porter)
Reproduced and IT for MNG-1895 extended. Maven doesn't do anything special to
resolve a conflict between provided and test scope, it just picks the scope
from the nearest dependency.
> POM dependency scope auto-downgrades from provided to test
> ----------------------------------------------------------
>
> Key: MNG-2686
> URL: http://jira.codehaus.org/browse/MNG-2686
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Dependencies
> Affects Versions: 2.0.4
> Reporter: Frank Cornelis
> Priority: Critical
>
> My project has a dependency on:
> XXX:YYY:jar:1.0-SNAPSHOT (selected for null)
> with transitive dependency:
> commons-logging:commons-logging:jar:1.1:test
> and again triggering a transitive dependency on:
> javax.servlet:servlet-api:jar:2.3:test (selected for test)
> Later on the project also has a dependency:
> AAA:BBB-container:pom:1.0-SNAPSHOT:provided (selected for provided)
> I use this to represent the dependencies provided by the J2EE container in
> which the application will be deployed.
> This triggers via:
> tomcat:catalina:jar:5.5.15:provided (selected for provided)
> the following funny thing:
> javax.servlet:servlet-api:jar:2.4:provided (removed - nearer found: 2.3)
> Leaving me without servlet-api for the compile scope.
--
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
