Parent pom parsing fails

15 views
Skip to first unread message

JH

unread,
Jan 19, 2011, 9:29:37 AM1/19/11
to Hudson Users
Hi,

Just came across an error which resembles http://issues.hudson-ci.org/browse/HUDSON-8390
though this should be fixed.

We're using a slave hudson version 1.393 . On this we checkout a
complete project with parent-child relations. Then trigger a build on
the child. The parent is only on the local workspace, not in the
private repository of the job. I tried without the relativePath and
with (../pom.xml) which should be correct in both cases. It didn't run
however and currently I fixed this by manually copying a parent pom to
the private repository.

Is this another bug? Or should this have been resolved with the issue
above?

Kind Regards,
Jan

Parsing POMs
ERROR: Failed to parse POMs
hudson.util.IOException2: remote file operation failed: /home/hudson/
workspace/Zoomit-Tools/software at
hudson.remoting.Channel@33854f:zoomit_slave_linux
at hudson.FilePath.act(FilePath.java:752)
at hudson.FilePath.act(FilePath.java:738)
at hudson.maven.MavenModuleSetBuild
$RunnerImpl.parsePoms(MavenModuleSetBuild.java:691)
at hudson.maven.MavenModuleSetBuild
$RunnerImpl.doRun(MavenModuleSetBuild.java:527)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:
417)
at hudson.model.Run.run(Run.java:1362)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:401)
at hudson.model.ResourceController.execute(ResourceController.java:
88)
at hudson.model.Executor.run(Executor.java:145)
Caused by: hudson.remoting.ProxyException:
hudson.maven.MavenModuleSetBuild$MavenExecutionException:
org.apache.maven.project.ProjectBuildingException: Some problems were
encountered while processing the POMs:
[FATAL] Non-resolvable parent POM for be.isabel.zoomit:zoomit_tools:
2.2-SNAPSHOT: Could not find artifact be.isabel.zoomit:zoomit:pom:2.2-
SNAPSHOT @ be.isabel.zoomit:zoomit_tools:2.2-SNAPSHOT, line 7, column
13

at hudson.maven.MavenModuleSetBuild
$PomParser.invoke(MavenModuleSetBuild.java:1145)
at hudson.maven.MavenModuleSetBuild
$PomParser.invoke(MavenModuleSetBuild.java:985)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:1925)
at hudson.remoting.UserRequest.perform(UserRequest.java:114)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:270)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:
417)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
at java.util.concurrent.FutureTask.run(FutureTask.java:123)
at java.util.concurrent.ThreadPoolExecutor
$Worker.runTask(ThreadPoolExecutor.java:651)
at java.util.concurrent.ThreadPoolExecutor
$Worker.run(ThreadPoolExecutor.java:676)
at java.lang.Thread.run(Thread.java:595)
Caused by: hudson.remoting.ProxyException:
org.apache.maven.project.ProjectBuildingException: Some problems were
encountered while processing the POMs:
[FATAL] Non-resolvable parent POM for be.isabel.zoomit:zoomit_tools:
2.2-SNAPSHOT: Could not find artifact be.isabel.zoomit:zoomit:pom:2.2-
SNAPSHOT @ be.isabel.zoomit:zoomit_tools:2.2-SNAPSHOT, line 7, column
13

at
org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:
325)
at hudson.maven.MavenEmbedder.buildProjects(MavenEmbedder.java:360)
at hudson.maven.MavenEmbedder.readProjects(MavenEmbedder.java:330)
at hudson.maven.MavenEmbedder.readProject(MavenEmbedder.java:321)
at hudson.maven.MavenModuleSetBuild
$PomParser.readChilds(MavenModuleSetBuild.java:1184)
at hudson.maven.MavenModuleSetBuild
$PomParser.invoke(MavenModuleSetBuild.java:1107)
... 11 more

olive...@gmail.com

unread,
Jan 19, 2011, 9:33:41 AM1/19/11
to hudson...@googlegroups.com
Hello,
Can you please try with 1.394.
If it's not fixed please open an issue with a sample project to reproduce this.

Thanks,
--
Olivier

Jan Hoskens

unread,
Jan 24, 2011, 2:56:35 AM1/24/11
to hudson...@googlegroups.com
I had to wait a while to update to the latest version, but it seems to be resolved now. The private repository doesn't contain the parent, though the build runs fine now. (as it should be, parent is in the local workspace)

Thanks,

Jan
Reply all
Reply to author
Forward
0 new messages