slachiewicz opened a new pull request, #1751: URL: https://github.com/apache/maven-dependency-plugin/pull/1751
These three goals now ask Maven only to collect the dependency graph, apply `includeScope` and the other filters, and then resolve just the artifacts that are left. A provided- or test-scope module of the same reactor that has not been built no longer fails the build when the filters exclude it. `resolve`, `build-classpath`, `list` and the other goals keep Maven's up-front resolution; the change sits behind a hook in `AbstractDependencyFilterMojo` that only these three enable. With a classifier and `failOnMissingClassifierArtifact=false`, an original that cannot be resolved is logged and left out instead of reaching the overwrite checks without a file. Fixes #1255, fixes #1402. Release note: copy-dependencies, unpack-dependencies and resolve-sources no longer fail on dependencies that their include and exclude filters drop, such as unbuilt provided- or test-scope modules of the same reactor. Verified: the two new ITs fail on master with "Could not resolve dependencies"; full IT suite on Maven 3.9.16 → 116 passed (before the null-file guard; 8 related ITs rerun after it); new ITs pass on 4.0.0-rc-7. -- 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]
