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

Stephen Connolly updated MNG-5404:
----------------------------------
    Fix Version/s:     (was: 3.5.0)
                   3.4.0

> Wrong resolution of dependency scope by Maven 3
> -----------------------------------------------
>
>                 Key: MNG-5404
>                 URL: https://issues.apache.org/jira/browse/MNG-5404
>             Project: Maven
>          Issue Type: Bug
>          Components: Dependencies
>    Affects Versions: 3.0.4
>            Reporter: Dmitry Batrak
>            Assignee: Jason van Zyl
>             Fix For: 3.4.0
>
>         Attachments: build.log, compile-as-transitive-of-provided.tgz, 
> example.zip
>
>
> For the following POM: 
> {noformat}
> <project> 
>     <modelVersion>4.0.0</modelVersion> 
>     <groupId>test</groupId> 
>     <artifactId>A</artifactId> 
>     <version>1.0</version> 
>     <dependencies> 
>         <dependency> 
>             <groupId>org.apache.axis2</groupId> 
>             <artifactId>axis2-xmlbeans</artifactId> 
>             <version>1.5</version> 
>             <scope>provided</scope> 
>         </dependency> 
>         <dependency> 
>             <groupId>org.apache.axis2</groupId> 
>             <artifactId>axis2-codegen</artifactId> 
>             <version>1.5</version> 
>             <exclusions> 
>                 <exclusion> 
>                     <groupId>org.apache.geronimo.specs</groupId> 
>                     <artifactId>geronimo-stax-api_1.0_spec</artifactId> 
>                 </exclusion> 
>             </exclusions> 
>         </dependency> 
>     </dependencies> 
> </project> 
> {noformat}
> running 'mvn dependency:resolve' using Maven 3.0.4 yields a wrong result. 
> Namely, geronimo-stax-api_1.0_spec dependency is reported as having the 
> resolved scope of 'compile'. With Maven 2.2.1 I get the 'provided' scope, as 
> expected.
> Debug log is attached.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to