Trying to update to Compose Compiler 1.4.5 and I'm seeing the following error. Anyone else run into ...

# compose

[Marcelo Hernandez]

Trying to update to Compose Compiler 1.4.5 and I'm seeing the following error. Anyone else run into this? I'm using JDK 11.

Untitled

[itnoles]

that's Java 17

[Marcelo Hernandez]

That's what I figured. But no where in the release notes am I seeing a mention of this "breaking" change:
https://developer.android.com/jetpack/androidx/releases/compose-compiler#version_145_3

[Kirill Grouchnikov]

Are you building from command line or from Studio?

[Marcelo Hernandez]

Command line.

[Marcelo Hernandez]

I guess I'm wondering if potentially making JDK 17 required was intended for Compose Compiler 1.4.5. 🤔

[Marcelo Hernandez]

I'm seeing the same issue in CI (GitHub Action) which has always been configured to use Java 11 for our build jobs.

[Ben Trengrove [G]]

The forced upgrade to Java 17 is being rolled back in another release

[Marcelo Hernandez]

The release notes have also been updated to include this information about the JDK 17 requirement for 1.4.5.

[Colton Idle]

there was a force update for compose + jdk?

[Marcelo Hernandez]

Yes, but next week there will be a 1.4.6 release that reverts back to JDK 11.

[Francis Mariano]

Do you think 1.4.6 release is available this week or the next??

[Marcelo Hernandez]

I believe it is supposed to come out this week. But for what it's worth, Android Gradle Plugin 8 also shipped last week and it too requires JDK 17. So if you're interested in updating to Android Gradle Plugin 8, Gradle 8.x, and Kotlin 1.8.20, you'll have to update to JDK 17 regardless.

[Marcelo Hernandez]

From there, Compose Compiler 1.4.5 can be used as is without having to wait for 1.4.6 😄

[Francis Mariano]

Ok, I want to update a library to kotlin 1.8.20 // compose-multiplatform 1.4.0 // compose-compiler 1.4.5/1.4.6 but I do not want to force the JDK 17

[Marcelo Hernandez]

If I'm not mistaken, I believe I saw a warning from the Kotlin Multiplatform plugin with Kotlin 1.8.20 that Gradle 7.x is not officially supported. 🤷‍♂️

[Marcelo Hernandez]

It's inevitable if you want to keep up with the latest and greatest tooling to ultimately update to JDK 17.

[Marcelo Hernandez]

You'd still target Java 11 with JDK 17.

[Marcelo Hernandez]

If I'm not mistaken, I believe I saw a warning from the Kotlin Multiplatform plugin with Kotlin 1.8.20 that Gradle 7.x is not officially supported. 🤷‍♂️

I could be wrong though. 🙂

[Francis Mariano]

You'd still target Java 11 with JDK 17.

Like this???

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

[Marcelo Hernandez]

For Android library modules, yes.

[Marcelo Hernandez]

If you have pure JVM modules, you'll need to do

tasks.withType<KotlinCompile>().configureEach {
    kotlinOptions {
        jvmTarget = "11"
    }
}

// If you still have code in Java.
// This includes if you use Dagger/Hilt with pure Kotlin since Dagger/Hilt code-gen is in Java.
tasks.withType<JavaCompile>().configureEach {
    sourceCompatibility = "11"
    targetCompatibility = "11"
}

[Marcelo Hernandez]

Assuming Kotlin Gradle DSL ☝️

[Francis Mariano]

So if I publish a library with JDK 17, a consumer can build it with JDK 11 ???

[Marcelo Hernandez]

I believe as long as the source and target compatibility are properly configured to 11, yes. Does your library have a sample app that you can test this with?

[jim]

Compose Compiler 1.4.6 with support for Java11 toolchain is released: https://developer.android.com/jetpack/androidx/releases/compose-compiler#1.4.6