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

["Herve Boutemy (Jira)" <ji...@apache.org>]

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

Herve Boutemy edited comment on MSHARED-428 at 3/22/20, 3:45 PM:
-----------------------------------------------------------------

Fixed in r1717974 / https://github.com/apache/maven-dependency-analyzer/commit/32ee156e231c253f302431c186ecf4173a1e5c52


was (Author: krosenvold):
Fixed in r1717974

> 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
>            Priority: Major
>             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
(v8.3.4#803005)