maven tycho eclipse pomless build not working because jenkins expects a pom.xml in all the modules

Johan Compagner

unread,

Mar 30, 2017, 6:58:05 AM3/30/17

to Jenkins Users

Hi,

i am getting this error:

First time build. Skipping changelog.
Parsing POMs
ERROR: Failed to parse POMs
org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:
[ERROR] Child module C:\xxxxx\rhino\org.eclipse.dltk.javascript.rhino\pom.xml of C:\xxxxx\rhino\pom.xml does not exist @ 

	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:1321)
	at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1118)
	at hudson.FilePath.act(FilePath.java:996)
	at hudson.FilePath.act(FilePath.java:974)
	at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.parsePoms(MavenModuleSetBuild.java:980)
	at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:692)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534)
	at hudson.model.Run.execute(Run.java:1728)
	at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:544)
	at hudson.model.ResourceController.execute(ResourceController.java:98)
	at hudson.model.Executor.run(Executor.java:405)

But it is correct that that pom is not there.

This is a eclipse tycho plugin build that is doesn't use poms in all the plugins (only 1 in the parent)

So its a pommless build with Tycho

But it seems that Jenkins wants to really check first the modules and it expects that the pom.xml is there?

I don't want that, Jenkins should just call  "mvn install" (or what ever i targets i set as an arguments/opts)

I am looking through the options but i can't find anything that would disable this scanning.

Johan

khmarbaise

unread,

Mar 30, 2017, 7:37:01 AM3/30/17

to Jenkins Users

Hi,

I assume you are using the Maven Job Type? If so you have to change to Freestyle project type...

Kind regards

Karl Heinz Marbaise

Johan Compagner

unread,

Mar 30, 2017, 7:59:06 AM3/30/17

to Jenkins Users

ah yes that seems to work, that is a bit counter intuitive because they are all full maven projects

(at least from the eclipse/tycho build perspective)

Op donderdag 30 maart 2017 13:37:01 UTC+2 schreef khmarbaise:

khmarbaise

unread,

Mar 30, 2017, 8:17:06 AM3/30/17

to Jenkins Users

The problem is simply related to the fact that running a tycho project you`re using extensions which are defined inside the pom file (tycho-maven-plugin) which handles things different in contradiction to Jenkins which does not load those extensions at all (either via plugins which use extensions:true nor which can be loaded via .mvn/extensions.xml )...And that is causing such problems...

Apart from others things which are sometimes a little bit weird in using the Maven project type...