StormeHawke wrote:
>
> Strange that it works with Maven though. *shrug*
>
Maven uses a different strategy for resolving version conflicts. It picks
the "nearest" version in the dependency graph. That's why your explicit
dependency wins. You can simulate this behavior to some extent with "compile
'some:dependency:version' { force = true }" in Gradle.
Cheers,
Peter
--
View this message in context:
http://gradle.1045684.n5.nabble.com/Strange-dependency-behavior-tp3322739p3323221.html
Sent from the gradle-user mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
