Dmitry Batrak created MNG-5404:
----------------------------------

             Summary: Wrong resolution of dependency scope by Maven 3
                 Key: MNG-5404
                 URL: https://jira.codehaus.org/browse/MNG-5404
             Project: Maven 2 & 3
          Issue Type: Bug
    Affects Versions: 3.0.4
            Reporter: Dmitry Batrak
         Attachments: build.log

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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to