[MNG-5404] Wrong resolution of dependency scope by Maven 3

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 3.0.4
• Fix Version/s: 4.0.x-candidate, needing-scrub-3.4.0-fallout
• Component/s: Dependencies
• Assignee: Unassigned
• Reporter: Dmitry Batrak
• Created: 05/Dec/12 22:47
• Updated: 27/Nov/20 12:37

Description

For the following POM:

<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> 

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.

Issue Links

• is related to: MNG-5622 Provided dependencies updated to 'compile' even when excluded