[GRADLE-3396] Eclipse classpath contains duplicates when version number is unparseable Created: 09/Feb/16  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Lari Hotari Assignee: Unassigned
Resolution: Won't Fix Votes: 0


 Description   

Forum issue:
https://discuss.gradle.org/t/gradle-eclipse-generates-duplicate-classpathentry-in-eclipses-classpath-with-gradle-2-6/11784

Unit test that reproduces the problem:
https://gist.github.com/lhotari/735a4ff4988d6820eac9#file-eclipseclasspathintegrationtest-groovy-L1061-L1101

The problem seems to be related to unparseable version number string. In this case the dependency is 'xpp3:xpp3:1.1.4c' . The VersionNumber class's default scheme cannot parse the version number. The assumption is that the bug is related to the version number.

Here are relevant parts of the test build that reproduces the failure

configure(project(":a")){
    dependencies {
        compile ('xpp3:xpp3:1.1.4c')
    }
}
configure(project(":b")){
    dependencies {
        compile project(':a')
        testCompile project(':a').sourceSets.test.runtimeClasspath
    }
}


 Comments   
Comment by Lari Hotari [ 09/Feb/16 ]

The problem goes away when the dependencies are configured in a proper way.

Currently there are dependencies like this in the original issue reporter's project:

testCompile project(':smack-core').sourceSets.test.runtimeClasspath

The correct way to express the dependency is:

testCompile project(path: ":smack-core", configuration: "testRuntime")
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:47:42 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.