Affects Version/s: None
Fix Version/s: None
I'll just quote the post from our internal mailing list:
"I don't like that plugin - it has reported dozens of missing dependencies that were unnecessary for me, so I stopped using it. The most common example is when you have a dependency on a project that has a dependency on Xerces, Xalan or some other XML project and your project has java.xml.* imports, which you're resolving from the JDK, it gives a higher priority to external dependencies, even if another project introduces them, than it does to JDK libraries."
I've got a (possible) patch coming up in a few...
|Workflow||jira [ 12963845 ]||Default workflow, editable Closed status [ 13000063 ]|
|Project Import||Mon Apr 06 01:15:59 UTC 2015 [ 1428282959282 ]|
|Patch Submitted||Yes [ 10763 ]|
|Flags||Patch [ 10430 ]|
|Workflow||jira [ 12726058 ]||Default workflow, editable Closed status [ 12764238 ]|
|Project Import||Sun Apr 05 13:14:21 UTC 2015 [ 1428239661755 ]|
|Component/s||maven-dependency-analyzer [ 13265 ]|
|Assignee||Brian Fox [ brianfox ]|
|Field||Original Value||New Value|
|Attachment||MNG-3620-maven-dependency-analyzer.patch [ 35105 ]|