[jira] [Commented] (MENFORCER-423) Maven enforcer rule which checks that all dependencies have an explicit scope set

["Konrad Windszus (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MENFORCER-423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17558351#comment-17558351 ] 

Konrad Windszus commented on MENFORCER-423:
-------------------------------------------

This was originally developed in the context of https://issues.apache.org/jira/browse/SLING-11410 with source code in https://github.com/apache/sling-maven-enforcer-rules/pull/2, but I think this rule makes sense to be added to the standard rule.
Please give me some feedback before I prepare a PR.

> 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
>            Priority: Major
>
> 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).



--
This message was sent by Atlassian Jira
(v8.20.7#820007)