Dependency resolution in 4.7 vs 4.10.2


(Alex Dubrouski) #1

Good afternoon,

I am facing interesting difference between dependency resolution in Gradle v4.7 vs v4.10.2

~/projects/service$ ~/gradle-4.7/bin/gradle -q dependencyInsight --configuration runtime --dependency commons-beanutils
commons-beanutils:commons-beanutils:1.9.2 (conflict resolution)
   variant "default+runtime"

versus

~/projects/service$ ~/gradle-4.10.2/bin/gradle -q dependencyInsight --configuration runtime --dependency commons-beanutils
commons-beanutils:commons-beanutils:1.8.3
   variant "runtime" [
      org.gradle.status = release (not requested)
   ]
   Selection reasons:
      - Was requested
      - By conflict resolution : between versions 1.8.0 and 1.8.3
...

commons-beanutils:commons-beanutils:1.9.2 -> 1.8.3
+--- com.google.api-ads:ads-lib:4.0.0
...

In v4.10.2 it does not even consider beanutils 1.9.2 even though it is clearly in dependency tree. I am curios what change in Gradle resolution mechanism could cause this side effect.

Thanks.

P.S. I run command with the same options, on the same code, same JDK, same computer. The only difference is Gradle version.