[GRADLE-1995] Tooling API: Allow to explicitly retrieve information about unresolved dependencies Created: 12/Dec/11  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Denis Zhdanov Assignee: Unassigned
Resolution: Won't Fix Votes: 2


The Tooling API doesn't allow to get information about unresolved third-party dependencies. Here is a simple test that illustrates that:

  1. Go to $GRADLE_HOME/samples/java/quickstart;
  2. Define, say, version '10.2' for 'commons-collections' dependency at 'build.gradle' there;
  3. Start the program below:
    package org.jetbrains.plugins.gradle;
    import org.gradle.tooling.GradleConnector;
    import org.gradle.tooling.ModelBuilder;
    import org.gradle.tooling.ProjectConnection;
    import org.gradle.tooling.model.idea.*;
    import java.io.File;
     * @author Denis Zhdanov
     * @since 12/8/11 5:07 PM
    public class GradleStartClass {
      private static final String GRADLE_PROJECT_PATH = "/home/denis/dev/gradle/gradle-1.0-milestone-6/samples/java/quickstart";
      public static void main(String[] args) {
        test("/home/denis/dev/gradle/gradle-1.0-milestone-6"); // Don't expect exception here
      private static void test(String gradleHome) {
        GradleConnector connector = GradleConnector.newConnector();
        connector.useInstallation(new File(gradleHome));
        connector.forProjectDirectory(new File(GRADLE_PROJECT_PATH));
        ProjectConnection connection = connector.connect();
        ModelBuilder<? extends IdeaProject> modelBuilder = connection.model(IdeaProject.class);
        IdeaProject project = modelBuilder.get();
        for (IdeaModule module : project.getModules()) {
          for (IdeaDependency dependency : module.getDependencies()) {
            if (dependency instanceof IdeaModuleDependency) {
            System.out.printf("Dependency: %s%n", ((IdeaSingleEntryLibraryDependency)dependency).getFile());


Dependency: unresolved dependency - commons-collections#commons-collections;10.2
Dependency: /home/denis/.gradle/caches/artifacts-4/junit/junit/c12498cf18507aa6433a94eb7d3e77d5/jars/junit-4.10.jar
Dependency: /home/denis/.gradle/caches/artifacts-4/org.hamcrest/hamcrest-core/c12498cf18507aa6433a94eb7d3e77d5/jars/hamcrest-core-1.1.jar

Comment by Szczepan Faber [ 16/Jan/12 ]

What do you mean explictly? If the dependency type has a flag isResolved() (or something like that, e.g. information about the resolution result) is it good enough?

Comment by Denis Zhdanov [ 16/Jan/12 ]

Yes, that would be sufficient

Comment by Denis Zhdanov [ 22/Jan/13 ]

I see that gradle-1.4-rc-2 mentions the following at the release notes:

'With earlier versions of Gradle, it was not possible to generate a dependency resolution report if one of the dependencies could not be resolved. This has been rectified. Not only will the dependency resolution reports run successfully if a dependency cannot be resolved, the reports will now include details of those dependencies that couldn't be resolved.'

However, that is information is still unavailable via the tooling api.

Comment by Szczepan Faber [ 25/Jan/13 ]

Correct. We'll fix it at some point. Thanks for being patient!

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