reminder to moderators not to moderate through anything from this address. I tried emailing it, but didn't get a response. Who knows what they've done.
- Brett [EMAIL PROTECTED] wrote: > 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 > > > 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 > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
