[GRADLE-1303] rethink default-resolution-strategy for dependencies Created: 12/Jan/11  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 0.9.1
Fix Version/s: None

Type: Improvement
Reporter: Helmut Denk Assignee: Unassigned
Resolution: Won't Fix Votes: 1


 Description   

situation

 
dependencies {
   compile 'org.clojure:clojure:1.2.0'
   compile 'org.clojure:clojure-contrib:1.2.0'
   compile 'enlive:enlive:1.0.0-SNAPSHOT'
}

with enlive having a dependency on clojure too: 

 
<dependency>
 <groupId>org.clojure</groupId>
 <artifactId>clojure</artifactId>
 <version>[1.1.0,)</version>
</dependency>

clojure;1.2.0 is evicted for clojure;1.3.0-alpha4 which is
not a desired result:

 
:: evicted modules:
org.clojure#clojure;1.2.0 by [org.clojure#clojure;1.3.0-alpha4] in [compile]

analysis (by adam murdoch)

I think a better option would be to make the default resolution handle this case better. Given the following dependencies in the graph:

org.clojure:clojure:[1.1.0,)
org.clojure:clojure:1.2.0

Gradle should choose 1.2.0, as it meets both constraints. There's no need for conflict management here, as there's no conflict.

Maven uses a breadth-first conflict resolution strategy, so it's going to hit the dependency on 1.2.0 before it hits the dependency on [1.1.0,)

references

http://gradle.1045684.n5.nabble.com/custom-dependency-conflict-resolver-tp3205266p3205266.html

 Comments   
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 11:52:07 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.