You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Robert Scholte (Jira)" <ji...@apache.org> on 2020/07/31 10:11:00 UTC
[jira] [Closed] (MENFORCER-354) Enforce no conflicts in
pluginManagement
[ https://issues.apache.org/jira/browse/MENFORCER-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte closed MENFORCER-354.
------------------------------------
Assignee: Robert Scholte
Resolution: Won't Fix
> Enforce no conflicts in pluginManagement
> ----------------------------------------
>
> Key: MENFORCER-354
> URL: https://issues.apache.org/jira/browse/MENFORCER-354
> Project: Maven Enforcer Plugin
> Issue Type: Improvement
> Components: Standard Rules
> Affects Versions: 3.0.0-M3
> Reporter: Konrad Windszus
> Assignee: Robert Scholte
> Priority: Major
>
> Sometimes you inherit from a 3rd party parent which manages certain plugin versions.
> In your own parent (inheriting from the 3rd party parent) you might manage the same plugins to different versions.
> Often this is not done deliberately but rather for historical reason (for a concrete use case look at https://issues.apache.org/jira/browse/SLING-9307). It would be helpful to have a Maven enforcer rule which would enforce that all plugins are only managed once in the pom hierarchy. Optionally one should allow only downgrades or upgrades in the lower level poms.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)