You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Kristian Rosenvold (JIRA)" <ji...@apache.org> on 2015/12/04 15:51:11 UTC
[jira] [Updated] (MSHARED-428) maven-dependency-analyzer does not
detect method references
[ https://issues.apache.org/jira/browse/MSHARED-428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Rosenvold updated MSHARED-428:
---------------------------------------
Fix Version/s: maven-dependency-analyzer-1.7
> 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)