[
https://issues.apache.org/jira/browse/MDEP-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MDEP-152.
-------------------------------
Resolution: Auto Closed
This issue has been auto closed because it has been inactive for a long period
of time. If you think this issue still persists, retest your problem with the
most recent version of Maven and the affected component, reopen and post your
results.
> Analyze main and test dependencies separately
> ----------------------------------------------
>
> Key: MDEP-152
> URL: https://issues.apache.org/jira/browse/MDEP-152
> Project: Maven Dependency Plugin
> Issue Type: Improvement
> Components: analyze
> Affects Versions: 2.0
> Reporter: Benjamin Bentmann
>
> The current design of the maven-dependency-analyzer is mixing apples and
> oranges. If a POM declares an artifact as a compile time dependency but
> actually only requires it for test execution, the analysis would be fine
> because the analyzer ignores scopes.
> Therefore, I suggest to split the analysis and its report into:
> - used declared main dependencies
> - used undeclared main dependencies
> - unused declared main dependencies
> - used declared test dependencies
> - used undeclared test dependencies
> - unused declared test dependencies
> Analysis of the main dependencies would only include "target/classes" and
> artifacts with scope "compile"/"system"/"provided" (similar but not equal to
> ignoreNonCompile=true). Analysis of the test dependencies would consider
> "target/test-classes" and all available artifacts. As a special case, the
> group "unused declared test dependencies" should be post-processed by
> removing all artifacts whose scope is not "test". Otherwise, many of the main
> artifacts would be reported here.
> Finally, a new parameter "excludeTest" should allow to skip the analysis of
> test dependencies.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
