Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This pull request updates the Maven wrapper and related build tooling to improve reliability, maintainability, and ensure key dependencies are kept up to date. The changes include upgrading the Maven wrapper version, improving the robustness of the wrapper scripts, refactoring the build configuration to use version properties, and adding a script to check for outdated Maven plugin dependencies.
Key changes:
Maven Wrapper and Build Tooling Updates
maven-wrapper.properties.mvnwandmvnw.cmdscripts to better handle extraction of Maven distributions, especially for snapshot versions where the extracted directory name may differ from the archive filename. The scripts now robustly locate the correct Maven directory before moving it. [1] [2] [3] [4] [5]mvnwandmvnw.cmd. [1] [2] [3] [4]Build Configuration Improvements
pom.xmlto use properties for plugin and dependency versions (e.g.,failsafe.version,surefire.version,jacoco.version,checkstyle.version,springboot.version,jjwt.version), and updated plugin/dependency declarations to reference these properties. This makes version management easier and more consistent. [1] [2] [3] [4] [5] [6] [7]Dependency Version Checking
tools/check-be-deps.sh, which checks if key Maven plugins and Spring Boot dependencies are up to date by comparing the current version inpom.xmlwith the latest available from Maven Central. This helps ensure the project uses the latest stable versions of important build tools.Minor Enhancements and Fixes
mvnwfor better compatibility.mvnw.cmdfor Windows environments.These changes collectively improve build reliability, simplify dependency management, and help keep the project up to date with the latest build tooling.