slachiewicz commented on issue #12521: URL: https://github.com/apache/maven/issues/12521#issuecomment-5418574200
This is fixed by 5ca34f18defd0befc6a077bcf55cedf600c496c3, "Preserve dependency scope in plugin artifacts", which closed #12497. Ran your reproducer at https://github.com/sellersj/example-wsdl-generation against builds of `maven-3.10.x` on either side of that commit, on JDK 11: | Maven | `generate-sources` | | --- | --- | | 3.10.0-rc-1 | `ClassNotFoundException: com.sun.tools.ws.wscompile.WsimportTool` | | `e2c2b82736`, parent of the fix | same `ClassNotFoundException` | | `5ca34f18de`, the fix | passes | | `699160f894`, branch head | passes | Both builds pinned `-DresolverVersion=2.0.21`, so Resolver is constant across them. That the cause is #12497 also fits your own finding: #12497 was raised against `jaxws-maven-plugin` too, and a plugin whose `PluginDescriptor.getArtifacts()` reports a null scope cannot have its classpath assembled correctly. I hit the same regression from a different direction in #12833, where surefire prepended its own test-scoped dependencies to the forked JVM classpath, and it bisects to the same commit. *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]
