Uploaded image for project: 'Maven Enforcer Plugin'
  1. Maven Enforcer Plugin
  2. MENFORCER-354

Enforce no conflicts in pluginManagement

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: 3.0.0-M3
    • Fix Version/s: None
    • Component/s: Standard Rules
    • Labels:
      None

      Description

      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.

        Attachments

        Issue Links

          Activity

            People

            • Assignee:
              rfscholte Robert Scholte
              Reporter:
              kwin Konrad Windszus

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment