[GRADLE-832] `gradle dependencies` should work if there are dependencies that can't be found and display what is missing Created: 22/Feb/10 Updated: 17/Jan/13 Resolved: 06/Dec/12
Currently, the -n option still requires all dependencies to download in order to succeed. I had an issue yesterday where I was trying to track down why my project was pulling in certain odd maven modules but I didn't have their custom repositories in my repo set. I never was really sure which configuration they belonged to and so just filtered them out of everything.
Later I started to wonder if there should be a way to get -n to work anyway and somehow report that the jars are missing (ie: the dependency tree stops but is not really terminated).
...maybe it can just report the misses and continue to work without all downloads succeeding.
|Comment by Philip Crotwell [ 22/Feb/10 ]|
This might be related to
I am not sure of how much overlap there is between -n and dependencyReport, so maybe not.
|Comment by Hans Dockter [ 02/Mar/10 ]|
In 0.9 Gradle does not try to download the actual artifacts. Yet if you use remote repositories with pom's containing metatdata, Gradle must downloads the pom for a correct dependency report. On the other hand, Gradle will also try to do this, if you are using jar only repositories. So in 0.10 we might provide ways to be more expressive whether your dependency relies on a pom or not. In the first case a dependency report should work without repository access. In the second case we could provide two versions of the report. One if the pom is not accessible (e.g. not in the cache and offline), the other if the pom is accessible. In the first case the report could say that the tree is truncated here because of missing information. But it would still give you potentially important information.