spring-projects / spring-projects/spring-boot
Use Gradle toolchains so that we fail with a useful error message on JDK < 24
Open
Nobody has claimed this yet.
status: pending-design-work
type: task
- Dominant language
- Java
- Stars
- 81.5k
- Forks
- 42.7k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 65
Description
As we now have JSpecify and NullAway in our build, we should configure our build to always compile with JDK 24, no matter what JDK is used to run Gradle.
Compiling with JDK 17 fails because of a compiler bug, which is fixed in 24 (and maybe get backported to 17).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Gradle build configuration that controls Java compilation and review how the JSpecify and NullAway setup is applied. Configure compilation to use JDK 24 independently of the Gradle runtime, and verify that running with an older JDK fails with a useful error message.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100