[slachiewicz]

Declares the Maven, Resolver and runtime artifacts that each module's classes reference directly but used to get only transitively, so the build no longer depends on what maven-core happens to bring in (javax.inject, SLF4J and Guice reach the compile path only through maven-core 3.x's own dependencies, and maven-plugin-api 4 brings none of Sisu's). Each one was confirmed by a class reference in target/classes or target/test-classes, found with pilot's bytecode analysis.

• maven-resolver-named-locks-hazelcast: maven-resolver-api (test).
• maven-resolver-named-locks-ipc: maven-resolver-api (test).
• maven-resolver-named-locks-redisson: maven-resolver-api (test).
• maven-resolver-supplier-mvn4: maven-api-core (compile).
• maven-resolver-test-http: maven-resolver-util (compile).
• maven-resolver-transport-apache: junit-jupiter-params (test).
• maven-resolver-transport-jdk11: junit-jupiter-params (test).

Part of apache/maven#13749.

---

To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
check one of the following:

• I hereby declare this contribution to be licensed under the Apache License Version 2.0, January 2004
• I hereby declare that I have filed an Apache Individual Contributor License Agreement.

[gnodet-bot]

LGTM. Straightforward declare-what-you-use cleanup — all seven dependency additions are confirmed by direct class references, scopes are correct, and versions are properly managed (reactor BOM for resolver modules, junit-bom for JUnit, ${maven4Version} for maven-api-core). CI green across all platforms.

This review was generated by an AI agent, Hermès on behalf of @gnodet.