maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Osipov (JIRA)" <>
Subject [jira] [Commented] (MSHARED-47) maven-dependency-analyzer finds too many used dependencies
Date Sun, 16 Apr 2017 10:34:42 GMT


Michael Osipov commented on MSHARED-47:

[~hboutemy], this issue still holds true. I have checked the patch: while it looks reasonable
now, it won't work for Java 9 becaue there won't be any JARs in {{java.home/lib}} to scan.
We can take the list you have proposed and check with {{#startsWith()}}. [~mbeerman], what
do you think? Will to rework the patch? I'd go ahead and commit it.

> maven-dependency-analyzer finds too many used dependencies
> ----------------------------------------------------------
>                 Key: MSHARED-47
>                 URL:
>             Project: Maven Shared Components
>          Issue Type: Bug
>          Components: maven-dependency-analyzer
>            Reporter: Matthew Beermann
>            Assignee: Brian Fox
>         Attachments: MNG-3620-maven-dependency-analyzer.patch
> 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...

This message was sent by Atlassian JIRA

View raw message