[
https://jira.codehaus.org/browse/MSHARED-47?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=350038#comment-350038
]
Jerrimiah Nance edited comment on MSHARED-47 at 7/21/14 4:27 AM:
-----------------------------------------------------------------
I'm kind of surprised, that this doesn't bother more people.
failOnWarning
(http://maven.apache.org/plugins/maven-dependency-plugin/analyze-mojo.html#failOnWarning)
is pretty useless if builds constantly fail because of incorrectly identified
dependencies.
h4. Example
I have to depend on large legacy projects that I can't really modify. Most of
these projects have dependencies on, for instance
{code}
<dependency>
<groupId>xml-apis</groupId>
<artifactId>xml-apis</artifactId>
<version>1.3.04</version>
</dependency>
{code}
In my own code, I reference
{monospaced}javax.xml.transform.Transformer{monospaced}.
When calling {monospaced}mvn dependency:analyze{monospaced}, maven will bug me
that xml-apis is used, but undeclared.
Until this is fixed _"officially"_, I am using a patched version of
maven-dependency-analyzer (using the patch attached to this issue)
was (Author: jerrimiah):
I'm kind of surprised, that this doesn't bother more people.
failOnWarning
(http://maven.apache.org/plugins/maven-dependency-plugin/analyze-mojo.html#failOnWarning)
is pretty useless if builds constantly fail because of incorrectly identified
dependencies.
h4. Example
I have to depend on large legacy projects that I can't really modify. Most of
these projects have dependencies on, for instance
{code}
<dependency>
<groupId>xml-apis</groupId>
<artifactId>xml-apis</artifactId>
<version>1.3.04</version>
</dependency>
{code}
In my own code, I reference
{{monospaced}}javax.xml.transform.Transformer{{monospaced}}.
When calling {{monospaced}}mvn dependency:analyze{{monospaced}}, maven will bug
me that xml-apis is used, but undeclared.
Until this is fixed _"officially"_, I am using a patched version of
maven-dependency-analyzer (using the patch attached to this issue)
> maven-dependency-analyzer finds too many used dependencies
> ----------------------------------------------------------
>
> Key: MSHARED-47
> URL: https://jira.codehaus.org/browse/MSHARED-47
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-dependency-analyzer
> Reporter: Matthew Beermann
> Assignee: brianfox brianfox
> 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
(v6.1.6#6162)
