-
Bug
-
Resolution: Duplicate
-
Minor
-
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
- duplicates
-
JENKINS-23846 Jenkins Maven support doesn't handle version ranges in parent definitions
-
- Open
-
Just tried the same thing from latest Jenkins ver. 2.19.1, running in Docker. Still same problem, although the error is little more verbose: