[
https://issues.apache.org/jira/browse/MSHARED-428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15092501#comment-15092501
]
Anders Hammar commented on MSHARED-428:
---------------------------------------
We should probably document this a bit better. If not to help ourselves in the
future when this solution doesn't work with newer JDK's. Also, it would
probably be good guidance for the end users if we explain expected differences
in result depending on which JDK used (as well as update level when it comes to
Oracle JDK 1.8).
Regarding JDK-7153958 I can't figure out which update it was introduced. I
can't find it being mentioned in the [release notes of Oracle JDK
1.8|http://www.oracle.com/technetwork/java/javase/8all-relnotes-2226344.html].
> maven-dependency-analyzer does not detect method references
> -----------------------------------------------------------
>
> Key: MSHARED-428
> URL: https://issues.apache.org/jira/browse/MSHARED-428
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-dependency-analyzer
> Affects Versions: maven-dependency-analyzer-1.6
> Reporter: Jonathan Haber
> Assignee: Kristian Rosenvold
> Fix For: maven-dependency-analyzer-1.7
>
>
> maven-dependency-analyzer doesn't seem to pick up on method reference usages.
> When using the maven-dependency-plugin, if the only usage of a dependency is
> via a method reference, this causes erroneous unused dependency errors that
> fail our build.
> I updated the maven-dependency-analyzer tests to fail and pushed it to our
> fork:
> https://github.com/HubSpot/maven-shared/commit/d5ffacb808fba01837c644f2045a79eab50fecbf
> Changing from a method reference to a lambda or anonymous class makes the
> test pass again.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
