[
https://issues.apache.org/jira/browse/MENFORCER-423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17583006#comment-17583006
]
Hudson commented on MENFORCER-423:
----------------------------------
Build succeeded in Jenkins: Maven » Maven TLP » maven-enforcer » master #67
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-enforcer/job/master/67/
> Maven enforcer rule which checks that all dependencies have an explicit scope
> set
> ---------------------------------------------------------------------------------
>
> Key: MENFORCER-423
> URL: https://issues.apache.org/jira/browse/MENFORCER-423
> Project: Maven Enforcer Plugin
> Issue Type: New Feature
> Components: Standard Rules
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
> Fix For: next-release
>
>
> Useful in case when the scope is no longer part of the dependencyManagement
> or in general to force making developers a distinct decision for every local
> dependency (prevents the default scope compile from being used for test
> dependencies).
> I propose the name {{requireDependencyScope}} for the new rule.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
