Seeing dependency tree
suggest changeUse the task dependencies. Depending on how your modules are set up, it may be either ./gradlew dependencies
or to see the dependencies of module app use ./gradlew :app:dependencies
The example following build.gradle file
dependencies { compile 'com.android.support:design:23.2.1' compile 'com.android.support:cardview-v7:23.1.1' compile 'com.google.android.gms:play-services:6.5.87' }
will produce the following graph:
Parallel execution is an incubating feature. :app:dependencies ------------------------------------------------------------ Project :app ------------------------------------------------------------ . . . _releaseApk - ## Internal use, do not manually configure ## +--- com.android.support:design:23.2.1 | +--- com.android.support:support-v4:23.2.1 | | \--- com.android.support:support-annotations:23.2.1 | +--- com.android.support:appcompat-v7:23.2.1 | | +--- com.android.support:support-v4:23.2.1 (*) | | +--- com.android.support:animated-vector-drawable:23.2.1 | | | \--- com.android.support:support-vector-drawable:23.2.1 | | | \--- com.android.support:support-v4:23.2.1 (*) | | \--- com.android.support:support-vector-drawable:23.2.1 (*) | \--- com.android.support:recyclerview-v7:23.2.1 | +--- com.android.support:support-v4:23.2.1 (*) | \--- com.android.support:support-annotations:23.2.1 +--- com.android.support:cardview-v7:23.1.1 \--- com.google.android.gms:play-services:6.5.87 \--- com.android.support:support-v4:21.0.0 -> 23.2.1 (*) . . .
Here you can see the project is directly including com.android.support:design
version 23.2.1, which itself is bringing com.android.support:support-v4
with version 23.2.1. However, com.google.android.gms:play-services
itself has a dependency on the same support-v4
but with an older version 21.0.0, which is a conflict detected by gradle.
(*)
are used when gradle skips the subtree because those dependencies were already listed previously.
Found a mistake? Have a question or improvement idea?
Let me know.
Table Of Contents