slachiewicz opened a new pull request, #346: URL: https://github.com/apache/maven-dependency-analyzer/pull/346
Fixes #343. `getUsedDependencyClasses()` and `getUnmappedUsedDependencyClasses()`, both new in 1.18.0, now leave out the project's own classes, JDK classes (including JDK modules on the application class loader, such as `jdk.compiler`) and excluded classes, unless a dependency provides the same class. The project's classes come from the `usedBy` side of the usages, so no extra scan is needed. Verified: `mvn -Prun-its verify` → 158 tests, 24/24 ITs; without the fix the `jarWithCompileDependency` IT reports `java.lang.Object`, `java.lang.String` and the project's own `Project2` as unmapped. I have not run it on JDK 8, where JDK classes are recognized by their jar under `java.home`. -- 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]
