elharo commented on issue #280: URL: https://github.com/apache/maven-dependency-analyzer/issues/280#issuecomment-4762928565
If developers are not going to try to resolve the ambiguity, then why show it to them at all? Why show them several they won't do anything with? Classpath construction and class loading is reasonably deterministic in the absence of version ranges. It's possible what you're trying to do is better handled by the maven-enforcer-plugin and doesn't belong in the maven-dependency-analyzer at all though I do think there is a real issue here we should look into. I just don't think the right fix is what you're asking for. -- 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]
