[ http://jira.codehaus.org/browse/MNG-3061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter closed MNG-3061. ----------------------------- Resolution: Cannot Reproduce Fix Version/s: (was: 2.2.x) can't reproduce in 2.0.6, let alone a recent version. Please attach a project showing the issue if it is still a problem > Circular dependencyManagement excludes all classpath dependencies > ----------------------------------------------------------------- > > Key: MNG-3061 > URL: http://jira.codehaus.org/browse/MNG-3061 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Dependencies > Affects Versions: 2.0.6 > Reporter: Hugo Palma > Priority: Critical > > It seems that if in the parent pom you have something like: > .... > <dependencyManagement> > <dependency> > <groupId>org.apache.tapestry</groupId> > <artifactId>tapestry-test</artifactId> > <version>${project.version}</version> > <scope>test</scope> > </dependency> > </dependencyManagement> > .... > when you try to compile the child tapestry-test sub-project it fails because > it can't find any dependencies. In fact doing "mvn > dependency:build-classpath" confirms this. As soon as the > dependencyManagement entry is removed the sub-project compiles just fine. > This works fine in Maven 2.0.5, it just stopped working in 2.0.6. -- 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