Two changes here need a word before the list.
Maven 3.9.0 is now the minimum for building. minimalMavenBuildVersion moves from 3.6.3 to 3.9.0, so an older Maven stops at enforce-maven-version, and the plexus-release profile no longer carries its own override. This is build-side only: the parent declares no <prerequisites> and requireMavenVersion is never checked on consumers, so the Maven version able to consume artifacts built from this parent is unchanged.
Managed versions are renamed to version.<artifactId>, as org.apache:apache names them. Seven property names disappear: spotless-maven-plugin.version, mavenPluginToolsVersion, mavenFluidoSkinVersion, mavenSurefireVersion, junit5Version, njord.version and sisuMavenPluginVersion. A child that still references one fails at POM read with must be a valid version but is ${...}. In this organisation that was plexus-languages, plexus-sec-dispatcher and modello; all three were fixed before this release.
The same pass brings three smaller changes from org.apache:apache and maven-parent: checkstyle defaults to maven_checks_nocodestyle.xml and no longer fetches a header file over the network on every run, enforceBytecodeVersion ignores test scope, and the single enforcer execution splits into enforce-maven-version, enforce-java-version and enforce-bytecode-version so a child can relax one check without losing the other two. The palantir-java-format version used by spotless is now pinned, so apply on one JDK and check on another cannot disagree.
🔧 Build
- Require Maven 3.9.0 to build (
9bb20a1) - Align build configuration with the ASF parent POM conventions (#439) @slachiewicz
📝 Documentation updates
- Rewrite the README and the site index in Google developer style (#441) @slachiewicz
📦 Dependency updates
- Bump version.njord from 0.9.9 to 0.9.10 (#440) @dependabot[bot]