[GRADLE-2483] Provide the dependencies of user defined configurations through the Tooling API Created: 17/Sep/12  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Improvement
Reporter: Attila Kelemen Assignee: Unassigned
Resolution: Won't Fix Votes: 4


 Description   

Currently it is not possible to see the dependencies added to a user defined configuration (i.e., other than compile, testCompile, runtime, testRuntime).

A real world example where this is needed is when a "provided" configuration is created to containing the dependencies known to be available at runtime. Here you can find such a project: https://github.com/vert-x/mod-mongo-persistor

The best would be of course to be able to retrieve these dependencies through the Tooling API but there are other acceptable solutions:

Alternative solutions:

1. Support the "provided" configuration natively (see: GRADLE-784) and make its dependencies visible through the Tooling API (even if as compile time dependencies).

2. Allow to specify what kind of dependencies (of the already existing four configs) a user defined configuration contains.

You can see the issue reported to me here: https://github.com/kelemen/netbeans-gradle-project/issues/7

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