Fix Maven compiler plugin configuration for Java 17 (EB-3) #20
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.
JIRA Ticket
EB-3: Fix Maven compiler plugin configuration for Java 17 in COG-GTM/Springboot-BankApp
Overview
This PR fixes a Java version mismatch in the Maven compiler plugin configuration. The project's
java.versionproperty was correctly set to 17, but the Maven compiler plugin was still configured for Java 1.8, creating build configuration inconsistencies.Changes Made
<version>3.8.0</version>to leverage Spring Boot's dependency management (now uses 3.13.0)<source>1.8</source>and<target>1.8</target>with<release>17</release><release>element which is the recommended approach for Java 9+ projectsRationale
The
<release>configuration element provides better compatibility than separate source/target settings because it:Verification
Build succeeds with the new configuration:
The compiler now correctly uses Java 17 for both source and target, matching the project's runtime environment (OpenJDK 17 in Docker) and Spring Boot 3.3.3 requirements.
Context
Link to Devin run: https://app.devin.ai/sessions/a9449a0118cf4a8399ff9c577cfa032b
Requested by: Alex Peng (alex.peng@windsurf.com) (@alexjpeng)