[GRADLE-2911] Attaching source information to dependencies (eg: for use in the Eclipse plugin) Created: 02/Oct/13  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Task
Reporter: Gradle Forums Assignee: Unassigned
Resolution: Won't Fix Votes: 4


 Description   

First posted here: [1]http://stackoverflow.com/questions/19...

I have this dependency:

testCompile group:"org.apache.mrunit", name:"mrunit", version:"1.+", classifier:'hadoop2'

I'm also using the `eclipse` plugin, but that dependency isn't getting its sources attached. The sources are there in Maven Central, hiding under the "sources" classifier, so I tried adding this:

testCompile group:"org.apache.mrunit", name:"mrunit", version:"1.+", classifier:'sources'

But that didn't solve my problem.

It'd be nice to have a way to specify the source dependency for a code dependency.
----------------------------------------------------------------------------------------
[1] http://stackoverflow.com/questions/19081423/attaching-a-source-dependency-to-a-dependency-with-classifiers

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

I tried to make it another way:
compile('org.codehaus.groovy:groovy:2.1.9') {
artifact

{ name = 'groovy' type = 'jar' extension = 'jar' classifier = 'indy' }

artifact

{ name = 'groovy' type = 'source' extension = 'jar' classifier = 'sources' }

}
but is still doesn't work in IDEA.

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