Im currently working with Gradle Milestone 6 on a larger project. We have a few issues after migrating our partially working gradle build from Milestone 3 to Milestone 6. One of the issues is that the version numbers of the parent pom of a project we're referencing seems to be no longer considered:

The parent pom containins:
----------------
...
dependencyManagement>
<dependencies>
<dependency>
<groupId>org.hibernate</groupId>
<artifactId>hibernate-annotations</artifactId>
<version>3.4.0.GA</version>
</dependency>
<dependency>
<groupId>org.hibernate</groupId>
<artifactId>hibernate-core</artifactId>
<version>3.3.1.GA</version>
</dependency>
....
-------------------
The pom of the project we're referencing has a dependency to hibernate-annotations (resolved to version 3.4.0.GA). Hibernate-annotations 3.4.0.GA itself has a dependency to hibernate-core 3.3.0.SP1.

The versions in the dependencyManagement section of the parent pom should override versions of transitive dependencies (http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Management). That means in the above example that hibernate-core version 3.3.1.GA should be used (from the parent pom). This is also how gradle up to Milestone 5 works. Unfortunately in Milestone 6 you changed the behaviour. In our project, gradle MS6 resolves hibernate-core to version 3.3.0.SP1.

Updates:

• Gradle 1.0-milestone-7-20111222000018+0100 has the same problems
• the problem occurs both using 'mavenRepo' and 'maven' - syntax.
• The corresponding discussion on gradle-dev is here: http://gradle.1045684.n5.nabble.com/Version-in-DependencyManagement-of-Parent-pom-not-considered-td5089384.html