Repository navigation
A bug-fix release for 2.25: pre-release versions are now left out where 2.25.0 and 2.25.1 still offered them, and display-plugin-updates no longer fails on a plugin declared in several profiles of a parent POM. It requires Maven 3.9.0 or later and Java 8 or later, as before.
✨ Highlights
display-dependency-updateshonoursallowPreReleases. Since 2.25.0 every goal is meant to skip alpha, beta, milestone, release candidate, preview and early-access versions by default, but this goal still offered them whateverallowPreReleaseswas set to (#1491). Early-access versions such as28-ea+12are now recognised as pre-releases in every goal.- The
maxDependencyUpdatesenforcer rule gainsallowPreReleases. Defaultfalse, as in the goals: pre-releases no longer count as updates and no longer fail the rule unless you set it totrue. display-plugin-updatesno longer fails with "Duplicate key". A report plugin declared in two profiles of a parent POM broke the goal in 2.25.1 (#1490); the last declaration now wins.- No more
minimumReleaseAgewarnings for snapshots. WithminimumReleaseAgeset, every SNAPSHOT in the local repository logged "Cannot determine the publication date". Snapshots now skip the age check;allowSnapshotsdecides whether they are offered.
🚀 New features and improvements
- Leave pre-releases out of the maxDependencyUpdates rule (#1495) @slachiewicz
🐛 Bug Fixes
- Skip the minimumReleaseAge lookup for snapshots (#1493) @slachiewicz
- Read a parent plugin declared in several profiles once (#1494) @slachiewicz
- Leave pre-releases out of display-dependency-updates (#1492) @slachiewicz
Thanks to @slachiewicz.