delanym opened a new issue, #280: URL: https://github.com/apache/maven-dependency-analyzer/issues/280
### New feature, improvement proposal AI DISCLAIMER: https://gemini.google.com/share/dd9579182da4 Currently, ProjectDependencyAnalyzer immediately aggregates scanned bytecode data into Set<Artifact>. When un-relocated classes exist across duplicate artifacts or fat-jars on the classpath, the artifact-guessing step yields false positives that are impossible for upstream plugins to filter cleanly. We need an option or an extended analysis result (e.g., a getUnmappedPackages() or passing a raw Set<String> of used types) that records the raw bytecode types detected for which no explicit top-level dependency exists before trying to associate them with a specific GAV coordinate loop. -- 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]
