[GRADLE-2621] eclipse plugin puts source jars as classpath entries Created: 09/Jan/13  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: 1


Imagine a module declared this way in ivy.xml (skipping most of the ivy.xml):

  <artifact name="jackson-core-asl" type="jar" ext="jar" conf="master"/>
  <artifact name="jackson-core-asl" type="source" ext="jar" conf="sources" m:classifier="sources"/>

When gradle build declares dependency to jackson-core-asl and eclipse classpath is generated, the .classpath contains both, the sources jar and library jar:

<classpathentry sourcepath="/.../jackson-core-asl-1.8.5-sources.jar" kind="lib" path="/.../jackson-core-asl-1.8.5.jar" exported="true"/>
<classpathentry kind="lib" path="/.../jackson-core-asl-1.8.5-sources.jar" exported="true"/>

The correct content of .classpath should only have the library jar with source attachement (1st entry in, 2nd entry out).


For most projects, this issue does not yield any wrong behavior (e.g. the project builds in eclipse). To avoid the source entries you can do something like:

allprojects {
  plugins.withType(EclipsePlugin) {
    project.plugins.withType(JavaBasePlugin) {
      eclipse.classpath.file.whenMerged { classpath ->
        classpath.entries.removeAll { it.path.endsWith('-sources.jar') }

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