[MSHARED-47] maven-dependency-analyzer finds too many used dependencies

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: maven-dependency-analyzer
• Labels: intern
• Flags: Patch
• Assignee: Unassigned
• Reporter: Matthew Beermann
• Created: 10/Jun/08 16:51
• Updated: 09/Sep/23 22:31

Description

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...

Issue Links

• is depended upon by: MDEP-289 Incorrect warning with javax.xml