Our build does not use `kts` buildscripts, however i still see that `kotlin-scripting` plugin is app...

# gradle

[Josh Friend]

Our build does not use kts buildscripts, however i still see that kotlin-scripting plugin is applied by the kotlin plugin, which is always creating the compileJava task during configuration. Can I somehow avoid using the kotlin-scripting plugin entirely?

[tapchicoma]

kotlin plugin does not create compileJava tasks 🙂

[tapchicoma]

on the original topic - no, you could not remove scripting plugin. This plugin is used when scripts are passed as a sources to the compilation task. If there are no scripts - overhead should be minimal

[Josh Friend]

yeah i thought that would be weird for kotlin to create a compileJava task, but the build scan looks like it blames kotlin.

[Josh Friend]

i put a tasks.withType(JavaCompile).configureEach {} in my build logic and set a breakpoint to see who was configuring the task. heres the stack trace, kotlin plugin is there in the stack

stack.txt

[Josh Friend]

perhaps fixed in a kotlin 2.x release? i only see this in the 1.9.x release we are still using https://github.com/JetBrains/kotlin/blob/v1.9.24/libraries/tools/kotlin-gradle-plugin/src/common/kotlin/org/jetbrains/kotlin/gradle/plugin/mpp/KotlinSoftwareComponent.kt#L214

[Josh Friend]

ah yeah, fixed in 2.0 https://github.com/JetBrains/kotlin/commit/dbd77fc785474065ed152e84d8218d085e9df8ea
https://youtrack.jetbrains.com/issue/KT-60664