slachiewicz opened a new issue, #343:
URL: https://github.com/apache/maven-dependency-analyzer/issues/343

   `getUnmappedUsedDependencyClasses()`, added in 1.18.0, returns every 
referenced class that no dependency artifact provides 
([ProjectDependencyAnalysis.java:279](https://github.com/apache/maven-dependency-analyzer/blob/master/src/main/java/org/apache/maven/shared/dependency/analyzer/ProjectDependencyAnalysis.java#L279)).
 The referenced classes are not filtered, so the result also contains JDK 
classes and the classes of the analyzed project itself. Running 
`ASMDependencyAnalyzer.analyzeUsages` on this repository's own `target/classes` 
gives 168 referenced classes, including `java.lang.Object` and 
`org.apache.maven.shared.dependency.analyzer.DependencyUsage`.
   
   As it stands, a consumer cannot use the method to find classes that a 
missing dependency would provide without filtering out both groups itself.
   
   Expected: leave out the project's own main and test classes and JDK classes, 
or document that the caller has to.
   


-- 
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]

Reply via email to