[GRADLE-2013] Version in DependencyManagement of Parent pom not considered Created: 23/Dec/11  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 1.0-milestone-6
Fix Version/s: None

Type: Bug
Reporter: Stefan Sieber Assignee: Unassigned
Resolution: Won't Fix Votes: 0


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:
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.


Comment by Stefan Sieber [ 23/Dec/11 ]

Forgot to mention the workaround (which works for me) as proposed by Daz DeBoer

There is a workaround for this issue: use the new "force" feature on ResolutionStrategy to set the correct version of hibernate-core. Of course, this doesn't make use of the information in the parent pom, but it will allow you to use the correct version. (see http://gradle.org/releases/latest/docs/dsl/org.gradle.api.artifacts.ResolutionStrategy.html)

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 12:10:25 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.