kotlin module uses different kotlin version than what boot provides, prevents boot 3.1 compatibility builds

[spencergibb]

This causes build failures when testing compatibility with boot 3.1.x. It also sets the target jvm version to 1.8, it should be 17

spring-cloud-function/spring-cloud-function-kotlin/pom.xml

Lines 64 to 99 in 9e39f2c

	<plugin>
	<artifactId>kotlin-maven-plugin</artifactId>
	<groupId>org.jetbrains.kotlin</groupId>
	<version>1.6.0</version>
	<configuration>
	<args>
	<arg>-Xjsr305=strict</arg>
	</args>
	<compilerPlugins>
	<plugin>spring</plugin>
	</compilerPlugins>
	<jvmTarget>1.8</jvmTarget>
	</configuration>
	<executions>
	<execution>
	<id>test-compile</id>
	<goals>
	<goal>test-compile</goal>
	</goals>
	<configuration>
	<sourceDirs>
	<sourceDir>${project.basedir}/src/test/kotlin</sourceDir>
	<sourceDir>${project.basedir}/src/test/java</sourceDir>
	</sourceDirs>
	<jvmTarget>1.8</jvmTarget>
	</configuration>
	</execution>
	</executions>
	<dependencies>
	<dependency>
	<groupId>org.jetbrains.kotlin</groupId>
	<artifactId>kotlin-maven-allopen</artifactId>
	<version>1.6.0</version>
	</dependency>
	</dependencies>
	</plugin>

One potential issue is the use of kotlin-maven-allopen which I don't think is managed anywhere. Maybe we can ask the boot team to manage it?

Here is a similar change that gateway made spring-cloud/spring-cloud-gateway@4c4c6f3

[spencergibb]

Not sure upgrading to 1.8.10 is the right answer. Boot 3.0 uses 1.7.x. Will a boot 3.0 app work if this is compiled with 1.8.x?

[olegz]

I guess back to your original comment, i'd rather not to even include the version and have it managed higher up.