[GRADLE-577] better message for transitive dependencies on download failure Created: 30/Jul/09  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: New Feature
Reporter: Philip Crotwell Assignee: Unassigned
Resolution: Won't Fix Votes: 1


Currently, if for example you have a dependency like:
compile group: 'log4j', name: 'log4j', version: '1.2.15'
you can get download failures for transitive dependencies, but it is very hard to figure out where they came from.

Cause: Could not resolve all dependencies for configuration 'testRuntime':

  • download failed: javax.jms#jms;1.1!jms.jar
  • download failed: com.sun.jdmk#jmxtools;1.2.1!jmxtools.jar
  • download failed: com.sun.jmx#jmxri;1.2.1!jmxri.jar

I presume this error message comes from Ivy, but it would be great if the "download
failed" message could show the transitive link instead of just the
jar, perhaps

  • download failed: javax.jms#jms;1.1!jms.jar transitive from log4j:log4j:1.2.15
    That would really help in tracking down these types of user errors.

Comment by Hans Dockter [ 03/Aug/09 ]

I agree. As you have pointed out, this comes from Ivy. Ivy does not offer a straight forward way to get subset of a dependency graph. But we have worked this out for the report so we could apply this to improve the error reporting as well.

Comment by Szczepan Faber [ 10/Dec/12 ]

I'd love the error message contain the dependency path(s) in a similar form dependency graphs show the dependency trees.

With Gradle 1.4, you can run gradle dependencies report and it will show you the failed dependencies in the graph.

Since Gradle 1.4, you can run gradle dependencyInsight --configuration testRuntime --dependency javax.jms:jms-1.1 to find out more about the particular dependency. Dependency insight report is available since Gradle 1.3 however, in Gradle 1.4 the report also accepts and renders unresolved dependencies.

Hope that helps!

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