Make Boot Gradle plugin setting kotlin.version based on kotlinPluginVersion

[sdeleuze]

I have got several users mentioning it is not obvious to define Kotlin version in a single place with Gradle plugins { } block (which is the recommended way to use Gradle, especially Gradle Kotlin DSL) and Spring Boot without adding a gradle.properties file (which is not supported yet by Gradle Kotlin DSL). Result can be mixed Kotlin versions in the classpath.

I have been discussing with Gradle team, and they advised to use following syntax in order to be able to sync Spring Boot Kotlin version with Gradle compiler one.

plugins {
    val kotlinVersion = "1.2.20"
    id("org.jetbrains.kotlin.jvm") version kotlinVersion
    id("org.jetbrains.kotlin.plugin.spring") version kotlinVersion
    id("org.springframework.boot") version "2.0.0.M7"
    id("io.spring.dependency-management") version "1.0.4.RELEASE"
}

extra["kotlin.version"] = plugins.getPlugin(KotlinPluginWrapper::class.java).kotlinPluginVersion

While achieving single definition of Kotlin version without gradle.properties, this is not obvious for users to write this kind of declaration and not very nice to find it in start.spring.io generated projects.

While discussing with @wilkinsona, he mentioned the possibility to update Spring Boot Gradle plugin to react to the Kotlin plugin being applied and set the kotlin.version property to the value of kotlinPluginVersion. This would be a very natural and elegant outcome to this issue.

[snicoll]

start.spring.io sets kotlin.version when Kotlin is selected. So what would be the outcome if we implemented this?

[wilkinsona]

I suspect there would be no need for start.spring.io to do that any more. Instead, It would just configure the Kotlin plugin(s) with the appropriate version and Boot's Gradle plugin would take care of the rest.

[sdeleuze]

Thank you so much for that one :-)

[leoedeng]

Is it possible to move this functionality to the dependency-management plugin? I usually work on multi-module projects, and let the dependency-management plugin manage the dependencies for all the modules. I tried boot 2.0.0.RC1 with kotlin 1.2.21, and it worked perfectly for the modules with boot plugin applied, but in other modules the kotlin-stdlib and kotlin-stdlib-jre7 version were still 1.2.20.

[wilkinsona]

Unfortunately not, no. The fix relies on knowing that it's the kotlin.version property that controls the version of Kotlin dependencies. That property is specific to Spring Boot's spring-boot-dependencies bom.

[leoedeng]

Ah, that makes sense. It's not big deal, I am setting the kotlin.version property manually like before then. BTW, starting from kotlin 1.2, kotlin-stdlib-jdk8 is preferred to kotlin-stdlib-jre8, and also kotlin-stdlib-jdk7 to kotlin-stdlib-jre7. Any plan to replace them in the future?