Maven 2 & 3
  1. Maven 2 & 3
  2. MNG-3814

Reactor builds fail due to erroneous cycle in project sorting which does not consider versions

    Details

    • Type: Bug Bug
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.0.9, 2.1.0-M1, 3.0-alpha-1
    • Fix Version/s: 3.0-alpha-3
    • Component/s: Reactor and workspace
    • Labels:
      None
    • Complexity:
      Intermediate
    • Number of attachments :
      0

      Description

      Just to officially track the reason why the parent POM maven-plugins currently excludes the maven-project-info-reports-plugin from the reactor:

      [INFO] Scanning for projects...
      [INFO] ------------------------------------------------------------------------
      [ERROR] BUILD FAILURE
      [INFO] ------------------------------------------------------------------------
      [INFO] The projects in the reactor contain a cyclic reference:
      Edge between
        'Vertex{label='org.apache.maven.plugins:maven-remote-resources-plugin'}'
      and
        'Vertex{label='org.apache.maven.plugins:maven-project-info-reports-plugin'}'
      introduces to cycle in the graph
        org.apache.maven.plugins:maven-project-info-reports-plugin -->
        org.apache.maven.plugins:maven-remote-resources-plugin -->
        org.apache.maven.plugins:maven-project-info-reports-plugin
      

      It appears the ProjectSorter does not take versions into account, i.e. there is no cycle in a multi-module scenario like this:

      parent:1
      - plugin-a:2.0 which uses plugin-b:1.0
      - plugin-b:2.0 which uses plugin-a:1.0
      

        Issue Links

          Activity

          Hide
          Régis Décamps added a comment -

          The problem occurs with any type of dependency. It can be a plugin dependency or a dependency.
          My project fails because
          module-1.1 (uses plugin)> plugin-1.0 (which depends on)> module-1.0

          Show
          Régis Décamps added a comment - The problem occurs with any type of dependency. It can be a plugin dependency or a dependency. My project fails because module-1.1 (uses plugin) > plugin-1.0 (which depends on) > module-1.0
          Hide
          Benjamin Bentmann added a comment -

          Fixed in r798906.

          Show
          Benjamin Bentmann added a comment - Fixed in r798906 .
          Hide
          Julien HENRY added a comment -

          If this is fixed maybe could you revert changes done in aggregator POM maven-plugins.

          Show
          Julien HENRY added a comment - If this is fixed maybe could you revert changes done in aggregator POM maven-plugins.
          Hide
          Benjamin Bentmann added a comment -

          It's fixed only in M3 and the aggregator POM already has a profile for M3 that enables all modules.

          Show
          Benjamin Bentmann added a comment - It's fixed only in M3 and the aggregator POM already has a profile for M3 that enables all modules.

            People

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

              Dates

              • Created:
                Updated:
                Resolved: