You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2022/06/24 07:02:00 UTC

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

     [ https://issues.apache.org/jira/browse/MENFORCER-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Konrad Windszus updated MENFORCER-423:
--------------------------------------
    Description: 
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.

  was: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).


> 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).
> I propose the name {{requireDependencyScope}} for the new rule.



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