Circular dependencyManagement excludes all classpath dependencies

It seems that if in the parent pom you have something like:

....
<dependencyManagement>
<dependency>
<groupId>org.apache.tapestry</groupId>
<artifactId>tapestry-test</artifactId>
<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.