[GRADLE-2430] eclipse task does not attach source if .jar has a classifier Created: 09/Aug/12  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Steve Eynon Assignee: Unassigned
Resolution: Won't Fix Votes: 1

Issue Links:
Related
Related to GRADLE-3170 Gradle 'idea' task generates wrong so... Resolved

 Description   

When referencing a .jar from a local Maven repository, if that .jar has a classifier, then no source .jar is attached.

dependencies

{ compile "com.af:config:1.3.10:T53" }

only gives

<classpathentry kind="lib" path="C:/Maven/com/af/config/1.3.10/config-1.3.10-T53.jar" exported="true"/>

Have tried many permutations of source jar names in case there's a standard I'm not aware of, but no joy:

  • config-1.3.10-sources.jar
  • config-1.3.10-sources-T53.jar
  • config-1.3.10-sourcesT53.jar
  • config-1.3.10-T53-sources.jar
  • config-1.3.10-T53sources.jar

 Comments   
Comment by Andrew Grabko [ 04/Nov/13 ]

I think this issue should be merged into http://issues.gradle.org/browse/GRADLE-2911 because it is more general

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