[GRADLE-2516] Using gradleApi() may lead to classpaths with conflicting jar versions Created: 10/Oct/12  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Szczepan Faber Assignee: Unassigned
Resolution: Won't Fix Votes: 4


 Description   

gradleApi() dependency does not participate in conflict resolution with other dependencies. Example:

apply plugin: 'java'

repositories {
  mavenCentral()
}

dependencies {
  compile gradleApi()
  //in reality, commons-lang may be pulled in as some transitive dependency
  compile 'commons-lang:commons-lang:2.4'
}

task printDeps << {
  def deps = configurations.compile.files*.name.sort()
  deps.each { println it }  
  //will show 2 different versions of commons-lang jar
}

Actually, this problem applies to any kind of self-resolving dependencies (like files('some.jar')) merged in a single configuration with repository-resolvable dependencies. In case of a user consciously choosing self-resolving deps as means of managing dependencies it is his problem to deal with duplicate jars. However, a plugin developer who uses gradleApi() and some external dependencies (like: 'commons-lang:commons-lang:x), he should not have to worry about the duplicate jars.

 Comments   
Comment by David M. Karr [ 31/Mar/15 ]

I don't know if this is related, but I see issues related to this even if I don't include the "gradleApi" dependency. I had it originally, but I removed it. I'm still getting Gradle including the "commons-io" 1.4 jar from the Gradle distribution (not from my Gradle cache). This makes my dependency on commons-io 2.4 useless. I don't even see "commons-io 1.4" in the "gradle dependencies" output.

To fix this in my code, I had to manually copy several classes from commons-io 2.4 into my codebase, renaming them and changing references. This is not a reasonable solution, but it's the only thing I can do right now to get this working.

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:24:05 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.