[GRADLE-2180] Tooling API: Expose information about the dependency graph Created: 18/Mar/12  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 1.0-milestone-9
Fix Version/s: None

Type: New Feature
Reporter: Denis Zhdanov Assignee: Unassigned
Resolution: Won't Fix Votes: 9


It would be cool if the Gradle API exposes information about dependencies graph (similar to the 'gradle dependencies' output).

That would allow IDE integration to visualize that information for the IDE users.

Comment by Chuck May [ 18/Jun/13 ]

This issue is over a year old. Is there any thought when it might get done? It is limiting the quality of the IDEA IntelliJ Gradle plugin since it has no way of displaying the dependency graph. The Maven plugin in IntellJ shows this information.

Comment by Adam Murdoch [ 28/Jun/13 ]

@Chuck, we would welcome a contribution to add this if you (or anyone else) is interested in helping out. Adding stuff to the tooling API models is fairly straight-forward, once you know what the pattern is, and this information would be very useful to expose to tools.

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