Maven Reactor Plugin (RETIRED)
  1. Maven Reactor Plugin (RETIRED)
  2. MREACTOR-1

Reactor plugin doesn't work with sibling aggregated modules

    Details

    • Type: Bug Bug
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None
    • Number of attachments :
      0

      Description

      Normally when you have an aggregator POM with a list of <modules>, the element lists out subdirectories of the aggregator, like this:

      <modules>
        <module>foo</module>
        <module>bar</module>
      </modules>
      

      But modules can be anywhere; the module list can declare relative paths to anywhere, like this:

      <modules>
        <module>../foo</module>
        <module>../../bar</module>
      </modules>
      

      Since the reactor plugin currently works by using "mvn --reactor", which only accepts subdirectories, it will silently fail to run these sibling modules.

      Ultimately we should fix this by using the new command line switches available in 2.1. http://docs.codehaus.org/display/MAVEN/Make+Like+Reactor+Mode In the meantime, we'll have to live with it. (Possibly include a warning? error?)

        Issue Links

          Activity

          Hide
          Brett Porter added a comment -

          Maven 2.2.1 includes the reactor options I was referring to: -rf, -pl (and the related -am and -amd). These supercede most of the functionality of the reactor plugin.

          Show
          Brett Porter added a comment - Maven 2.2.1 includes the reactor options I was referring to: -rf, -pl (and the related -am and -amd). These supercede most of the functionality of the reactor plugin.
          Hide
          Nathan Freeling added a comment -

          Using those reactor options runs me right into MNG-4262 which is fixed in a Maven3 release. I'll have to find a workaround until we can move to Maven3.

          Show
          Nathan Freeling added a comment - Using those reactor options runs me right into MNG-4262 which is fixed in a Maven3 release. I'll have to find a workaround until we can move to Maven3.
          Hide
          Benjamin Bentmann added a comment -

          As mentioned in this issue, the workaround is to specify groupId:artifactId instead of the relative paths to denote the projects.

          Show
          Benjamin Bentmann added a comment - As mentioned in this issue, the workaround is to specify groupId:artifactId instead of the relative paths to denote the projects.
          Hide
          Roger Pack added a comment -

          Does this also cause any "nested" modules to fail? like if I have a a/b and a/c/d1 and a/c/d2 it will fail [I think I'm getting that currently "roots differ" with 3.0.3]

          Show
          Roger Pack added a comment - Does this also cause any "nested" modules to fail? like if I have a a/b and a/c/d1 and a/c/d2 it will fail [I think I'm getting that currently "roots differ" with 3.0.3]
          Hide
          Karl-Heinz Marbaise added a comment -

          This plugin is retired. So all issue are being closed.

          Show
          Karl-Heinz Marbaise added a comment - This plugin is retired. So all issue are being closed.

            People

            • Assignee:
              Unassigned
              Reporter:
              Dan Fabulich
            • Votes:
              4 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: