Java 8 to 11 Migration: Toolchain Configuration and CI Updates #170
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR improves the Java 11 build configuration by adding proper Gradle toolchain support and modernizing the CI workflow. The project was already targeting Java 11 but lacked explicit toolchain configuration and had outdated CI action versions.
Build changes:
CI changes:
Review & Testing Checklist for Human
DefaultJwtServiceTest.java)javap -von a compiled class)Recommended test plan: After CI passes, pull the branch locally and run
./gradlew clean build testto verify the build works end-to-end.Notes
The codebase was analyzed for usage of removed JDK modules (JAXB, JAX-WS, JavaFX, CORBA, Nashorn) - none were found, so no additional dependencies were needed.
See
MIGRATION_NOTES.mdfor detailed documentation of all changes.Link to Devin run: https://app.devin.ai/sessions/22a134aac3e944e9a8ca4a321fa2f16f
Requested by: milind@cognition.ai (@milind-cognition)