[MNG-1921] test scope in dependencyManagement does not appear to be transitive to dependent subProjects

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.0.1
• Environment: jdk1.5.0_04, mvn 2.0.1
• Assignee: Carlos Sanchez Gonzalez
• Reporter: Brian Bonner
• Created: 04/Jan/06 13:52
• Updated: 28/May/06 13:46
• Resolved: 28/May/06 13:46

Description

If we have a root pom.xml that includes dependencyManagement and specifies the scope on a dependent component to be test, it's picked up in a subproject, but it's does not appear to be transitive.

e.g. parent pom

<dependencyMgmt>
<dependency>
<artifactId>easymock</artifactId>
...
<scope>test</scope>
</dependency>
</dependencyMgmt>

child pom

<dependency>
<artifactId>easymock</artifactId>
</dependency>

peer pom

<dependency>
<artifactId>child</artifactId>
</dependency>
<dependency>
<artifactId>easymock</artifactId>
</dependency>

The peer pom gets compilation exceptions indicating that it can't find the package specified by the dependent jar easymock. The easymock jar is nowhere in the classpath.

Judging by this: http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html
the test scope should be transitive.

Brian

Issue Links

• duplicates: MNG-1378 Make dependencies of test-jars transitive