I am getting resolve errors and want to see the dependency tree to see where the problem is. It seems that Gradle doesn’t allow this - which is hard to believe. I run “gradle dependencies” and get a “Could not resolve all dependencies” error.
Sounds like you have some unresolvable ‘buildScript’ dependencies, which are necessary to evaluate the build script itself. Until you’ve fixed those issues, you won’t be able to run the ‘dependencies’ task.
How is someone supposed to debug dependency issues? Is there a way to get Gradle to output the tree yp to the point that the error occurs?
For regular dependency issues, use ‘gradle dependencies’ and/or ‘gradle dependencyInsight’. For ‘buildScript’ dependency issues (which should be less frequent and less complicated), use the console/log output.
dependencyInsight must be new. I’ll look into it.