Automatically supplemented properties may break existing Java-Kotlin maven project CodeQL CI

[NorthRealm]

Hello. I have a Java 8 project which is a custom package that uses both Java and Kotlin. In my recent updates to the package I notice there's possibly a change in CodeQL bundle between 2.23.5 and 2.23.6 that has broken my CodeQL CI.

The difference is the properties supplemented to mvn by autobuild. In the latest successful CodeQL run there's no automatic -Dmaven.compiler.source=8 -Dmaven.compiler.target=8 from autobuild while this failed one has, where autobuild detects Java 8 correctly. And because kotlin-maven-plugin is not recognizing 8, the compilation fails.

The pom.xml has maven.compiler.source and maven.compiler.target already as 1.8, everything except the CodeQL CI goes well.

Probably not a big deal by manually creating a codeql.yml, but I don't see it necessary in the project, and feel quite annoyed by this small yet breaking change. Is the properties intentionally added automatically, or am I just simply doing something wrong?

[IdrissRio]

Thanks for the report. This is a bug on our side. The Kotlin compiler does not accept Java 8 and expects 1.8 instead. We are actively working on a fix and expect it to land in the next release.