slachiewicz commented on issue #12833: URL: https://github.com/apache/maven/issues/12833#issuecomment-5418542885
Bisected. The fixing commit is 5ca34f18defd0befc6a077bcf55cedf600c496c3, "Preserve dependency scope in plugin artifacts", which closed #12497. This report is the same regression seen through surefire, so it can be closed as fixed by that. Results, building each commit from `maven-3.10.x` and running the same test on JDK 11: | commit | result | | --- | --- | | `1f7f1a54` (3.10.0-rc-1) | fails | | `e2c2b82736` (parent of the fix) | fails | | `5ca34f18de` (preserve dependency scope) | passes | | `699160f894` (branch head) | passes | Every build pinned `-DresolverVersion=2.0.21`, so the Resolver version is constant across all four and cannot account for the change. That is also what the earlier jar swap showed from the other direction. The mechanism matches #12497 exactly. With `PluginDescriptor.getArtifacts()` returning a null scope, surefire cannot tell its own test-scoped dependencies apart from the ones it must pass on, so it prepends them to the booter classpath. For surefire 2.22.2 that means Mockito 2.21.0, PowerMock 2.0.0-beta.5, Byte Buddy 1.8.17 and JUnit 4.12 arriving ahead of the project's own Mockito 5.15.2. Worth noting for anyone triaging the other rc-1 reports: #12497 was raised against `jaxws-maven-plugin`, and #12521 is also a `jaxws-maven-plugin` classpath failure on rc-1, so that one may share this root cause. *This comment was created with AI assistance.* -- 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]
