[jira] [Comment Edited] (MSHARED-428) maven-dependency-analyzer does not detect method references

["Anders Hammar (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MSHARED-428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15075039#comment-15075039 ] 

Anders Hammar edited comment on MSHARED-428 at 12/30/15 2:00 PM:
-----------------------------------------------------------------

[~krosenvold] what JDK did you verify with? Two of the new JDK 8 unit tests fail locally for me with Oracle JDK 1.8.0_45 on MacOS.
Update: Tested with 1.8.0_65 and then the unit tests pass. Not good; need to support any patch level I think. JDK 7 support would also be good as we support that for our plugins.


was (Author: afloom):
[~krosenvold] what JDK did you verify with? Two of the new JDK 8 unit tests fail locally for me with Oracle JDK 1.8.0_45 on MacOS.

> 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)