maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mirko Friedenhagen (JIRA)" <>
Subject [jira] (MSHARED-47) maven-dependency-analyzer finds too many used dependencies
Date Thu, 03 Apr 2014 09:12:00 GMT


Mirko Friedenhagen commented on MSHARED-47:


I like your solution better, two questions come to my mind:
* Is there an official list of the JDK's API packages? I see {{java}}, {{javax}} and maybe
some {{org}} packages, is this really all?
* For your solution do you suggest to put the JDK's api package lists into a shared JAR of
it's own?

I never encountered this, however the issue is quite old so maybe should just drop this.

> 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