Java 8 to 11 Migration: Complete Migration with Documentation #66
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 completes the Java 8 to 11 migration effort with CI pipeline updates, Docker configuration, build tooling, test infrastructure, and comprehensive documentation. Changes include:
maven:3.8.8-eclipse-temurin-11andeclipse-temurin:11-jre-alpine)-Xlint:allcompiler argmysql:mysql-connector-javatocom.mysql:mysql-connector-jsrc/test/resources/application.propertieswith H2 in-memory database for testsMIGRATION_NOTES.mdwith comprehensive migration detailsREADME.mdwith Java 11 requirements and build instructionsUpdates since last revision
com.mysql:mysql-connector-j)MIGRATION_NOTES.mddocumenting all migration changesREADME.mdwith Java Requirements section and build instructionsReview & Testing Checklist for Human
mvn clean verifylocally with Java 11 to verify build and tests passdocker build -t bankapp-test .Recommended test plan:
Notes
mvn clean verifyusing JDK 17 (which is backward compatible with Java 11 bytecode)MIGRATION_NOTES.mdfor detailed documentation of all changesLink to Devin run: https://app.devin.ai/sessions/89995ffcaca640cbabedd871069f9dde
Requested by: Joao Esteves (joao.esteves@cognition.ai) / @joao-cognition