-
Notifications
You must be signed in to change notification settings - Fork 299
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove support for running on JDK / Java 8 #634
Comments
EP 2.15.0 has a check enabled by default that we want to disable (see google/error-prone#3366). We cannot just disable this check with the existing config, since it does not exist in version 2.10.0, the latest version that works with JDK 8. Rather than adding conditional config around this one check, this PR disables compiling our code with Error Prone checks on JDK 8. We still check all our code with Error Prone on JDK 11+, and we are still running our own tests on JDK 8 (for now; see #634). Beyond the config changes, no code changes were required.
Upon further thought, I think we shouldn't be too aggressive in dropping Java 8 support. There are scenarios in which libraries that still want to target Java 8 would want to build on a JDK 8 JVM, and NullAway dropping that support would make things more inconvenient. I think we can survive with the hacks we have for now. Leaving this open as we want to do this eventually |
We're now at the end of 2023, and I think we should aim to drop support for running NullAway on JDK 8 in the near future. Specifically, I propose:
@lazaroclapp @yuxincs thoughts? |
This was done a while back |
Error Prone dropped support for Java 8 several months ago:
https://github.com/google/error-prone/releases/tag/v2.11.0
Dropping Java 8 support will allow us to clean up several ugly hacks in the NullAway code and build configuration. We'll aim to cut one final release supporting Java 8 before doing this.
The text was updated successfully, but these errors were encountered: