Is there a difference between: ```tasks.withType(KotlinJvmCompile::class).configureEach { sourc...

# gradle

[eygraber]

Is there a difference between:

tasks.withType(KotlinJvmCompile::class).configureEach {
    sourceCompatibility = JavaVersion.VERSION_11
    targetCompatibility = JavaVersion.VERSION_11

    kotlinOptions {
        jvmTarget = "11"
    }
}

and

android {
  compileOptions {
    sourceCompatibility = JavaVersion.VERSION_11
    targetCompatibility = JavaVersion.VERSION_11
  }

  kotlinOptions {
    jvmTarget = "11"
  }
}

when using the kotlin-android plugin?

[plastiv]

I have noticed a little inconsistency with what stdlib dependency kotlin plugin injects.

Since configuring task is “lazy evaluation” approach kotlin plugin injects kotlin-stdlib instead of kotlin-stdlib-jdk11. Since there is a little practical difference between two I haven’t investigated further what actually happens.

Was checking with ./gradlew :apk-module:dependencies --configuration releaseRuntimeClasspath

[tapchicoma]

if you will confirm this - please open a new issue. Probably worth to fix it

[Alexander.Likhachev]

I believe that sourceCompatibility and targetCompatibility is the properties coming from JavaCompile task rather than KotlinJvmCompile

[eygraber]

So using them in android.compileOptions wouldn't make sense for a 100% Kotlin project?