This is an automated email from the ASF dual-hosted git repository. ascheman pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/maven-deploy-plugin.git
commit b24f4a2c9ab0525cebe9ebceb67166c079ae0639 Author: Gerd Aschemann <[email protected]> AuthorDate: Wed Jun 17 22:17:49 2026 +0200 Pin maven-xml to ${mavenVersion} for the test classpath maven-plugin-testing-harness 4.0.0-beta-4 transitively pins maven-xml to 4.0.0-rc-3 and pulls in maven-xml-impl 4.0.0-alpha-9, an artifactId that no longer exists from rc-4 onward (the XmlService SPI provider moved into maven-xml itself). The mismatch makes XmlService$Holder fail with "No XmlService implementation found" — the NoClassDefFoundError reported on #632. Override in dependencyManagement so the unit-test JVM picks up the SPI provider that matches the runtime maven-api-xml on the classpath. --- pom.xml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/pom.xml b/pom.xml index cb925ba..024e66b 100644 --- a/pom.xml +++ b/pom.xml @@ -105,6 +105,19 @@ under the License. <artifactId>guava</artifactId> <version>33.6.0-jre</version> </dependency> + <!-- + maven-plugin-testing-harness 4.0.0-beta-4 transitively pins maven-xml to 4.0.0-rc-3 + and pulls in maven-xml-impl 4.0.0-alpha-9 (an artifact ID that no longer exists + from rc-4 onward; the XmlService implementation moved into maven-xml itself). + Pin maven-xml to ${mavenVersion} so the right XmlService provider is on the + test classpath; otherwise Holder.<clinit> fails with + "No XmlService implementation found" and every unit test errors out. + --> + <dependency> + <groupId>org.apache.maven</groupId> + <artifactId>maven-xml</artifactId> + <version>${mavenVersion}</version> + </dependency> </dependencies> </dependencyManagement>
