build: fix maven-enforcer config and enforce plugin versions#1867
build: fix maven-enforcer config and enforce plugin versions#1867spannm wants to merge 2 commits into
Conversation
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1867 +/- ##
============================================
- Coverage 92.52% 92.48% -0.05%
+ Complexity 3563 3561 -2
============================================
Files 346 346
Lines 7050 7050
Branches 684 684
============================================
- Hits 6523 6520 -3
- Misses 365 366 +1
- Partials 162 164 +2 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
- Move requireMavenVersion rule inside the <rules> block to fix warning - Raise minimum required Maven version to 3.9 - Add requirePluginVersions rule to ensure reproducible builds
cfdd025 to
d0c17c1
Compare
|
Should the project's maven wrapper be updated as well? (I have no idea how that's handled, my primary projects use gradle) |
Updated maven wrapper scripts and properties using the command: ./mvnw wrapper:wrapper
Yes @kingthorin, I just updated the wrapper scripts and properties using |
Summary
According to Official Apache Maven documentation, Maven 3.8.x and earlier have reached End of Life (EOL) and new plugin releases will require Maven 3.9.0 or later.
This PR updates our build constraints accordingly, raises the minimum required Maven version to 3.9, and fixes a misconfiguration within the
maven-enforcer-plugin.Changes
[3.6,)to[3.9,)withinrequireMavenVersion.requireMavenVersionrule inside the<rules>element to resolve the unknown parameter warning.requirePluginVersionsrule to guarantee reproducible builds by banning missing plugin versions, excluding common core plugins viaunCheckedPluginList.