[GRADLE-1761] Tooling api SimpleIdeaProject should include information about dependencies, too Created: 22/Aug/11  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

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


 Description   

Tooling API allows to get information about target project structure without resolving all of it's dependencies (at least for IntelliJ IDEA view, see org.gradle.tooling.model.idea.OfflineIdeaProject interface). However, it doesn't provide information about third-party dependencies that don't present at the local cache yet ('~/.gradle').

The feature request is to expose that information as well. Looks like 'dependency name', 'dependency version' and 'dependency group' (properties of Dependency object) are enough.

Benefits:

  • software that works with the tooling api may show the whole project structure to the end-user without 'library download' delay;
  • we can offer automatic library resolve (e.g. check local maven repo and global libraries that are already configured at the IDE level);

 Comments   
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:03:40 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.