Hi Guillaume, +1 from me (binding).
Tested 4.0.0-rc-7 (6d8f301b) on macOS/aarch64 with JDK 21.0.12: - Verified the source zip SHA-512 from the announcement and the GPG signature; distro bin.tar.gz checksum and signature also verified. - Full Maven sources aggregator (~700 module builds: core, doxia, plexus, plugins, shared, misc) built with rc-7 as the runner: success except one module — see below. - Same aggregator with the 3.x plugin/shared lines (717 module builds) under rc-7: same result, no additional failures. - MojoHaus projects (build-helper, extra-enforcer-rules, versions, jaxb2): all green. Plexus plugin DI validation and the default-on PathConflictResolver tripped nothing. - mvnup: migrated a project pinned to old core plugin versions (check/apply/re-apply); no-op re-apply leaves the POM untouched, no bogus JDK constraints, jar-plugin 3.4.2 handled, migrated project builds green. - Probes: consumer POM shape (no leaked executable() conditions), forced wagon transporter still selects wagon, clear error for unsupported source levels, ComparableVersion ordering/transitivity sanity, JLine natives present in the distro. One regression found — non-blocking IMO, but should be known before this closes: - maven-shade-plugin 3.6.2 with createDependencyReducedPom (the default) fails under rc-7: shade re-processes dependency-reduced-pom.xml, whose parent.relativePath then resolves to the project itself, and the corrected parent.relativePath mismatch check (MNG-5146) makes that a FATAL — rc-6 tolerated it. Reproducer: doxia-converter (doxia 1.4-SNAPSHOT). Workarounds: -Dmaven.maven3Personality (as rc-7's own message suggests) or <createDependencyReducedPom>false</createDependencyReducedPom>. Follow-up issue to be filed against shade/core with the analysis. Minor nits, fine to defer: - mvnup check is a dry-run but reports "applied"/"Modified: 1 POMs" wording: https://github.com/apache/maven/issues/13250 - The new unsupported-source-level error says "install JDK -1" when no upper bound is known (cosmetic). Environment note, not a Maven issue: JDK 27 breaks spotless/palantir-java-format in-process with any Maven version. [x] +1 [ ] +0 [ ] -1 Thanks, Sylwester On Mon, Sep 21, 2026 at 2:28 PM Guillaume Nodet <[email protected]> wrote: > Hi all, > > We solved the following issues since rc-6: > https://gist.github.com/gnodet/6da71ea6f95c5701ed989b5f5231554d > > Staging repo: > https://repository.apache.org/content/repositories/maven-2475/ > > Source release: > > https://repository.apache.org/content/repositories/maven-2475/org/apache/maven/apache-maven/4.0.0-rc-7/apache-maven-4.0.0-rc-7-src.zip > > Source release SHA-512: > > e3ad765feb70f616df3f3f1a3725740491e3acb43c65a7eaff18a34a38569e3443ae9cf6e6d9c361b9e33c5c082b9ada0a5dd2b27b477fd7f2cb60e8ecaa721e > > Distribution: > https://dist.apache.org/repos/dist/dev/maven/maven-4/4.0.0-rc-7/ > > Staging site: > https://maven.apache.org/ref/4-LATEST/ > > Guide to testing staged releases: > https://maven.apache.org/guides/development/guide-testing-releases.html > > Vote open for at least 72 hours. > > [ ] +1 > [ ] +0 > [ ] -1 > > Guillaume Nodet > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
