Hi Stefan Glad that "forced versions" works for you. If you could file a Jira issue that would be great.
cheers Daz On 23 December 2011 00:35, Sieber, Stefan D. <[email protected]> wrote: > Hi Daz > > > > Thank you for the detailed explanation. I guessed that the problem is > related to your work on the dependency resolution engine. > > > > The workaround you proposed works well for me and was exactly what I was > looking for (forcing the version in a one place in contrast to 'patching' > every dependency to that artifact). > > > > Should I file a Jira issue for you? > > > > Merry Christmas and Happy new Year to the whole Gradle Team! Keep up the > great work :) > > > > Stefan > > > ------------------------------ > *Von:* Daz DeBoer [[email protected]] > *Gesendet:* Donnerstag, 22. Dezember 2011 21:23 > *Bis:* [email protected] > *Betreff:* Re: [gradle-dev] Re: Version in DependencyManagement of Parent > pom not considered. > > Hi Stefan > > The handling of <dependencyManagement> pom elements was previously > handled by a little known feature of Ivy called Dependency Mediation. This > allowed a transitive dependency to force an arbitrary revision of another > transitive dependency, ignoring the usual Conflict Management rules. (see > http://ant.apache.org/ivy/history/2.0.0/ivyfile/override.html). So > handling of > > In M6 we introduced our own Dependency Resolution engine to replace the > one provided by Ivy. We are still using ivy DependencyResolver instances > under the covers, but the resolve engine has been completely reimplemented. > This will allow us to develop new features that just weren't feasible when > using Ivy directly. > > Unfortunately in your case, we have not (yet) implemented a mechanism > for a dependency to force an arbitrary version of another dependency. So > although the parent POM declares "everyone use hibernate-core:3.3.1.GA", > our dependency resolution engine doesn't honour that request. > > 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 > ) > > To take advantage of forced versions, you should use the M7 snapshot. > > Hope this helps > > > On 21 December 2011 00:39, Sieber, Stefan D. <[email protected]> wrote: > >> Hi Peter >> >> Thank you for your fast answer! >> >> - I just tried it with the latest m7 snapshot >> (gradle-1.0-milestone-7-20111219065105+0100). The problem is still the same. >> - We used the old 'mavenRepo', but I just gave it a try with the new >> syntax (in both M6 and M7 snapshot) and the result is the same. >> >> Regards >> >> Stefan >> >> ________________________________________ >> Von: Peter Niederwieser [[email protected]] >> Gesendet: Dienstag, 20. Dezember 2011 20:44 >> Bis: [email protected] >> Betreff: [gradle-dev] Re: Version in DependencyManagement of Parent pom >> not considered. >> >> I don't think it's an intentional change. Could you try with the latest m7 >> snapshot (see announcement at http://forums.gradle.org)? Did you use the >> old >> `mavenRepo()` or the new `maven()` syntax to declare the repository(s)? >> >> -- >> Peter Niederwieser >> Principal Engineer, Gradleware >> http://gradleware.com >> Creator, Spock Framework >> http://spockframework.org >> Twitter: @pniederw >> >> >> -- >> View this message in context: >> http://gradle.1045684.n5.nabble.com/Version-in-DependencyManagement-of-Parent-pom-not-considered-tp5089384p5089883.html >> Sent from the gradle-dev mailing list archive at Nabble.com. >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> >> > > > -- > Darrell (Daz) DeBoer > Principal Engineer, Gradleware > http://www.gradleware.com > > -- Darrell (Daz) DeBoer Principal Engineer, Gradleware http://www.gradleware.com
