slachiewicz opened a new issue, #12676:
URL: https://github.com/apache/maven/issues/12676
Maven **4.0.0-rc-6** was released on 2026-07-30. This tracks moving the
repositories that build against a Maven 4 pre-release onto it, so nothing is
left pinned to rc-5 or older.
Each linked PR moves the repository's Maven 4 version property and — where
the repository was relying on the `maven4-version` default in
`maven-gh-actions-shared` — also pins the version explicitly in that
repository's own `maven-verify.yml`, so its CI no longer moves when the shared
default does.
### Shared CI default
| PR | Notes |
|---|---|
| apache/maven-gh-actions-shared#298 | `maven4-version` default rc-5 → rc-6,
base `v4` |
| apache/maven-gh-actions-shared#299 | same change, base `v5` — should land
together with #298 |
### Maven core
| PR | Notes |
|---|---|
| apache/maven#12674 | wrapper job → rc-6 (`master`) |
| apache/maven#12675 | wrapper job → rc-6 (`maven-4.0.x`) |
| apache/maven-mvnd#1714 | `maven.version` + wrapper `distributionUrl` |
| apache/maven-resolver#2027 | `maven4Version` |
| apache/maven-build-cache-extension#520 | `maven4.0` profile |
| apache/maven-executor | pending |
### Plugins and shared components
| PR | Was on |
|---|---|
| apache/maven-clean-plugin#329 | rc-5 |
| apache/maven-deploy-plugin#685 | rc-5 |
| apache/maven-install-plugin#429 | rc-5 |
| apache/maven-archiver#390 | rc-5 |
| apache/maven-filtering#367 | rc-5 |
| apache/maven-compiler-plugin#1104 | rc-4 |
| apache/maven-plugin-tools#1146 | rc-4 |
| codehaus-plexus/plexus-xml#87 | rc-5 (`maven-xml` dependency) |
### CI-only version pins (3.x lines verifying against Maven 4)
| PR | Was on |
|---|---|
| apache/maven-compiler-plugin#1105 | rc-4 |
| apache/maven-mapping#58 | rc-4 |
| apache/maven-shared-io#122 | rc-2 |
## Known blockers
**The Google Cloud mirror of Central has not synced rc-6.**
`apache-maven-4.0.0-rc-6-bin.zip` is a 404 on
`maven-central.storage-download.googleapis.com/maven2` while
`repo.maven.apache.org` serves it, and rc-5 is present on the mirror.
`.github/workflows/maven.yml` pointed the wrapper there via `MVNW_REPOURL`,
which broke the `initial-build` job on both core PRs; they now leave it unset
so the wrapper downloads from Central. Note the same mirror is configured for
dependency resolution in `.github/ci-mimir-session.properties`.
**ASF Jenkins does not have 4.0.0-rc-6 installed.** Raised on
apache/maven-clean-plugin#329 — an INFRA request is needed; it is not fixable
in the repositories.
**apache/maven-jar-plugin** is not included. It cannot move to rc-6 yet:
`maven-testing` is versioned by `${mavenVersion}`, and in rc-6 its
`org.apache.maven.api.plugin.testing` package was relocated to
`org.apache.maven.testing.plugin`. The deprecated shim left behind for
`ProducedArtifactStub` is a bare no-arg subclass, so the five-argument
constructor is gone and `JarMojoTest.jarTestEnvironment` fails — `expected:
<foo> but was: <myGroupId>`. Bisected: passes on rc-4 and rc-5, fails on rc-6.
apache/maven-compiler-plugin#1104 works around the same relocation by moving
its imports to the new package.
**apache/maven-resources-plugin** is not included either, for a different
reason: its IT `MRESOURCES-131` fails, but that break is not from rc-6 — the
same assertion fails on rc-5 (`<skip>true</skip>` set in `pluginManagement` is
not honoured, so `skipped.txt` is written). Its CI stays green today only
because it pins rc-4.
**apache/maven-source-plugin** still targets `4.0.0-beta-3` and is a
migration rather than a bump: `maven-api-meta` and `maven-api-impl` no longer
exist, and `ProjectManager.getCompileSourceRoots`/`getResources` have been
replaced by the `SourceRoot` model, with `attachArtifact` now taking a
`ProducedArtifact`.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
