Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-38808

Jenkins fails to parse Maven poms with version ranges in parent elements

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Minor Minor
    • maven-plugin
    • None

      I am running Jenkins 1.651.3, Linux, OracleJava8.
      From within Jenkins I installed Maven 3.3.9 "from Apache".

      In our poms, we are using version ranges in parent elements, as described here. This all builds fine from command line.

      In my Maven build project, if I specify a Pre-Build step that uses the installed Maven, with target "clean install", everything builds fine.

      If in the main build phase I specify target "clean install", the build fails with:

      Parsing POMs
      Failed to transfer Could not find artifact <redacted>:<redacted>:pom:(1.3.0,99.0) in central (http://repo.maven.apache.org/maven2)
      ERROR: Failed to parse POMs
      org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:
      [FATAL] Non-resolvable parent POM: Could not find artifact <redacted>:<redacted>:pom:(1.3.0,99.0) in central (http://repo.maven.apache.org/maven2) and 'parent.relativePath' points at wrong local POM @ line 10, column 10
      

          [JENKINS-38808] Jenkins fails to parse Maven poms with version ranges in parent elements

          Mark Lehky created issue -
          Mark Lehky made changes -
          Description Original: I am running Jenkins 1.651.3, Linux, OracleJava8.
          From within Jenkins I installed Maven 3.3.9 "from Apache".

          In our poms, we are using version ranges in parent elements, as described [here | https://maven.apache.org/docs/3.2.2/release-notes.html#Support_version_ranges_in_parent_elements_MNG-2199].

          In my Maven build project, if I specify a Pre-Build step that uses the installed Maven, with target "clean install", everything builds fine.

          If in the main build phase I specify target "clean install", the build fails with:

          {code}
          Parsing POMs
          Failed to transfer Could not find artifact <redacted>:<redacted>:pom:(1.3.0,99.0) in central (http://repo.maven.apache.org/maven2)
          ERROR: Failed to parse POMs
          org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:
          [FATAL] Non-resolvable parent POM: Could not find artifact <redacted>:<redacted>:pom:(1.3.0,99.0) in central (http://repo.maven.apache.org/maven2) and 'parent.relativePath' points at wrong local POM @ line 10, column 10
          {code}
          New: I am running Jenkins 1.651.3, Linux, OracleJava8.
          From within Jenkins I installed Maven 3.3.9 "from Apache".

          In our poms, we are using version ranges in parent elements, as described [here|https://maven.apache.org/docs/3.2.2/release-notes.html#Support_version_ranges_in_parent_elements_MNG-2199]. This all builds fine from command line.

          In my Maven build project, if I specify a Pre-Build step that uses the installed Maven, with target "clean install", everything builds fine.

          If in the main build phase I specify target "clean install", the build fails with:

          {code}
          Parsing POMs
          Failed to transfer Could not find artifact <redacted>:<redacted>:pom:(1.3.0,99.0) in central (http://repo.maven.apache.org/maven2)
          ERROR: Failed to parse POMs
          org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:
          [FATAL] Non-resolvable parent POM: Could not find artifact <redacted>:<redacted>:pom:(1.3.0,99.0) in central (http://repo.maven.apache.org/maven2) and 'parent.relativePath' points at wrong local POM @ line 10, column 10
          {code}
          Mark Lehky made changes -
          Description Original: I am running Jenkins 1.651.3, Linux, OracleJava8.
          From within Jenkins I installed Maven 3.3.9 "from Apache".

          In our poms, we are using version ranges in parent elements, as described [here|https://maven.apache.org/docs/3.2.2/release-notes.html#Support_version_ranges_in_parent_elements_MNG-2199]. This all builds fine from command line.

          In my Maven build project, if I specify a Pre-Build step that uses the installed Maven, with target "clean install", everything builds fine.

          If in the main build phase I specify target "clean install", the build fails with:

          {code}
          Parsing POMs
          Failed to transfer Could not find artifact <redacted>:<redacted>:pom:(1.3.0,99.0) in central (http://repo.maven.apache.org/maven2)
          ERROR: Failed to parse POMs
          org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:
          [FATAL] Non-resolvable parent POM: Could not find artifact <redacted>:<redacted>:pom:(1.3.0,99.0) in central (http://repo.maven.apache.org/maven2) and 'parent.relativePath' points at wrong local POM @ line 10, column 10
          {code}
          New: I am running Jenkins 1.651.3, Linux, OracleJava8.
          From within Jenkins I installed Maven 3.3.9 "from Apache".

          In our poms, we are using version ranges in parent elements, as described [here|https://maven.apache.org/docs/3.2.2/release-notes.html#Support_version_ranges_in_parent_elements_MNG-2199]. This all builds fine from command line.

          In my Maven build project, if I specify a Pre-Build step that uses the installed Maven, with target "clean install", everything builds fine.

          If in the main build phase I specify target "clean install", the build fails with:

          {noformat}
          Parsing POMs
          Failed to transfer Could not find artifact <redacted>:<redacted>:pom:(1.3.0,99.0) in central (http://repo.maven.apache.org/maven2)
          ERROR: Failed to parse POMs
          org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:
          [FATAL] Non-resolvable parent POM: Could not find artifact <redacted>:<redacted>:pom:(1.3.0,99.0) in central (http://repo.maven.apache.org/maven2) and 'parent.relativePath' points at wrong local POM @ line 10, column 10
          {noformat}
          Mark Lehky made changes -
          Link New: This issue duplicates JENKINS-23846 [ JENKINS-23846 ]
          Mark Lehky made changes -
          Resolution New: Duplicate [ 3 ]
          Status Original: Open [ 1 ] New: Closed [ 6 ]

            Unassigned Unassigned
            siking Mark Lehky
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: