You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "slachiewicz (via GitHub)" <gi...@apache.org> on 2026/09/19 15:09:56 UTC

Re: [I] Understand hamcrest-core 2.2 [maven-dependency-analyzer]

slachiewicz commented on issue #251:
URL: https://github.com/apache/maven-dependency-analyzer/issues/251#issuecomment-5742937792

   The shim is not empty: hamcrest-core 2.2 contains `org/hamcrest/core/deprecated/HamcrestCoreIsDeprecated.class`, so a "no classes → never unused" rule would not apply to it. The two warnings appear because the pin is expressed as a `<dependency>`; with `hamcrest-core:2.2` in `<dependencyManagement>` (or excluded from junit) and `org.hamcrest:hamcrest` declared for the classes in use, neither warning fires and no analyzer change is needed. Could the plugin instead hint at that when a declared-but-unused artifact also appears transitively at another version? That'd be a maven-dependency-plugin message change, not analyzer logic.
   


-- 
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: issues-unsubscribe@maven.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org