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

ReactorModuleConvergence should better recognize multimodule roots

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

Details

    • Improvement
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • None

    Description

      In case there's an aggregator outside of a multimodule project to trigger one or more multimodules, this rule fails.

      In the code is a valid question: // After we are sure having consistent version we can simply use the first one?

      Most of the time the answer is yes, but not always.

      Attached is an example. 

      Running mvn validate from base-project succeeds, but not from extended-project

      Also notice that base-project is executed before extended-project, however it doesn't seem to be the first of the sorted projects?!

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            rfscholte Robert Scholte

            Dates

              Created:
              Updated:

              Slack

                Issue deployment