[ https://issues.apache.org/jira/browse/MENFORCER-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17559010#comment-17559010 ]
Konrad Windszus commented on MENFORCER-424: ------------------------------------------- Right, so probably such a rule needs a way to allow certain dependencies to have their scope managed. But what about the rule in general, would you accept a PR for adding it to the standard rules? > 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 > Priority: Major > > 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}}. > Probably scope {{import}} should be accepted though, because it is a special > case. -- This message was sent by Atlassian Jira (v8.20.7#820007)