Did you ever have android build failed issue because of dependency resolution?
… or you were curious where all these old rxjava dependencies come from?
You can pretty easy track the module causing issues via following gradle command.
gradlew :root-module:dependencyInsight \
--configuration debugRuntimeClasspath \ // or debugCompileClasspath
--dependency io.reactivex:rxjava:1.1.0 > dependencies.txt // saves result to 'dependencies.txt' file
Output of dependencies.txt
io.reactivex:rxjava:1.1.0 -> 1.3.8
\--- com.jakewharton.rxbinding:rxbinding:0.4.0
\--- com.jakewharton.rxbinding:rxbinding-support-v4:0.4.0
\--- project :my-module-1
+--- debugRuntimeClasspath
You can use any combination of maven groupId, artifactId and version.
// dependency with specific version
--dependency io.reactivex:rxjava:1.1.0
// dependency with any version
--dependency io.reactivex:rxjava
// dependency with specific groupId
--dependency io.reactivex:rxjava