Refactor Maven properties and centralize Spring BOM versions#106
Merged
mercyblitz merged 3 commits intomicrosphere-projects:dev-1.xfrom Mar 27, 2026
Merged
Refactor Maven properties and centralize Spring BOM versions#106mercyblitz merged 3 commits intomicrosphere-projects:dev-1.xfrom
mercyblitz merged 3 commits intomicrosphere-projects:dev-1.xfrom
Conversation
Delete explicit maven.compiler.source and maven.compiler.target (set to 8) from microsphere-spring-cloud-openfeign/pom.xml to rely on parent/default compiler plugin settings and reduce duplication.
Remove Spring Boot/Cloud version properties from the top-level and place them into a renamed profile (java8-16 -> spring-cloud-2021). The profile is now activeByDefault (was activated by a JDK range) and contains spring-boot.version, spring-cloud.version and spring-cloud-alibaba.version. Also update junit-jupiter.version to 5.14.3 at the top level. This centralizes Spring BOM versions in a dedicated, enabled profile and upgrades the JUnit version.
|
Codecov Report✅ All modified and coverable lines are covered by tests. 🚀 New features to boost your workflow:
|
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 dependency and configuration management in the project’s Maven POM files, primarily focusing on clarifying version management and improving consistency. The main changes involve moving Spring Cloud and related dependency versions into a dedicated Maven profile, updating the JUnit Jupiter version, and removing explicit Java compiler version settings.
Dependency and configuration management improvements:
spring-boot,spring-cloud, andspring-cloud-alibabaversion properties from the global properties section into a dedicated Maven profile namedspring-cloud-2021, which is now active by default. This clarifies version scoping and makes the configuration more maintainable. [1] [2]junit-jupiter.versionproperty from6.0.3to5.14.3in the global properties, ensuring the correct and latest compatible version is used.Build configuration cleanup:
maven.compiler.sourceandmaven.compiler.targetproperties frommicrosphere-spring-cloud-openfeign/pom.xml, likely to allow these to be inherited or set elsewhere, reducing redundancy.