Uploaded image for project: 'Maven Deploy Plugin'
  1. Maven Deploy Plugin
  2. MDEPLOY-201

deployAtEnd issue for multi-module projects

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 2.8.1, 2.8.2
    • Fix Version/s: None
    • Component/s: deploy:deploy
    • Labels:
      None

      Description

      There appears to be a bug with the deployAtEnd feature when the maven project includes
      a parent module which is not part of the build.
      Eg: Includes a release parent pom with some standard config.

      The bug is that the code is using the size of the reactorProjects list and this includes
      the parent which isn't in the build process. This is causing the code to not perform any
      deployments at the end because it is expecting to see another module in the build
      sequence so that READYPROJECTSCOUNTER matches the size of the reactorList and this never
      happens.

      A potential solution to this is to look at the MavenSession and get the top level project
      which started the build. Then getting the index position of the top level project in the
      reactorList and subtracting it from the total size of the reactorList will give the
      correct number of expected build modules.

      We have tested these changes locally and the solution appears to work.
      But are currently unsure as to how the testing is done for this project.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                DSzervanszky David Szervanszky
              • Votes:
                4 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                • Created:
                  Updated: