[ http://jira.codehaus.org/browse/MNG-1921?page=all ]
John Casey updated MNG-1921:
----------------------------
Fix Version: 2.0.5
> test scope in dependencyManagement does not appear to be transitive to
> dependent subProjects
> --------------------------------------------------------------------------------------------
>
> Key: MNG-1921
> URL: http://jira.codehaus.org/browse/MNG-1921
> Project: Maven 2
> Type: Bug
> Versions: 2.0.1
> Environment: jdk1.5.0_04, mvn 2.0.1
> Reporter: Brian Bonner
> Fix For: 2.0.5
>
>
> 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
--
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
