slachiewicz opened a new issue, #3586: URL: https://github.com/apache/maven-surefire/issues/3586
The 3.x line builds against Maven 3.10.0 (`mavenVersion`) with Resolver 2.0.24 (`resolverVersion`), while maven-surefire-plugin still declares a 3.6.3 prerequisite (`mavenVersion.prerequisite`). Maven 3.10.0, released 2026-09-27, is the first 3.x release that ships Resolver 2 (2.0.24). Maven 3.9.16 ships Resolver 1.9.27. A plugin that declares a 3.6.3 prerequisite but compiles against Resolver 2 assumes a runtime that only Maven 3.10 and 4 provide. maven-surefire-common declares `maven-resolver-util` at compile scope, so Resolver 2 classes are packaged into the plugin artifact. On a Maven 3.9 runtime, which provides Resolver 1.9.27, those classes can shadow the ones the runtime provides. The property reached 3.10.0 through the Dependabot pull request "Bump mavenVersion from 3.9.16 to 3.10.0" (apache/maven-surefire#3501), merged on 2026-10-07. Suggested change, in line with the other Maven 3.x plugin lines: - `mavenVersion` 3.10.0 to 3.9.16 and `resolverVersion` 2.0.24 to 1.9.27, the Resolver that Maven 3.9.16 ships. - Per-artifact Dependabot exclusions in `.github/dependabot.yml` for the core artifacts bound to the property (`maven-core`, `maven-plugin-api`, `maven-model`, `maven-artifact`, `maven-settings`, `maven-embedder`, `maven-resolver-provider`) at `>= 3.10.0`, and `org.apache.maven.resolver:*` at `>= 2.0.0`. The exclusion has to cover every artifact bound to the property, otherwise Dependabot still proposes the bump under the property name. -- 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]
