slachiewicz opened a new issue, #636: URL: https://github.com/apache/maven-parent/issues/636
The Maven 3.x plugin lines build against Maven 3.9.x and stay there: `mavenVersion` points at the latest 3.9.x, `resolverVersion` at the Resolver 1.9.x that the same Maven ships, and Dependabot is kept off the Maven core artifacts (`>= 3.10.0`) and off Resolver 2.x. Maven 3.10.0, released 2026-09-27, is the first 3.x line that ships Resolver 2 (2.0.24); Maven 3.9.16 ships Resolver 1.9.27. A plugin that declares a 3.9.0 prerequisite but builds against Maven 3.10 therefore pulls a Resolver 2 API into a runtime that only has Resolver 1.9. Between 2026-10-03 and 2026-10-11 twenty Dependabot pull requests titled "Bump mavenVersion from 3.9.16 to 3.10.0" were merged across the plugin repositories, moving those lines onto 3.10.0. Six further bump pull requests are still open. Repositories moved onto the 3.10.0 baseline, with the pull request that puts them back: | Repository | Current `mavenVersion` | Pull request | |---|---|---| | maven-antrun-plugin | 3.10.0 (Resolver 2.0.24) | pending | | maven-assembly-plugin | 3.10.0 | pending | | maven-clean-plugin | 3.10.0 | pending | | maven-dependency-analyzer | 3.10.0 | pending | | maven-ear-plugin | 3.10.0 | pending | | maven-enforcer | 3.10.0 | pending | | maven-indexer | 3.10.0 | pending | | maven-invoker-plugin | 3.10.0 | pending | | maven-jar-plugin | 3.10.0 | pending | | maven-jdeps-plugin | 3.10.0 | pending | | maven-jlink-plugin | 3.10.0 | pending | | maven-jmod-plugin | 3.10.0 | pending | | maven-plugin-testing | 3.10.0 (Resolver 2.0.24) | pending | | maven-pmd-plugin | 3.10.0 (Resolver 2.0.24) | pending | | maven-reporting-impl | 3.10.0 (Resolver 2.0.24) | pending | | maven-source-plugin | 3.10.0 | pending | | maven-toolchains-plugin | 3.10.0 | pending | | maven-wrapper | 3.10.0 | pending | | maven-resolver-ant-tasks | 3.10.0 (Resolver 2.0.24) | pending | | maven-surefire | 3.10.0 (Resolver 2.0.24) | pending | maven-resolver-ant-tasks stays on 3.10.0 on purpose: its 2.0.x line is built on Resolver 2 (`maven-resolver-supplier-mvn3` and `maven-resolver-named-locks` do not exist in 1.9.x), and its core artifacts are capped at `>= 3.11.0` instead. Repositories already on the 3.9.x baseline that still need the Dependabot exclusion, because the ignore has to cover every artifact bound to the version property: maven-acr-plugin, maven-changelog-plugin, maven-compiler-plugin (maven-model was missing), maven-deploy-plugin, maven-doap-plugin, maven-install-plugin. Two open Dependabot pull requests are on repositories whose ignore was incomplete: maven-compiler-plugin#1189 and maven-install-plugin#476. Dependabot closes its own bump pull requests once the exclusion is in place. -- 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]
