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 2020/04/07 21:07:00 UTC

[jira] [Created] (MENFORCER-354) Enforce no conflicts in pluginManagement

Konrad Windszus created MENFORCER-354:
-----------------------------------------

             Summary: 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


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)