[
https://issues.apache.org/jira/browse/MDEP-471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15268798#comment-15268798
]
Jonathan Haber commented on MDEP-471:
-------------------------------------
Ah, I see,
https://github.com/apache/maven-shared/commit/d8404aa19875ce7dc9d912a1f8b65a3b97bfdd08
However, the latest snapshot of maven-dependency-plugin isn't using a snapshot
of maven-dependency-analyzer so it doesn't pick up that commit. Overriding the
maven-dependency-analyzer version to 1.7-SNAPSHOT when declaring the
maven-dependency-plugin does the trick though. But I hit an issue with the
ConstantPoolParser throwing an exception when parsing certain class files. I
tracked it down to some missing code when it was ported from the stack overflow
answer and sent a PR https://github.com/apache/maven-shared/pull/10 with a fix
and a small test change that shows the broken behavior before and the fixed
behavior after.
In the meantime we'll run our fork, but let me know if you want me to make any
changes to the PR, or feel free to close the PR and incorporate the changes in
svn directly since it's pretty trivial.
> Java 8 Method references are not detected
> -----------------------------------------
>
> Key: MDEP-471
> URL: https://issues.apache.org/jira/browse/MDEP-471
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: analyze
> Affects Versions: 2.9
> Environment: Mac OSX
> 13.3.0 Darwin Kernel Version 13.3.0: Tue Jun 3 21:27:35 PDT 2014;
> root:xnu-2422.110.17~1/RELEASE_X86_64 x86_64
> Reporter: Ben Hardy
>
> It is possible to get the depedency plugin to fail to recognize methods
> references.
> For example, the following function declaration is the only place in its
> class where the Guava "Lists" class is referenced (apart from imports):
> public static <V> SequenceMap<String, Character, V> forStringKeys() {
> return new SequenceMap<>(Lists::charactersOf);
> }
> We choose to fail when declared dependencies are thought to be unused, and
> this usage is simply not detected, resulting in the following output and
> exception:
> [WARNING] Unused declared dependencies found:
> [WARNING] com.google.guava:guava:jar:18.0:compile
> [INFO]
> ------------------------------------------------------------------------
> Caused by: org.apache.maven.plugin.MojoExecutionException: Dependency
> problems found
> at
> org.apache.maven.plugin.dependency.analyze.AbstractAnalyzeMojo.execute(AbstractAnalyzeMojo.java:187)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> Will try to get a test and patch attached to this once I figure out where
> your test case class file resources are coming from.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
