[
https://issues.apache.org/jira/browse/MDEP-714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17461936#comment-17461936
]
Lars Knickrehm commented on MDEP-714:
-------------------------------------
[~mirabilos], in general it makes sense to analyze the test scoped
dependencies, as it's likely they are used within the test classes. Instead
runtime scoped dependencies are most likely dependencies, which are not
referenced directly, but loaded aside.
In the case of the JUnit engine it'd be cool to have some kind of test-runtime
scope, which does not seem to exist. Therefore I'm simply ignoring those
dependencies the way you described in my projects, too.
If you find a better solution, I'd be interested, too.
> Add analyze parameter "ignoreUnusedRuntime"
> -------------------------------------------
>
> Key: MDEP-714
> URL: https://issues.apache.org/jira/browse/MDEP-714
> Project: Maven Dependency Plugin
> Issue Type: New Feature
> Components: analyze
> Reporter: Elliotte Rusty Harold
> Assignee: Michael Osipov
> Priority: Major
> Fix For: 3.2.0
>
>
> Typical output when analyzing the maven-archetype-plugin:
> [WARNING] Unused declared dependencies found:
> [WARNING] org.apache.ivy:ivy:jar:2.5.0:runtime
> However since this is needed at runtime, possibly via reflection, it seems
> likely that it is used but the dependency analyzer can't figure this out.
> Confirm and consider whether the plugin should simply never report runtime
> dependencies as unused.
> This is tricky because it's certainly possible that a runtime dependency is
> unused, but in practice it seems more likely than not to be a false positive.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
