[
https://issues.apache.org/jira/browse/MDEP-804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17534017#comment-17534017
]
Hudson commented on MDEP-804:
-----------------------------
Build succeeded in Jenkins: Maven » Maven TLP » maven-dependency-plugin »
master #22
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-dependency-plugin/job/master/22/
> Allow auto-ignore of all non-test scoped dependencies used only in test scope
> -----------------------------------------------------------------------------
>
> Key: MDEP-804
> URL: https://issues.apache.org/jira/browse/MDEP-804
> Project: Maven Dependency Plugin
> Issue Type: New Feature
> Components: analyze
> Affects Versions: 3.3.0
> Reporter: Henning Schmiedehausen
> Priority: Major
> Labels: pull-request-available
> Fix For: wontfix-candidate
>
>
> Pre-3.2.0, dependencies that were used only in test scope but not declared in
> test scope (most likely declared in compile scope) were accepted by the
> plugin and not flagged as a problem.
> Starting with 3.2.0 (and the current 3.3.0), these are reported with
> "Non-test scoped test only dependencies found". If the scope of the
> dependencies can not be changed (there are many reasons for that in large
> projects), the old behavior can be restored by adding each flagged dependency
> to the "ignoredNonTestScopedDependencies" configuration option in the
> respective project.
> This is, especially in large projects, cumbersome and brittle.
> There should be a boolean flag, "ignoreAllNonTestScoped" that, when set,
> allows ignoring non-test scoped dependencies if they are used only in test
> scope. This flag restores the pre-3.2.0 behavior.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
