IssueTracker

(Updated the bug title to make it clearer that this is about targeting bytecode 17 when compiling AGP, not the users' code.)

Hung, I am removing the blocking C1 tag but we should not do this in a late Canary, do you think you can do this in the next few weeks ?

Similar change we made for JDK 11: http://ag/q/topic:%22jdk11%22

Thanks, I've uploaded http://ag/q/topic:%22compile-to-jvm-target-17%22 for review.

This appears to break google3 because it changes the JVM target for modules like ddmlib to 17, and google3 still uses JDK 11. See b/284337751 for an example. I think lwuk@ might reach out to discuss.

Starting with AGP 8.2.0-alpha03, AGP was compiled to Java 17 (change).

However, we had to revert this change (see comment #6 or internal Issue 284344368).

Starting with AGP 8.2.0-alpha08, AGP will be compiled to Java 11 again (revert).

We can retry compiling to Java 17 at a later time.

Removed from H Beta blockers list.

This was reverted back to 11, except for lint

Note that this change (as described in #1) also forces all Gradle plugin authors that depend on AGP to target Java 17 as well, even if their feature set only "supports Android" (among other things).

Example: Kotlin Gradle Plugin which depends on AGP, but also the same plugin hosts JS, Native, etc. plugins which have the Gradle minimum Java target of Java 8.

There is a workaround, but it's very hacky. If anyone is interested, I commented out the code here: https://github.com/TWiStErRob/net.twisterrob.gradle/pull/531/commits/1186324b0d0b9daf96ce32cc130dc86536b54e09, because of #9 above.

We'll revisit this issue in a future release, so decreasing priority.

This was reverted back to 11, except for lint

Lint is back to 11 as well: https://cs.android.com/android-studio/platform/tools/base/+/6738759a511d59f3864d55105f774e0af23b4989