Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 346428

Summary:	Cannot find layout implementation corresponding to: 'p2'
Product:	Community	Reporter:	Vincent Zurczak <vincent.zurczak>
Component:	CI-Jenkins	Assignee:	Eclipse Webmaster <webmaster>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	denis.roy, vincent.zurczak
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:	stalebug

Description Vincent Zurczak

2011-05-19 08:19:40 EDT

Hi,

Our last Hudson job (tycho-soa.sca.trunk-release) is supposed to run with Maven and Tycho.
Unfortunately, this job fails all the time with the same error:

Parsing POMs
ERROR: Failed to parse POMs
org.apache.maven.project.ProjectBuildingException: Cannot find layout implementation corresponding to: 'p2' for remote repository with id: 'eclipse-repository'. for project org.eclipse.soa.sca:org.eclipse.soa.sca.parent.pom
	at org.apache.maven.project.DefaultMavenProjectBuilder.buildArtifactRepositories(DefaultMavenProjectBuilder.java:951)
	at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1144)
	at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:821)
	at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:506)
	at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:215)
	at hudson.maven.MavenEmbedder.readProject(MavenEmbedder.java:332)
	at hudson.maven.MavenUtil.resolveModules(MavenUtil.java:226)
	at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:970)
	at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:859)
	at hudson.FilePath.act(FilePath.java:753)
	at hudson.FilePath.act(FilePath.java:735)
	at hudson.maven.MavenModuleSetBuild$RunnerImpl.parsePoms(MavenModuleSetBuild.java:587)
	at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:464)
	at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:417)
	at hudson.model.Run.run(Run.java:1337)
	at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:349)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:140)
Caused by: org.apache.maven.artifact.InvalidRepositoryException: Cannot find layout implementation corresponding to: 'p2' for remote repository with id: 'eclipse-repository'.
	at org.apache.maven.project.ProjectUtils.getRepositoryLayout(ProjectUtils.java:147)
	at org.apache.maven.project.ProjectUtils.buildArtifactRepository(ProjectUtils.java:100)
	at org.apache.maven.project.ProjectUtils.buildArtifactRepositories(ProjectUtils.java:56)
	at org.apache.maven.project.DefaultMavenProjectBuilder.buildArtifactRepositories(DefaultMavenProjectBuilder.java:944)
	... 17 more
Caused by: org.codehaus.plexus.component.repository.exception.ComponentLookupException: Component descriptor cannot be found in the component repository: org.apache.maven.artifact.repository.layout.ArtifactRepositoryLayoutp2.
	at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:323)
	at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:440)
	at org.apache.maven.project.ProjectUtils.getRepositoryLayout(ProjectUtils.java:143)
	... 20 more

We have another Hudson job (tycho-soa.sca.trunk-integration) which is based on Tycho too and which works correctly (same POM and same parameters to compare). When I look at the internet about this error, it is said that it is due to a wrong Maven version (Maven2 instead of Maven3). But the job is configured to run with Maven 3.0.3.

And another weird thing is that the configuration pages for the two jobs are slightly different (not exactly the same options, not exactly the same labels). Maybe this difference is related to the error above.

I have also changed the root POM to be as much simple as possible (it only displays the M2_HOME variable). It works on my machine but not on Hudson. Instead, there is the following error.

Parsing POMs
[workspace] $ java -Dhttp.proxyHost=proxy.eclipse.org -Dhttp.proxyPort=9898 -Dhttps.proxyHost=proxy.eclipse.org -Dhttps.proxyPort=9898 -Dhttp.nonProxyHosts=*.eclipse.org -Dhttps.nonProxyHosts=*.eclipse.org -cp /opt/users/hudsonbuild/.hudson/plugins/maven-plugin/WEB-INF/lib/maven-agent-1.389.jar:/shared/common/apache-maven-3.0.3/boot/plexus-classworlds-2.4.jar hudson.maven.agent.Main /shared/common/apache-maven-3.0.3 /opt/users/hudsonbuild/.hudson/war/WEB-INF/lib/remoting-1.389.jar /opt/users/hudsonbuild/.hudson/plugins/maven-plugin/WEB-INF/lib/maven-interceptor-1.389.jar 53760
Exception in thread "main" java.lang.NoSuchMethodError: org.codehaus.classworlds.Launcher.getWorld()Lorg/codehaus/classworlds/ClassWorld;
	at hudson.maven.agent.Main.main(Main.java:115)
	at hudson.maven.agent.Main.main(Main.java:62)
ERROR: Failed to launch Maven. Exit code = 1

Comment 1 Eclipse Webmaster

2011-05-19 09:56:06 EDT

Since you indicated that this was a maven based build I used the Maven job template in hudson(instead of a free software template).  That would explain the differing config options.  I don't have a way to convert job types but I can delete the job and re-create it with a different template.

-M.

Comment 2 Vincent Zurczak

2011-05-19 10:05:26 EDT

> I don't have a way to convert job types but I
> can delete the job and re-create it with a different template.

Let's do that then.

Comment 3 Eclipse Webmaster

2011-05-19 11:54:52 EDT

Ok I've recreated the job.

-M.

Comment 4 Vincent Zurczak

2011-05-19 13:02:21 EDT

Thanks, it works now. :) 

Either it was me who made a mistake in the configuration or there might be a problem with the default Maven configuration. I cannot say.

Comment 5 Eclipse Genie

2014-10-17 15:10:15 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.

Comment 6 Denis Roy

2014-10-21 15:38:21 EDT

Seems like this was fixed.