what's the difference between ```tasks.withType<KotlinCompile> { kotlinOptions { freeCompilerA...

# gradle

[kqr]

what's the difference between

tasks.withType<KotlinCompile> {
  kotlinOptions {
    freeCompilerArgs = listOf("-Xjsr305=strict", "-Xallow-any-scripts-in-source-roots")
  }
}

and

kotlin {
  compilerOptions {
    freeCompilerArgs.add("-Xjsr305=strict")
    freeCompilerArgs.add("-Xallow-any-scripts-in-source-roots")
  }
}

or to be more precise why the latter one does not work ?:)

[mateusz.kwiecinski]

The first one seems to be deprecated now:
https://kotlinlang.org/docs/compatibility-guide-18.html#changes-in-compiler-options

he kotlinOptions task input and the kotlinOptions{...} task DSL are in a support mode and will be deprecated in upcoming releases.

[mateusz.kwiecinski]

ah, I missed the question 🤦‍♂️ Does setting compilerOptions instead of kotlinOptions on the tasks directly work?

[kqr]

yes -Xallow-any-scripts-in-source-roots is respected in the first one

[mateusz.kwiecinski]

You can println what are tasks's compilerOptions.freeCompilerArgs in both scenarios and compare them 🙂 They both should work the same way.
I can't play with your source code, but maybe you have custom kotlinCompile tasks that are not configured by KGP, maybe the later scenario has some extra arguments in the freeCompilerArgs already, which are overwritten in the first scenario (by freeCompilerArgs = listOf()

[kqr]

thanks, you are right. in parent module I had

tasks.withType<KotlinCompile> {
  kotlinOptions {
    freeCompilerArgs = listOf("-Xjsr305=strict")
  }
}

[tapchicoma]

Do you have a repro? Generally second approach should also work

[tapchicoma]

btw first one replaces any previously configured freeCompilerArgs - better to use +=

[tapchicoma]

Overall better to not use kotlinOptions - they are semi-deprecated and we should add normal @Deprecated annotation in 2.0

[kqr]

If I may continue here. I have in

tasks.withType<KotlinCompile> {
    kotlinOptions {
      freeCompilerArgs += "-Xjsr305=strict"
      jvmTarget = "17"
    }
  }

in my root build file in allprojects block. How can I use kotlin there? or how can I achieve globally set compile options that can be fine tuned in subprojects? right now this will apparently override anything I set in subprojects with kotlin even when using +=

[tapchicoma]

hm, something like this may work:

plugins {
    id("org.jetbrains.kotlin.jvm")
}

allprojects {
    kotlin.compilerOptions {
        // common configuration for compiler args
   }
}

[kqr]

that unfortunately did not work, but this looks like it did

tasks.withType<KotlinCompile> {
    compilerOptions {
      freeCompilerArgs.add("-Xjsr305=strict")
      jvmTarget.set(JvmTarget.JVM_17)
    }
  }