Maven
  1. Maven
  2. MNG-2199

Support version ranges in parent elements

    Details

      Description

      It would be great if Maven supports version ranges when specifying parent artifacts in a multi-module build. Currently this does not work.

        <parent>
          <artifactId>artifactId</artifactId>
          <groupId>groupId</groupId>
          <version>[2.0, 2.0.1]</version>
        </parent>
      [INFO] Scanning for projects...
      Downloading: http://repo1.maven.org/maven2/groupId/artifactId/[2.0, 2.0.1]/artifactId-[2.0, 2.0.1].pom

      Additionally it would be great if this

        <parent>
          <artifactId>artifactId</artifactId>
          <groupId>groupId</groupId>
          <version>[2.0, ${pom.version}]</version>
        </parent>
      [INFO] Scanning for projects...
      Downloading: http://repo1.maven.org/maven2/groupId/artifactId/[2.0, ${pom.version}]/artifactId-[2.0, ${pom.version}].pom

      would also work, if the version is specified in the same pom.xml which defines this parent definition.

      1. MNG-2199.patch
        24 kB
      2. MNG-2199.patch
        23 kB
      3. MNG-2199.patch
        16 kB
      4. MNG-2199.patch
        16 kB
      5. MNG-2199.patch
        16 kB
      6. MNG-2199.patch
        10 kB
      7. MNG-2199-3.0.4.patch
        23 kB
      8. MNG-2199-3.0.4.patch
        22 kB
      9. MNG-2199-3.1.0-alpha-1.patch
        29 kB
      10. test-project.zip
        0.6 kB
        Eduardo Souza

        Issue Links

          Activity

          Christian Schulte created issue -
          John Casey made changes -
          Field Original Value New Value
          Fix Version/s 2.1 [ 11704 ]
          Jason van Zyl made changes -
          Fix Version/s 2.1.x [ 13142 ]
          Fix Version/s 2.1 [ 11704 ]
          Brett Porter made changes -
          Link This issue relates to MNG-624 [ MNG-624 ]
          Jason van Zyl made changes -
          Fix Version/s 3.0 [ 13142 ]
          Fix Version/s 3.x [ 13145 ]
          schulte2005 made changes -
          Attachment MNG-2199.patch [ 61306 ]
          schulte2005 made changes -
          Attachment MNG-2199.patch [ 61309 ]
          Paul Benedict made changes -
          Issue Type Bug [ 1 ] Wish [ 5 ]
          schulte2005 made changes -
          Attachment MNG-2199.patch [ 61315 ]
          schulte2005 made changes -
          Attachment MNG-2199.patch [ 61325 ]
          schulte2005 made changes -
          Attachment MNG-2199.patch [ 61722 ]
          schulte2005 made changes -
          Attachment MNG-2199-3.0.4.patch [ 61723 ]
          Jason van Zyl made changes -
          Fix Version/s 3.1.1 [ 18968 ]
          Fix Version/s Issues to be reviewed for 3.x [ 13145 ]
          schulte2005 made changes -
          Attachment MNG-2199.patch [ 61992 ]
          Attachment MNG-2199-3.0.4.patch [ 61993 ]
          schulte2005 made changes -
          Attachment MNG-2199-3.1.0-alpha-1.patch [ 63441 ]
          Jason van Zyl made changes -
          Fix Version/s 3.1.2 [ 18969 ]
          Fix Version/s 3.1.1 [ 18968 ]
          Jason van Zyl made changes -
          Fix Version/s 3.1.2 [ 18969 ]
          Fix Version/s 3.2 [ 15565 ]
          stephenconnolly made changes -
          Fix Version/s 3.2 [ 15565 ]
          Fix Version/s Issues to be reviewed for 4.x [ 19871 ]
          Jason van Zyl made changes -
          Assignee Jason van Zyl [ jason ]
          Hervé Boutemy made changes -
          Description It would be great if Maven supports version ranges when specifying parent artifacts in a multi-module build. Currently this does not work.

            <parent>
              <artifactId>artifactId</artifactId>
              <groupId>groupId</groupId>
              <version>[2.0, 2.0.1]</version>
            </parent>

          [INFO] Scanning for projects...
          Downloading: http://repo1.maven.org/maven2/groupId/artifactId/[2.0, 2.0.1]/artifactId-[2.0, 2.0.1].pom

          Additionally it would be great if this

            <parent>
              <artifactId>artifactId</artifactId>
              <groupId>groupId</groupId>
              <version>[2.0, ${pom.version}]</version>
            </parent>

          [INFO] Scanning for projects...
          Downloading: http://repo1.maven.org/maven2/groupId/artifactId/[2.0, ${pom.version}]/artifactId-[2.0, ${pom.version}].pom

          would also work, if the version is specified in the same pom.xml which defines this parent definition.
          It would be great if Maven supports version ranges when specifying parent artifacts in a multi-module build. Currently this does not work.

          {code:xml} <parent>
              <artifactId>artifactId</artifactId>
              <groupId>groupId</groupId>
              <version>[2.0, 2.0.1]</version>
            </parent>{code}

          {noformat}[INFO] Scanning for projects...
          Downloading: http://repo1.maven.org/maven2/groupId/artifactId/[2.0, 2.0.1]/artifactId-[2.0, 2.0.1].pom{noformat}

          Additionally it would be great if this

          {code:xml} <parent>
              <artifactId>artifactId</artifactId>
              <groupId>groupId</groupId>
              <version>[2.0, ${pom.version}]</version>
            </parent>{code}

          {noformat}[INFO] Scanning for projects...
          Downloading: http://repo1.maven.org/maven2/groupId/artifactId/[2.0, ${pom.version}]/artifactId-[2.0, ${pom.version}].pom{noformat}

          would also work, if the version is specified in the same pom.xml which defines this parent definition.
          Jason van Zyl made changes -
          Summary Version ranges not supported for parent artifacts Support version ranges in parent elements
          Jason van Zyl made changes -
          Fix Version/s 3.2.2 [ 20042 ]
          Fix Version/s Issues to be reviewed for 4.x [ 19871 ]
          Jason van Zyl made changes -
          Status Open [ 1 ] Closed [ 6 ]
          Resolution Fixed [ 1 ]
          Mark Thomas made changes -
          Project Import Sun Apr 05 08:49:45 UTC 2015 [ 1428223785911 ]
          Mark Thomas made changes -
          Workflow jira [ 12712852 ] Default workflow, editable Closed status [ 12752708 ]
          Mark Thomas made changes -
          Project Import Sun Apr 05 21:45:26 UTC 2015 [ 1428270326204 ]
          Mark Thomas made changes -
          Workflow jira [ 12951995 ] Default workflow, editable Closed status [ 12986235 ]
          Mark Thomas made changes -
          Assignee jason lane [ jason ] Jason van Zyl [ jvanzyl ]
          Eduardo Souza made changes -
          Attachment test-project.zip [ 12775588 ]
          Christian Schulte made changes -
          Assignee Jason van Zyl [ jvanzyl ] Christian Schulte [ schulte77 ]

            People

            • Assignee:
              Christian Schulte
              Reporter:
              Christian Schulte
            • Votes:
              26 Vote for this issue
              Watchers:
              33 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development