[GRADLE-576] dependencyReport should not download artifacts Created: 30/Jul/09  Updated: 04/Jan/13  Resolved: 24/Nov/10

Status: Resolved
Project: Gradle
Affects Version/s: 0.7
Fix Version/s: 0.9-rc-1

Type: New Feature
Reporter: Philip Crotwell Assignee: Hans Dockter
Resolution: Fixed Votes: 0


I just figured out an error in my build script relating to log4j and
transitive dependencies, basically I had
compile group: 'log4j', name: 'log4j', version: '1.2.15'
and when I ran gradle jar I got this:

Execution failed for task ':fissuresImpl:test'.
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

Very confusing as the jms, jmxtools and jmxri dependencies were
sneaking in as transitive dependencies of log4j (at least I think that
is what is happening). In trying to figure this out, I tried gradle
dependencyReport to see where the jms dependencies were coming from,
but it also died due with the same error.

In order to help find these "bad" transitive dependencies, it would be
really nice if the dependencyReport did not actually try to download
the jars. I would think that all the information needed to generate
the report would exist in either the build.gradle or perhaps poms and
ivy.xml files if using the remote repositories.

Comment by Hans Dockter [ 03/Aug/09 ]

I agree that this would make a lot of sense. The only difficulty with implementing this issue are the project dependencies. But I have already an idea how to solve this.

Generated at Wed Jun 30 11:33:28 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.