Maven Invoker Plugin
  1. Maven Invoker Plugin
  2. MINVOKER-50

Filter all POMs that are relevant to the forked build

    Details

    • Type: New Feature New Feature
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.2
    • Fix Version/s: 1.3
    • Labels:
      None
    • Number of attachments :
      0

      Description

      Imagine a multi module project:

      mod2-parent/
        mod1/
          pom.xml
        mod1-parent/
          pom.xml
        mod2/
          pom.xml
        pom.xml  (aggregator of mod1 and mod2)
      

      When the Invoker Plugin is configured to run the build on mod2-parent/pom.xml, i.e. do a reactor build, none of the POMs in the sub directories are filtered, only the reactor root POM is. This makes it hard for those POMs to reference the artifact under test via @pom.version@ or similar. Possible workaround is using system properties but this is cumbersome.

      My initial assumption is we could analyze the executed POM's model and recursively follow modules/parents to locate the other POMs that will participate in the invoked reactor build to filter these, too. This in turn would require to

      • either rewrite all models to reference the interpolated-pom.xml (would require Maven 2.0.9+, see MNG-1493)
      • or simply retain the original file name of the POM which is of couse only possible when cloning the projects

        Issue Links

          Activity

          Hide
          Benjamin Bentmann added a comment -

          Done in r686481.

          Show
          Benjamin Bentmann added a comment - Done in r686481 .

            People

            • Assignee:
              Benjamin Bentmann
              Reporter:
              Benjamin Bentmann
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: