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

14 views
Skip to first unread message

mark.lehky@gmail.com (JIRA)

unread,
Oct 6, 2016, 10:20:01 PM10/6/16
to jenkinsc...@googlegroups.com
Mark Lehky created an issue
 
Jenkins / Bug JENKINS-38808
Jenkins fails to parse Maven poms with version ranges in parent elements
Issue Type: Bug Bug
Assignee: Unassigned
Components: maven-plugin
Created: 2016/Oct/07 2:19 AM
Priority: Minor Minor
Reporter: Mark Lehky

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 .

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
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
Atlassian logo

mark.lehky@gmail.com (JIRA)

unread,
Oct 8, 2016, 5:54:04 PM10/8/16
to jenkinsc...@googlegroups.com
Mark Lehky updated an issue
Change By: Mark Lehky
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@gmail.com (JIRA)

unread,
Oct 8, 2016, 5:56:01 PM10/8/16
to jenkinsc...@googlegroups.com
Mark Lehky updated an issue
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 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
{ code noformat }

mark.lehky@gmail.com (JIRA)

unread,
Oct 8, 2016, 5:58:01 PM10/8/16
to jenkinsc...@googlegroups.com
Mark Lehky commented on Bug JENKINS-38808
 
Re: Jenkins fails to parse Maven poms with version ranges in parent elements

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:

Parsing POMs
Failed to transfer Could not find artifact <redacted>:<redacted>:pom:(1.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.0,99.0) in central (http://repo.maven.apache.org/maven2) and 'parent.relativePath' points at wrong local POM @ line 10, column 10

	at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:364)
	at hudson.maven.MavenEmbedder.buildProjects(MavenEmbedder.java:361)
	at hudson.maven.MavenEmbedder.readProjects(MavenEmbedder.java:331)
	at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1301)
	at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1098)
	at hudson.FilePath.act(FilePath.java:1018)
	at hudson.FilePath.act(FilePath.java:996)
	at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.parsePoms(MavenModuleSetBuild.java:960)
	at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:679)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534)
	at hudson.model.Run.execute(Run.java:1720)
	at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531)
	at hudson.model.ResourceController.execute(ResourceController.java:98)
	at hudson.model.Executor.run(Executor.java:404)

mark.lehky@gmail.com (JIRA)

unread,
Oct 8, 2016, 6:02:03 PM10/8/16
to jenkinsc...@googlegroups.com
Mark Lehky closed an issue as Duplicate
 

should have done better search
Change By: Mark Lehky
Status: Open Closed
Resolution: Duplicate
Reply all
Reply to author
Forward
0 new messages