gradle dependencies: Usage & Common CI Errors

Print the resolved dependency tree, per configuration.

dependencies is the built-in Gradle report task that prints the dependency tree for each configuration (compileClasspath, runtimeClasspath, testRuntimeClasspath, etc.), showing transitive dependencies and how Gradle resolved version conflicts.

What it does

dependencies lists every configuration and its resolved tree, annotating selected versions (e.g. "1.2 -> 1.4") where conflict resolution upgraded a dependency. Scope it to one configuration with --configuration to cut the noise.

Common usage

Terminal

./gradlew dependencies
./gradlew dependencies --configuration runtimeClasspath
./gradlew :app:dependencies --configuration compileClasspath

Common error in CI (and the fix)

Symptom: a NoSuchMethodError or NoClassDefFoundError at runtime from two versions of the same library. Cause: conflicting transitive versions; Gradle picks the highest by default, which may be incompatible. Fix: run dependencies (or dependencyInsight) to see the "X -> Y" upgrade, then pin the version with a constraint in the dependencies block or a resolutionStrategy.force, or exclude the unwanted transitive path.

Related guides

gradle dependencyInsight: Usage & Common CI ErrorsWhat gradle dependencyInsight does - explains why a dependency resolved to the version it did and which paths… Gradle "Could not resolve all dependencies" - Fix in CIFix Gradle "Could not resolve all dependencies for configuration" in CI -- a missing repository, a wrong coor… Java "NoClassDefFoundError" - Fix Classpath/Init Errors in CIFix "java.lang.NoClassDefFoundError" in CI -- a class present at compile time is missing from the runtime cla… Java "NoSuchMethodError" - Fix Dependency Version Conflicts in CIFix "java.lang.NoSuchMethodError" in CI -- a method present at compile time is missing at runtime because a d…