Question regarding upgrade from v4.9.5 to v11.1.2 #211
Description
Hi,
We have a project using a very old version of dependency lock(v.4.9.5) with Gradle 5.6.x. In v4.9.5 and Gradle 5.6 the generateLock generate multiple configuration lock like compile/runtime/testCompile /testRuntime...etc and we have those configuration lock in our dependency.lock file for a while.
We recently decided to upgrade to Gradle 6.8 and plugin to v11.1.2. I just found out that in v7.6.0 the plugin removed couple configurations here
And in the releases notes for v8.1.0 it mentioned that Gradle 6.1 has deprecated compile and runtime configuration.
When running generateLock in v11.1.2 and Gradle 6.8 those configurations compile/runtime/testCompile /testRuntime are no longer locked by default. Besides the behavior change in Gradle 6.X, any other decisions behind the removal of those configurations? Would that have any potential impact? All the dependencies in those deprecated configurations are live in runtimeClasspath/compileClassPath so I am assuming it will take effect over, but just want to confirm that the removal of compile/runtime didn't cause any side effect while upgrading the plugin. Thanks for your help!