Specify generic type nullness #34140
Comments
sdeleuze
added a commit
to sdeleuze/spring-framework
that referenced
this issue
Jan 9, 2025
In order to be able to fix spring-projectsgh-34140 which requires using at least a Java 22 compiler, this commit intends to change the configuration of the Gradle toolchain to use Java 23, while setting the Java release to Java 17 (or other versions when using MRJARs) when relevant in order to keep the current Java 17 baseline. See spring-projectsgh-34220
sdeleuze
changed the title
sdeleuze
added a commit
to sdeleuze/spring-framework
that referenced
this issue
Jan 9, 2025
In order to be able to fix spring-projectsgh-34140 which requires using at least a Java 22 compiler, this commit intends to change the configuration of the Gradle toolchain to use Java 23, while setting the Java release to Java 17 (or other versions when using MRJARs) when relevant in order to keep the current Java 17 baseline. See spring-projectsgh-34220
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As a follow-up of #28797, Spring Framework 7 should specify generic type nullness across its codebase, as well as fixing issues reported when configuring
NullAway:JSpecifyMode=true, see https://github.com/uber/NullAway/wiki/JSpecify-Support for more details.The text was updated successfully, but these errors were encountered: