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:09:00 UTC
[jira] [Created] (MENFORCER-424) Maven enforcer rule which checks that all dependencies in dependencyManagement don't have an explicit scope set
Konrad Windszus created MENFORCER-424:
-----------------------------------------
Summary: Maven enforcer rule which checks that all dependencies in dependencyManagement don't have an explicit scope set
Key: MENFORCER-424
URL: https://issues.apache.org/jira/browse/MENFORCER-424
Project: Maven Enforcer Plugin
Issue Type: New Feature
Components: Standard Rules
Reporter: Konrad Windszus
Setting the scope in the dependencyManagement is an anti-pattern and may lead to surprising results during classpath creation. Compare also with the discussion in https://github.com/apache/maven-apache-parent/pull/63#discussion_r788361219.
I propose to add a new rule with name {{banDependencyManagementScope}}.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)