slachiewicz opened a new pull request, #873: URL: https://github.com/apache/maven-shade-plugin/pull/873
Fixes #870. `ArtifactSelector` now records which configured `artifactSet` patterns matched any artifact it was asked about, and the mojo reports the rest after selection: ``` [WARNING] No artifact matching artifactSet include no.such:artifact [INFO] No artifact matching artifactSet exclude no.such:other ``` Unmatched excludes are reported at INFO because an exclude inherited from a parent `pluginManagement` is often legitimately unmatched in a given module. The patterns the selector adds itself, the project's own artifact and the `shadedGroupFilter` prefix, are never reported. Selection results are unchanged: both pattern sets are now always evaluated so that every matching pattern is recorded, but the same artifacts are selected. The existing `No artifact matching filter …` message moves from DEBUG to WARN for the same reason. #849 puts that message behind its new `verbose` option; whichever lands second needs a one-line rebase there. Verified: `-Prun-its verify` → 75 unit tests and 86 ITs pass; none of the existing ITs logs any of these messages, so the new output appears only where a pattern really matches nothing. --- To make clear that you license your contribution under the [Apache License Version 2.0, January 2004](https://www.apache.org/licenses/LICENSE-2.0) check one of the following: - [x] I hereby declare this contribution to be licensed under the [Apache License Version 2.0, January 2004](https://www.apache.org/licenses/LICENSE-2.0) - [x] I hereby declare that I have filed an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). -- 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]
