Allow suppressing a warning about JDK 21 deprecating support for targeting java 8 [332788833]

Fixed

Bug

Status Update

No update yet.

Description

au...@google.com

created issue #1

Apr 4, 2024 02:07AM

When building AGP 8.5.0-alpha03, JDK 21 and targeting java 1.8 (androidx set up) a warning prints out:

Java compiler version 21 has deprecated support for compiling with source/target version 8.
Try one of the following options:
    1. [Recommended] Set a lower Java compiler version (using Java toolchain)
    2. Set a higher source/target version
    3. If you don't want to use Java toolchain, try using a lower version of the JDK running the build
       (e.g., by setting the `JAVA_HOME` environment variable or the `org.gradle.java.home` Gradle property)
For more details on how to configure these settings, see https://developer.android.com/build/jdks.

Given that JDK still does allow building Java 1.8 bytecode, there should be away to supress this warning until the support for this bytecode version is removed (like java 1.7).

Comments

au...@google.com <au...@google.com> #2Apr 4, 2024 02:09AM

I am also on Catalina if it helps.

Message last modified on Apr 4, 2024 02:10AM

ar...@google.com <ar...@google.com> Apr 4, 2024 06:08PM

Assigned to an...@google.com.

ga...@google.com <ga...@google.com> Apr 5, 2024 10:31AM

Reassigned to hu...@google.com.

au...@google.com <au...@google.com> #3Apr 8, 2024 04:50PM

I'm also affected but I'm on Windows10. can confirm it on version 4.0 Canary 9

hu...@google.com <hu...@google.com> #4Apr 8, 2024 06:04PM

Happening on junit tests for me as well.

Android Studio 3.6 RC 1
Build #AI-192.7142.36.36.6071332, built on December 13, 2019
Runtime version: 1.8.0_212-release-1586-b4-5784211 x86_64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
macOS 10.15.2
GC: ParNew, ConcurrentMarkSweep
Memory: 1237M
Cores: 16
Registry: ide.new.welcome.screen.force=true, ide.tooltip.initialDelay=600
Non-Bundled Plugins: IdeaVIM, org.jetbrains.kotlin, com.squareup.sqldelight

ga...@google.com <ga...@google.com> #5Apr 8, 2024 07:02PM

I'm not yet able to repro this using MvRx project.
Any additional info any of you have to help us repro this would be useful. Such as:
- Is this happening to Java as well as Kotlin tests?
- How did you start the test run exactly? Through clicking the run button at the top bar, or the run button in the gutter next to the test class/method name, or through context menu in the project view?
- Please attach idea.log of when this reproes for you.

Thanks!

hu...@google.com <hu...@google.com> #6Apr 12, 2024 02:18PM

1) I ran StateStoreTest by clicking the arrow next to the class name. Tests passed
2) I changed the expected value for the first assert in testSubscribeNotCalledForNoop from 1 to 2
3) I reran the tests with control + r. Tests passed
4) I reran them again and they correctly failed (because I changed the assert)

I also ran YourKit. Out of the last 2 runs, the 2nd to last ran with out of date sources and incorrectly passed. The last run incorrectly failed.

au...@google.com <au...@google.com> Apr 12, 2024 05:54PM

Verified by au...@google.com.

hu...@google.com <hu...@google.com> #7Apr 12, 2024 06:01PM

Status: Assigned (reopened)

Thanks, I'm able to repro this now.

hu...@google.com <hu...@google.com> Apr 18, 2024 12:23PM

Marked as fixed.

an...@google.com <an...@google.com> #8May 20, 2024 05:05PM

Any update or workaround here? It's extremely error prone to work when you don't know what version of the source Android Studio is using.

yu...@gmail.com <yu...@gmail.com> #9May 25, 2024 07:12PM

This seems to be an issue where the Gradle plugin does not see up to date sources, maybe due to VFS freshness. Jerome, anyone in Build team can help take a look?

da...@gmail.com <da...@gmail.com> #10May 30, 2024 07:04AM

Comment has been deleted.

Message last modified on May 30, 2024 11:04AM