delanym commented on issue #280: URL: https://github.com/apache/maven-dependency-analyzer/issues/280#issuecomment-4762987566
I'm coming off a bit harsh on developers. All i'm saying is if the dependency plugin wont even show them the ambiguity then they're just going to tick the checkbox and make the warning go away. And by developers that naturally includes agents too, which will be much more likely to take up the issue of an ambiguous dependency. But not if it doesn't appear in the output. The maven-dependency-plugin's analyze goal should be the go to place to understand whats going on with the dependencies so it should have all the details. I will of course turn on the `banDuplicateClasses` enforcer rule once all the duplicates are actually resolved. Then I'll have no more use for this ability I'm asking for. You say its something to look into - so I take it my part here is done. -- 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]
