I think one of these plugins is explicitly changing the `com

Question

I think one of these plugins is explicitly changing the `compile kotlin stdlib ` dependency version to match what they find in the build environment which is wrong

Czar · Answer

``` Root project classpath + org springframework boot spring boot gradle plugin 2 0 0 M6 | + org springframework boot spring boot loader tools 2 0 0 M6 | | + org springframework spring core 5 0 1 RELEASE | | | org springframework spring jcl 5 0 1 RELEASE | | org apache commons commons compress 1 14 | + io spring gradle dependency management plugin 1 0 3 RELEASE | org apache commons commons compress 1 14 + org jetbrains kotlin kotlin gradle plugin 1 1 60 | + org jetbrains kotlin kotlin gradle plugin api 1 1 60 | | org jetbrains kotlin kotlin stdlib 1 1 60 gt 1 1 51 | | org jetbrains annotations 13 0 | + org jetbrains kotlin kotlin stdlib 1 1 60 gt 1 1 51 | + org jetbrains kotlin kotlin compiler embeddable 1 1 60 | | + org jetbrains kotlin kotlin stdlib 1 1 60 gt 1 1 51 | | + org jetbrains kotlin kotlin script runtime 1 1 60 | | org jetbrains kotlin kotlin reflect 1 1 60 gt 1 1 51 | | org jetbrains kotlin kotlin stdlib 1 1 51 | + org jetbrains kotlin kotlin annotation processing gradle 1 1 60 | | + org jetbrains kotlin kotlin stdlib 1 1 60 gt 1 1 51 | | org jetbrains kotlin kotlin compiler embeddable 1 1 60 | + org jetbrains kotlin kotlin android extensions 1 1 60 | | org jetbrains kotlin kotlin compiler embeddable 1 1 60 | org jetbrains kotlin kotlin compiler runner 1 1 60 | + org jetbrains kotlin kotlin build common 1 1 60 | + org jetbrains kotlin kotlin daemon client 1 1 60 | org jetbrains kotlin kotlin compiler embeddable 1 1 60 + org jetbrains kotlin kotlin allopen 1 1 60 | + org jetbrains kotlin kotlin gradle plugin api 1 1 60 | org jetbrains kotlin kotlin stdlib 1 1 60 gt 1 1 51 + org jetbrains kotlin kotlin noarg 1 1 60 | + org jetbrains kotlin kotlin gradle plugin api 1 1 60 | org jetbrains kotlin kotlin stdlib 1 1 60 gt 1 1 51 io spring gradle dependency management plugin 1 0 3 RELEASE ```

Czar · Answer

should I file an issue on GitHub

Czar · Answer

and whose issue is this actually kotlin dsl s or jetbrains plugins

bamboo · Answer

There s no issue in `kotlin dsl` AFAICS that s the expected behaviour for the buildscript classpath the version of `kotlin stdlib` is pinned to the embedded version 1 1 51 atm because that s the one available in the Gradle buildscript classpath

bamboo · Answer

I don t think there s an issue with the JetBrains Kotlin plugin either because you can definitely build with 1 1 60 and the production stdlib dependency will be correct

bamboo · Answer

So I would bet it s one of ``` id org jetbrains kotlin plugin spring version 1 1 60 id org jetbrains kotlin plugin jpa version 1 1 60 ```

mkobit · Answer

It s almost certainly a spring dependency management plugin issue

Czar · Answer

for now I m just including all stdlib flavours with forced 1 1 60 version will continue the investigation tomorrow Thanks for all the pointers