[GRADLE-3210] IDEA model in Tooling API does not allow multiple source artifacts for library Created: 10/Dec/14  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Daz DeBoer Assignee: Unassigned
Resolution: Won't Fix Votes: 0

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

 Description   

A single ivy module may contain multiple jar artifacts together with multiple source artifacts. Presently, there's no way for Gradle to know which source artifact(s) are related to which jars. This was addressed in the fix for GRADLE-3170 by attaching every source artifact to each jar artifact. The duplicate source declarations that result seem to be handled fine by IDEA.

However, GRADLE-3170 fixed the issue for the Gradle 'idea' task, but did not push this fix out to the IDEA model exposed by the Tooling API.

This means that this issue remains unfixed:
https://youtrack.jetbrains.com/issue/IDEA-128460

 Comments   
Comment by Daz DeBoer [ 10/Dec/14 ]

This would be fixed by:

1. Add the appropriate methods to IdeaSingleEntryLibraryDependency
2. Add implementation to DefaultIdeaSingleEntryLibraryDependency.
3. Add an integration test that verifies that the new methods work for the current Gradle version.
4. Add a mix in to make the new methods work for older Gradle versions.
5. Update the integration test to verify that the new method work for older Gradle versions too.
6. Mention in release notes.

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