I have to correct myself. It's not working both on Windows and on Linux. The working job I've seen on Windows wasn't a real Maven job but a free-style job with a Maven build step (and that's invoked with mvn.bat).

Any updates on the issue?

There is a bug in maven 2.x which is only fixed in maven 3.0
<profile><activation><file><exists/> does not work in a multi-project build
http://jira.codehaus.org/browse/MNG-2363
With this bug there not a working combination of maven and hudson that can use a file for activating a profile in a multi-module project

Maven 3 has a new build plan and lifecycle API that would be a better option for integration in Hudson.

This issue becomes a little more pressing now as maven 3 is officially released.

Just tried to move to official release of Maven 3.0 and finding Hudson 1.380 with java 6 on Linux (multiproject pom) does not work. All my hudson plugins are also updated to the latest releases.

My job output:

Parsing POMs
[modules] $ /home/foo/hudson/tools/bin/java -cp /home/foo/hudson/plugins/maven-plugin/WEB-INF/lib/maven-agent-1.380.jar:/home/foo/apache-maven-3.0/boot/plexus-classworlds-2.2.3.jar hudson.maven.agent.Main /home/foo/apache-maven-3.0 /home/foo/hudson/war/WEB-INF/lib/remoting-1.380.jar /home/foo/hudson/plugins/maven-plugin/WEB-INF/lib/maven-interceptor-1.380.jar 53698
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)
Terminating xvnc.
$ vncserver -kill :10
Killing Xvnc process ID 13366
ERROR: Failed to launch Maven. Exit code = 1

If you web search for "Exception in thread "main" java.lang.NoSuchMethodError: org.codehaus.classworlds.Launcher.getWorld" you will see other people are hitting this too.

The same project builds fine from the command line with "mvn install" on the the same Linux server using the same maven 3.0 and java version.

olamy,

I see this issue does not have a fix version. Any idea when when might see Maven 3 support in Hudson?

I have a workaround for that problem. If you use a "Freestyle project" instead of a Maven2 project you can use Maven 3.

I have started to work on this.
Please note : Personnally I work on this during my spare time, so no real timeframe.

olamy,

Thanks for the communication and the hard work you put into this. We all really appreciate it!

I guess your work is in http://github.com/olamy/hudson-maven3-support/commits/master.
From http://github.com/olamy/hudson-maven3-support/blob/master/README it looks like a separate plugin.
Can it live happily side by side the default maven(2) support in hudson?

yup the goal is to be user friendly (no new plugin : that's the challenge !)

Code changed in hudson
User: : olamy
Path:
trunk/hudson/lib/maven-embedder/pom.xml
trunk/hudson/lib/maven-embedder/src/main/java/hudson/maven/MavenEmbedder.java
trunk/hudson/lib/maven-embedder/src/main/java/hudson/maven/MavenEmbedderException.java
trunk/hudson/lib/maven-embedder/src/main/java/hudson/maven/MavenRequest.java
trunk/hudson/lib/maven-embedder/src/test/java/hudson/maven/TestMavenEmbedderSimpleProject.java
trunk/hudson/lib/maven-embedder/src/test/projects-tests/one-module/pom.xml
trunk/hudson/lib/maven-embedder/src/test/projects-tests/one-module/src/main/java/com/mycompany/app/App.java
trunk/hudson/lib/maven-embedder/src/test/projects-tests/one-module/src/test/java/com/mycompany/app/AppTest.java
http://jenkins-ci.org/commit/36159
Log:
JENKINS-4988 pushing some jobs on embedder version using maven 3 apis

Should a maven-plugin configuration option be exposed which disables the M3 support? Since we will only have one plugin which builds Maven projects for all Maven releases, perhaps it would be useful to provide a mechanism for disabling the new support code path..

If we agree that a kill switch should be exposed, what should its default value be?

nice idea, but is a configuration element for that really necessary? From a user point of view, I want the plugin to work, not depending on which version of Maven I'm using. The design decision was that the plugin works with both versions. Isn't it possible to derive necessary information from the context (Maven version), in order to switch some parts of the implementation?

I think Oliver would need to comment what is and is not possible, but I just think that if we break everyone's working M2 jobs because of some regression while enabling M3 support.... it would be very, very bad.

Uhm, As we have planned to move the embedder to maven 3 apis.
All the embedder part will be upgraded using this new versions.
So having such option will be impossible IMHO.
BTW I will work in a branch so some people will be able to test the change.

It's worth mentioning that Maven 3 is supposed to be backwards-compatible with Maven 2 , within the limits noted at https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html . Perhaps that should somehow be communicated to the users?

Uhm some core (internal) maven apis are not compatible.
And some are used in the hudson maven plugin (exemple DefaultPluginManager which has changed)

In reply to comment #18:
> Uhm some core (internal) maven apis are not compatible.
> And some are used in the hudson maven plugin (exemple DefaultPluginManager which
> has changed)

I meant that for the Hudson users things will probably not break when the Maven 3 support comes out. For plugin developers it's a different business altogether.

Code changed in hudson
User: : olamy
Path:
branches/main-maven3-support/core/pom.xml
branches/main-maven3-support/core/src/main/java/hudson/PluginManager.java
branches/main-maven3-support/maven-agent/pom.xml
branches/main-maven3-support/maven-agent/src/main/java/hudson/maven/agent/Main.java
branches/main-maven3-support/maven-agent/src/main/resources/hudson/maven/agent/classworlds-2.0.6.conf
branches/main-maven3-support/maven-agent/src/main/resources/hudson/maven/agent/classworlds.conf
branches/main-maven3-support/maven-interceptor/pom.xml
branches/main-maven3-support/maven-interceptor/src/main/java/hudson/maven/agent/DefaultPluginManager.java
branches/main-maven3-support/maven-interceptor/src/main/java/hudson/maven/agent/PluginManagerInterceptor.java
branches/main-maven3-support/maven-plugin/pom.xml
branches/main-maven3-support/maven-plugin/src/main/java/hudson/maven/AbstractMavenBuilder.java
branches/main-maven3-support/maven-plugin/src/main/java/hudson/maven/EmbedderLoggerImpl.java
branches/main-maven3-support/maven-plugin/src/main/java/hudson/maven/Maven3Builder.java
branches/main-maven3-support/maven-plugin/src/main/java/hudson/maven/Maven3ProcessFactory.java
branches/main-maven3-support/maven-plugin/src/main/java/hudson/maven/MavenBuilder.java
branches/main-maven3-support/maven-plugin/src/main/java/hudson/maven/MavenComputerListener.java
branches/main-maven3-support/maven-plugin/src/main/java/hudson/maven/MavenModuleSetBuild.java
branches/main-maven3-support/maven-plugin/src/main/java/hudson/maven/MavenProcessFactory.java
branches/main-maven3-support/maven-plugin/src/main/java/hudson/maven/MavenUtil.java
branches/main-maven3-support/maven-plugin/src/main/java/hudson/maven/MavenVersionCallable.java
branches/main-maven3-support/maven-plugin/src/main/java/hudson/maven/MojoInfo.java
branches/main-maven3-support/maven-plugin/src/main/java/hudson/maven/RedeployPublisher.java
branches/main-maven3-support/maven-plugin/src/main/java/hudson/maven/reporters/MavenAbstractArtifactRecord.java
branches/main-maven3-support/maven-plugin/src/main/java/hudson/maven/reporters/MavenAggregatedArtifactRecord.java
branches/main-maven3-support/maven-plugin/src/main/java/hudson/maven/reporters/MavenArtifact.java
branches/main-maven3-support/maven-plugin/src/main/java/hudson/maven/reporters/MavenArtifactRecord.java
branches/main-maven3-support/maven3-agent/.gitignore
branches/main-maven3-support/maven3-agent/pom.xml
branches/main-maven3-support/maven3-agent/src/main/java/org/jvnet/hudson/maven3/agent/Maven3Main.java
branches/main-maven3-support/maven3-agent/src/main/java/org/jvnet/hudson/maven3/agent/RealFilterOutputStream.java
branches/main-maven3-support/maven3-agent/src/main/resources/org/jvnet/hudson/maven3/agent/classworlds.conf
branches/main-maven3-support/maven3-listener/.gitignore
branches/main-maven3-support/maven3-listener/pom.xml
branches/main-maven3-support/maven3-listener/src/main/java/org/apache/maven/cli/DefaultMavenExecutionRequestBuilder.java
branches/main-maven3-support/maven3-listener/src/main/java/org/apache/maven/cli/MavenExecutionRequestBuilder.java
branches/main-maven3-support/maven3-listener/src/main/java/org/apache/maven/cli/MavenExecutionRequestsBuilderException.java
branches/main-maven3-support/maven3-listener/src/main/java/org/jvnet/hudson/maven3/launcher/Maven3Launcher.java
branches/main-maven3-support/maven3-listener/src/main/java/org/jvnet/hudson/maven3/listeners/HudsonMavenExecutionResult.java
branches/main-maven3-support/maven3-listener/src/main/java/org/jvnet/hudson/maven3/listeners/MavenProjectBuildResult.java
branches/main-maven3-support/maven3-listener/src/main/java/org/jvnet/hudson/maven3/listeners/MavenProjectInfo.java
branches/main-maven3-support/pom.xml
branches/main-maven3-support/remoting/src/main/java/hudson/remoting/UserRequest.java
branches/main-maven3-support/test/src/main/java/org/jvnet/hudson/test/HudsonTestCase.java
http://jenkins-ci.org/commit/36643
Log:
JENKINS-4988 push some stuff
to be able to get in an other place (sure git could be better )
some issue when using maven 2
some stuff to do more in maven 3 build (recording mojo execution etc...)

Code changed in hudson
User: : olamy
Path:
branches/main-maven3-support/maven-plugin/src/main/java/hudson/maven/Maven3Builder.java
branches/main-maven3-support/maven-plugin/src/main/java/hudson/maven/MavenBuilder.java
branches/main-maven3-support/maven-plugin/src/main/java/hudson/maven/MavenModuleSetBuild.java
branches/main-maven3-support/maven3-listener/src/main/java/org/jvnet/hudson/maven3/launcher/Maven3Launcher.java
branches/main-maven3-support/maven3-listener/src/main/java/org/jvnet/hudson/maven3/listeners/HudsonMavenBuildHelper.java
http://jenkins-ci.org/commit/36677
Log:
JENKINS-4988 push some stuff to work in other laptop.

Code changed in hudson
User: : olamy
Path:
branches/main-maven3-support/maven-plugin/src/main/java/hudson/maven/Maven3Builder.java
branches/main-maven3-support/maven-plugin/src/main/java/hudson/maven/MavenModuleSetBuild.java
branches/main-maven3-support/maven3-listener/src/main/java/org/jvnet/hudson/maven3/launcher/Maven3Launcher.java
branches/main-maven3-support/maven3-listener/src/main/java/org/jvnet/hudson/maven3/listeners/HudsonMavenBuildHelper.java
http://jenkins-ci.org/commit/36682
Log:
JENKINS-4988 cleanup stuff which failed in previous commit.

Code changed in hudson
User: : olamy
Path:
branches/main-maven3-support/maven-plugin/src/main/java/hudson/maven/Maven3Builder.java
http://jenkins-ci.org/commit/36695
Log:
JENKINS-4988 implements more MavenReporter call.
still work in progress ....

Code changed in hudson
User: : olamy
Path:
branches/main-maven3-support/maven-plugin/src/main/java/hudson/maven/Maven3Builder.java
http://jenkins-ci.org/commit/36728
Log:
JENKINS-4988 reccord ExecutedMojos after each mojo execution end.

Nice to see some progress on this issue.

If you need some (early) testing of the Maven integration with Maven 3, I would be glad offer my help. In that case, tell whenever there's something worth to be tried out.

Code changed in hudson
User: : olamy
Path:
branches/main-maven3-support/maven-plugin/src/main/java/hudson/maven/Maven3Builder.java
http://jenkins-ci.org/commit/36742
Log:
JENKINS-4988 mark maven module as finished and recording build time.

Code changed in hudson
User: : olamy
Path:
branches/main-maven3-support/maven-plugin/src/main/java/hudson/maven/Maven3Builder.java
http://jenkins-ci.org/commit/36743
Log:
JENKINS-4988 fix mark maven module as finished and recording build time. record skipped project too

Since issue type has been changed, for consistency issue name should be changed as well.

Is this issue progressing anyhow?

It will make a huge difference for a lot of people.

Some stuff has been done here : https://hudson.dev.java.net/svn/hudson/branches/main-maven3-support/
The main issue currently is maven 2 builds doesn't work anymore .
ATM I don't have time (not before 1 or 2 weeks).
I hope someone will take time to review.

Seeing if this issue is still active. Maven3 has been released for two months now. Would be interested in looking at the new work to try to test or help but the links appear to be bad.

https://svn.java.net/svn/hudson~svn/branches/main-maven3-support/ is the new path to the SVN URL that olamy posted above

I discovered, quite by accident, that the Artifactory plugin has some Maven3 support for free style builds, and thats working for me.

The stuff is available in git https://github.com/hudson/hudson in branch called main-maven3-support.
Currently there are still issues using maven 2 but works with maven 3.
If you have the patch to fix maven 2 support, I will be happy to push it

>>The stuff is available in git https://github.com/hudson/hudson in branch called main-maven3-support.
I got it and tried to build but unfortunately a build doesn't work:
It couldn't find the artifact rg.jvnet.hudson:maven-embedder:jar:3.0-SNAPSHOT

-----------------------------------------------------------------------------------------
Path to dependency:
1) org.jvnet.hudson.main:maven-plugin:hpi:1.389-SNAPSHOT
2) org.jvnet.hudson:maven-embedder:jar:3.0-SNAPSHOT

----------
1 required artifact is missing.

Sure you must build this dependency

svn co https://svn.java.net/svn/hudson~svn/trunk/hudson/lib/hudson-maven-embedder 
cd hudson-maven-embedder
mvn install

Thanks, I was able to build it now.
But when I try to build a maven project using hudson I getting the following error:

ERROR: Processing failed due to a bug in the code. Please report this to hudson-users@googlegroups.com
java.lang.NullPointerException
at org.sonatype.aether.impl.internal.DefaultRemoteRepositoryManager.aggregateRepositories(DefaultRemoteRepositoryManager.java:140)
at org.apache.maven.project.ProjectModelResolver.addRepository(ProjectModelResolver.java:119)
at org.apache.maven.model.building.DefaultModelBuilder.configureResolver(DefaultModelBuilder.java:567)
at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:306)
at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:232)
at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:135)
at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:98)

git pull (and svn for embedder).
And please send/attach the full stack trace.

Here is a full stack trace (git pull and svn update was done sure):

ERROR: Processing failed due to a bug in the code. Please report this to hudson-users@googlegroups.com
java.lang.NullPointerException
at org.sonatype.aether.impl.internal.DefaultRemoteRepositoryManager.aggregateRepositories(DefaultRemoteRepositoryManager.java:135)
at org.apache.maven.project.ProjectModelResolver.addRepository(ProjectModelResolver.java:119)
at org.apache.maven.model.building.DefaultModelBuilder.configureResolver(DefaultModelBuilder.java:567)
at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:306)
at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:232)
at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:135)
at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:98)
at hudson.maven.MavenEmbedder.readProject(MavenEmbedder.java:378)
at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1042)
at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:933)
at hudson.FilePath.act(FilePath.java:753)
at hudson.FilePath.act(FilePath.java:735)
at hudson.maven.MavenModuleSetBuild$RunnerImpl.parsePoms(MavenModuleSetBuild.java:652)
at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:495)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:417)
at hudson.model.Run.run(Run.java:1337)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:377)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:140)

Thanks for reporting.
I need more info regarding the maven project you are using (what is the structure ? multi modules ? how are they organized ? )
Is it an open source so I can test with it ? (this could be more easy )

I am seeing the following:

Parsing POMs
ERROR: Processing failed due to a bug in the code. Please report this to users@hudson.dev.java.net
java.lang.NullPointerException
at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:200)
at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:190)
at org.apache.maven.project.ProjectModelResolver.resolveModel(ProjectModelResolver.java:179)
at org.apache.maven.model.building.DefaultModelBuilder.readParentExternally(DefaultModelBuilder.java:819)
at org.apache.maven.model.building.DefaultModelBuilder.readParent(DefaultModelBuilder.java:670)
at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:308)
at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:232)
at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:135)
at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:98)
at hudson.maven.MavenEmbedder.readProject(MavenEmbedder.java:378)
at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:971)
at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:876)
at hudson.FilePath.act(FilePath.java:753)
at hudson.FilePath.act(FilePath.java:735)
at hudson.maven.MavenModuleSetBuild$RunnerImpl.parsePoms(MavenModuleSetBuild.java:597)
at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:440)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:416)
at hudson.model.Run.run(Run.java:1280)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:322)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:139)
project=hudson.maven.MavenModuleSet@8f337b[acct-data]
project.getModules()=[]
project.getRootModule()=null
FATAL: null
java.lang.NullPointerException
at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:200)
at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:190)
at org.apache.maven.project.ProjectModelResolver.resolveModel(ProjectModelResolver.java:179)
at org.apache.maven.model.building.DefaultModelBuilder.readParentExternally(DefaultModelBuilder.java:819)
at org.apache.maven.model.building.DefaultModelBuilder.readParent(DefaultModelBuilder.java:670)
at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:308)
at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:232)
at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:135)
at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:98)
at hudson.maven.MavenEmbedder.readProject(MavenEmbedder.java:378)
at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:971)
at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:876)
at hudson.FilePath.act(FilePath.java:753)
at hudson.FilePath.act(FilePath.java:735)
at hudson.maven.MavenModuleSetBuild$RunnerImpl.parsePoms(MavenModuleSetBuild.java:597)
at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:440)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:416)
at hudson.model.Run.run(Run.java:1280)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:322)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:139)

Src built from head for maven-embedder src built from head of main-maven3-support branch for Hudson.

I see this on single and multi-module projects.

multi-module is as follows:
accounting-transaction-service-parent
+-accounting-transaction-service
+-accounting-transaction-service-web

• the service module produces client and impl jars, it uses wsimport to do top-down generation of web service classes from wsdl.
• the web module produces a war.

I don't have a lot of time to devote but if you point me where/what I should be looking for I could have a quick look at the problem.

A little more info on the error I am seeing. It appears to be related to parent poms. I built a new "hello world" project as described here: http://www.sonatype.com/books/mvnex-book/reference/simple-project-sect-create-simple.html

This built fine under hudsonm3 support. When I added our parent pom it began exploding with the same issue as above. This leads me to believe there is a problem with the embedder resolving dependencies specified higher in the pom chain than the project being built. I plan to do a little more testing to verify this postulation.

so git pull and svn up.
And should be better.
I usually test with projects here :

• https://github.com/olamy/scm-git-test
• https://github.com/olamy/scm-git-test-one-module

Olamy, I just pulled the new code and. It appears to be working much better! Thanks for your work.

One last thing we are seeing is that the build whenever snapshot dependencies are built option is not working, any thoughts on this?

probably somehing else I have to check.
But currently I'm working on having builds working correctly if you use m2 or m3.

Hi Folks,
I have added some details here http://olamy.blogspot.com/2010/12/maven-3-support-in-hudson-maven-plugin.html
So all feedbacks are welcome !

PS : if everything works fine I will accept all beer parties invitations

It works for me now, thanks a lot

Hi,

I've got the following exception:
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239)
at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:148)
at hudson.maven.Maven3Builder.call(Maven3Builder.java:121)
at hudson.maven.Maven3Builder.call(Maven3Builder.java:69)
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:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.NullPointerException
at org.jvnet.hudson.maven3.listeners.HudsonMavenExecutionResult.<init>(HudsonMavenExecutionResult.java:57)
at org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:88)
... 18 more

The problem was, that site-plugin failed, because the folders weren't there where they were supposed to be (local site-deploy). So the build failure handling could be enhanced.

@aldaris which maven goals are you using ?

The goal was exactly: clean -Phudson -Dmaven.test.skip=true install site-deploy
The project was this: http://stewie.sch.bme.hu/pub/aldaris/korok/
The clean install works nicely for me with two different project, although I'm not quite sure about Hudson static analysis and task warnings plugins, because they doesn't seems to show any results in Hudson. But maybe I misconfigured something there..

ok I have to have a look when the site plugin is invoked with a maven3 build as it's very different from maven2.

@aldaris I have fixed your NPE in push 93ed8223ff7e81d5d9ca3abc8d7df594069bf1a9

Just to know does it happened when your maven build failed (test failure ) ?

I need to investigate more regarding site plugin with maven 3.

As I wrote earlier, I've ran the build with skipping tests, because this was just a dummy Hudson install. Later this evening I'll try to build this project within a correct environment (where I can actually run those tests) and I'll let you know about the results.

Ok I see the "that site-plugin failed".
So my last push should fix that.

With e90e51b91c6599dbe4df13f826301b11a6d3febe it looks like my project builds fine with this goal:
-Dmaven.test.failure.ignore=true -Phudson clean install checkstyle:checkstyle site-deploy

Thanks!

Thank you for posting the war for Hudson ver. 1.389-SNAPSHOT (private-12/13/2010 23:51-olamy). Olamy, my understanding from your blogspot was copy the hudson.war you posted to the hudson install directory and restart the server.

Building using maven 2.2.1 it worked (both with freestyle and the maven 2 type job), but with maven 3.0.1 the same multi-pom project with a maven 2 type job generated this error using the goals and options "-e -X -V clean install":

Started by user anonymous
[workspace] $ cvs -q -z3 update -PdC -D "Tuesday, December 14, 2010 12:17:47 PM UTC"
? modules/hs_err_pid6427.log
? modules/[omitted]/target
? modules/[omitted]/target
? modules/[omitted]/target
? modules/[omitted]/target
? modules/[omitted]/rpm/target
? modules/[omitted]/rpm/target
? modules/[omitted]/rpm/target
? modules/common/test.csv
? modules/common/test.txt
? modules/[omitted]/target
? modules/help/target
? modules/[omitted]/target
? modules/[omitted]/rpm/target
? modules/sequencer/[omitted].xml
? modules/sequencer/[omitted].xml
? modules/sequencer/[omitted].xml
? modules/sequencer/[omitted].xml
$ no changes detected
Starting xvnc
[workspace] $ vncserver :10

New 'xxxxxx036:10 (root)' desktop is xxxxxx036:10

Starting applications specified in /root/.vnc/xstartup Log file is /root/.vnc/xxxxxx036:10.log

Parsing POMs
[modules] $ /home/jjohnson/hudson/tools/_usr_java_jdk1.6.0_20/bin/java -Xmx512M -XX:MaxPermSize=512M -cp /home/jjohnson/hudson/plugins/maven-plugin/WEB-INF/lib/maven-agent-1.388.jar:/home/jjohnson/apache-maven-3.0.1/boot/plexus-classworlds-2.4.jar hudson.maven.agent.Main /home/jjohnson/apache-maven-3.0.1 /home/jjohnson/hudson/war/WEB-INF/lib/remoting-1.389-SNAPSHOT.jar /home/jjohnson/hudson/plugins/maven-plugin/WEB-INF/lib/maven-interceptor-1.388.jar 46129 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)
Terminating xvnc.
$ vncserver -kill :10
Killing Xvnc process ID 16102
ERROR: Failed to launch Maven. Exit code = 1 Archiving artifacts
Finished: FAILURE

@jonathanjohnson
I need more details .
How you hudson is installed ? (war in a servlet container, using java -jar hudson.war ? )
Does your build runs on master node or slave one ?
The cli is bad

 /home/jjohnson/hudson/tools/_usr_java_jdk1.6.0_20/bin/java -Xmx512M -XX:MaxPermSize=512M -cp /home/jjohnson/hudson/plugins/maven-plugin/WEB-INF/lib/maven-agent-1.388.jar:/home/jjohnson/apache-maven-3.0.1/boot/plexus-classworlds-2.4.jar hudson.maven.agent.Main /home/jjohnson/apache-maven-3.0.1 /home/jjohnson/hudson/war/WEB-INF/lib/remoting-1.389-SNAPSHOT.jar /home/jjohnson/hudson/plugins/maven-plugin/WEB-INF/lib/maven-interceptor-1.388.jar 46129

With maven 3 you must have something like

 /local/maven/hudson-slave-dev-totw/tools/current-tars-prod/bin/java -Xmx256m -Xms256m -client -cp /local/maven/hudson-slave-dev-totw/maven3-agent.jar:/local/maven/hudson-slave-dev-totw/tools/maven-3.0/boot/plexus-classworlds-2.2.3.jar org.jvnet.hudson.maven3.agent.Maven3Main /local/maven/hudson-slave-dev-totw/tools/maven-3.0 /local/maven/hudson-slave-dev-totw/slave.jar /local/maven/hudson-slave-dev-totw/maven3-interceptor.jar 58341

It works for me now, thanks a lot

Hi Folks,
New build available here : http://people.apache.org/~olamy/hudson/main-maven3-support/

Maybe this is a little too much to ask right now, but I tried building a project which uses Tycho and it failed. The project can be found at git://mylyn-mantis.git.sourceforge.net/gitroot/mylyn-mantis/mylyn-mantis . I just configured a maven2 job to perform 'clean install' . The reported hudson version is Hudson ver. 1.389-SNAPSHOT (private-12/15/2010 12:00-olamy) .

Let me know if I should open a separate issue.

Started by user anonymous
Parsing POMs
use transfertListener hudson.maven.MavenModuleSetBuild$SimpleTransferListener
ERROR: Failed to parse POMs
org.apache.maven.project.ProjectBuildingException: 1 problem was encountered while building the effective model for com.itsolut.mantis:com.itsolut.mantis:3.1.6-SNAPSHOT
[ERROR] Unknown packaging: eclipse-plugin @ line 13, column 13
 for project com.itsolut.mantis:com.itsolut.mantis:3.1.6-SNAPSHOT at /home/robert/.hudson/jobs/mylyn-mantis/workspace/com.itsolut.mantis.parent/../com.itsolut.mantis/pom.xml
	at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:139)
	at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:98)
	at hudson.maven.MavenEmbedder.readProject(MavenEmbedder.java:396)
	at hudson.maven.MavenUtil.resolveModules(MavenUtil.java:249)
	at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1060)
	at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:943)
	at hudson.FilePath.act(FilePath.java:753)
	at hudson.FilePath.act(FilePath.java:735)
	at hudson.maven.MavenModuleSetBuild$RunnerImpl.parsePoms(MavenModuleSetBuild.java:661)
	at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:498)
	at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:417)
	at hudson.model.Run.run(Run.java:1337)
	at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:380)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:140)
Caused by: org.apache.maven.model.building.ModelBuildingException: 1 problem was encountered while building the effective model for com.itsolut.mantis:com.itsolut.mantis:3.1.6-SNAPSHOT
[ERROR] Unknown packaging: eclipse-plugin @ line 13, column 13

	at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:422)
	at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:374)
	at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:365)
	at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:232)
	at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:135)
	... 14 more
Finished: FAILURE

Debugging output from the log.

@olamy

On my Linux server I start hudson using a Linux service (the single master node) with a service script and when calling hudson.sh start it invokes this command:

java -XX:MaxPermSize=512m -DDISPLAY_NUMBER= -jar /home/jjohnson/hudson/hudson.war --httpPort=8080 --ajp13Port=8010 --prefix=/hudson

To install your hudson.war I stopped the server, backed up /home/jjohnson/hudson/hudson.war, and copied the olamy hudson.war over it and started the server. The hudson pages had changed a footer saying 1.389-SNAPSHOT (private-12/13/2010 23:51-olamy, so we know it started with the olamy hudson.war. In the configuration of the job I just changed the "Maven Version" from 2.2.1 to 3.0.1.

Also noticed in the hudson.sh the MAVEN_HOME directory was still at 2.2.1 so I also changed that to 3.0.1. But that had no effect on the bad cli. What what other installation or configuration changes would be necessary to fix the bad cli?

@jonathanjohnson
I will add some debug stuff and ask you to start your hudson master and your nodes with some -D to activate debugging.
No time ATM, will back to you tomorrow.

Running Hudson Hudson ver. 1.389-SNAPSHOT (private-12/15/2010 12:00-olamy) on Linux gives me for a project the following stack trace:

Sadly, the project is company confidential, so I cannot provide the poms to you but I can test further releases which maybe show more debug output

[INFO] Copying 0 resource
mojoSucceeded maven-resources-plugin
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239)
at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:148)
at hudson.maven.Maven3Builder.call(Maven3Builder.java:121)
at hudson.maven.Maven3Builder.call(Maven3Builder.java:69)
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:442)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:139)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:909)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.InternalError
at hudson.maven.reporters.MavenFingerprinter.record(MavenFingerprinter.java:137)
at hudson.maven.reporters.MavenFingerprinter.postExecute(MavenFingerprinter.java:85)
at hudson.maven.Maven3Builder$MavenExecutionListener.mojoSucceeded(Maven3Builder.java:571)
at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:81)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:214)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:140)
at org.apache.maven.lifecycle.internal.MojoExecutor.executeForkedExecutions(MojoExecutor.java:351)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeForkedExecutions(DefaultLifecycleExecutor.java:165)
at org.apache.maven.plugins.site.DefaultMavenReportExecutor.buildMavenReports(DefaultMavenReportExecutor.java:250)
at org.apache.maven.plugins.site.AbstractSiteRenderingMojo.getReports(AbstractSiteRenderingMojo.java:208)
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:105)

@rombert I have noticed this in your poms :

<relativePath>../com.itsolut.mantis.parent</relativePath>
could you change to 
<relativePath>../com.itsolut.mantis.parent/pom.xml</relativePath>

BTW I will change something in embedder which read the project.

@rombert I have pushed some stuff . No new binary builds done as I want to add more debugging stuff for @jonathanjohnson and @hakan42.

If you want to test now you can build yourself (follow steps from my blog entry)

Thanks, I'll wait for your binary builds... Too much pressure on $DAYJOB just now

Hudson log after updating. The build still fails, now the error is

Unpacking http://archive.apache.org/dist/maven/binaries/apache-maven-3.0-bin.zip to /home/robert/.hudson/tools/maven-3.0 on Hudson
Parsing POMs
ERROR: Failed to parse POMs
org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:
[ERROR] Unknown packaging: eclipse-plugin @ line 13, column 13
[ERROR] Unknown packaging: eclipse-plugin @ line 13, column 13
[ERROR] Unknown packaging: eclipse-plugin @ line 13, column 13
[ERROR] Unknown packaging: eclipse-test-plugin @ line 13, column 13
[ERROR] Unknown packaging: eclipse-feature @ line 13, column 13
[ERROR] Unknown packaging: eclipse-update-site @ line 13, column 13

	at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:325)
	at hudson.maven.MavenEmbedder.readProjects(MavenEmbedder.java:380)
	at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1061)
	at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:946)
	at hudson.FilePath.act(FilePath.java:753)
	at hudson.FilePath.act(FilePath.java:735)
	at hudson.maven.MavenModuleSetBuild$RunnerImpl.parsePoms(MavenModuleSetBuild.java:662)
	at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:499)
	at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:417)
	at hudson.model.Run.run(Run.java:1337)
	at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:381)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:140)
Finished: FAILURE

Forgot to mention that I also changed the relative paths as you suggested.

New build push : http://people.apache.org/~olamy/hudson/main-maven3-support/hudson.war (16-Dec-2010 23:41)
@jonathanjohnson can you launch hudson with adding : -Dhudson.maven.debug=true
You will see something like that in the logs :

mavenVersion 3.0 for mavenHome /home/hudson/hudson-slave/tools/maven-3.0

Can you send me values ?
@hakan42 As I can see in the logs you are executing site plugin which forks mojo ?
Can you explain which reporting mojos you are using ? (I can probably reproduce with those informations or add -X in the maven goals)

@rombert : I see what is the issue here with the plugin extensions (I have to find a good way to fix it).

@olamy :There's no rush, many thanks for looking into this!

@olamy:

Here is the configuration of the reporting plugin. I will also attach the most current log file from the build, I ran it with the -Dhudson.maven.debug=true flag.

<reportPlugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-project-info-reports-plugin</artifactId>
<reportSets>
<reportSet>
<id>default</id>
<reports>
<report>cim</report>
<report>dependencies</report>
<report>dependency-convergence</report>
<report>dependency-management</report>
<report>index</report>
<report>issue-tracking</report>
<report>license</report>
<report>mailing-list</report>
<report>plugin-management</report>
<report>plugins</report>
<report>project-team</report>
<report>scm</report>
<report>summary</report>
</reports>
</reportSet>
</reportSets>
</reportPlugin>

Log file from maven3 site build with the -Dhudson.maven.debug=true flag switched on

@hakan42 Thanks.
You have more reporting mojos . I can see at least the aggregated javadoc mojo which causes the failure.
I think I see what to fix here. The site plugin now fork stuff and there is some todos I haven't done regarding forking .

@olamy

Received your new hudson.war and the hudson.sh service script restarted Hudson master with your new debug setting:

java -XX:MaxPermSize=512m -Dhudson.maven.debug=true -DDISPLAY_NUMBER= -jar /home/jjohnson/hudson/hudson.war --httpPort=8080 --ajp13Port=8010 --prefix=/hudson

On the hudson pages the version is reported as:
Hudson ver. 1.389-SNAPSHOT (private-12/17/2010 00:29-olamy)

I ran the job with maven 3.0.1 and got the same error message and did not see your debug log output (hm?). I searched for "mavenVersion" and did not find it in the job log file or the "Raw console output".

Still getting same error message:

[modules] $ /home/jjohnson/hudson/tools/_usr_java_jdk1.6.0_20/bin/java -Xmx512M -XX:MaxPermSize=512M -cp /home/jjohnson/hudson/plugins/maven-plugin/WEB-INF/lib/maven-agent-1.389.jar:/home/jjohnson/apache-maven-3.0.1/boot/plexus-classworlds-2.4.jar hudson.maven.agent.Main /home/jjohnson/apache-maven-3.0.1 /home/jjohnson/hudson/war/WEB-INF/lib/remoting-1.389-SNAPSHOT.jar /home/jjohnson/hudson/plugins/maven-plugin/WEB-INF/lib/maven-interceptor-1.389.jar 59256
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)

@jonathanjohnson can you detail me the content of the directory /home/jjohnson/apache-maven-3.0.1
especially /home/jjohnson/apache-maven-3.0.1/lib

/home/jjohnson/apache-maven-3.0.1

drwxrwxr-x 2 jjohnson jjohnson 4096 Dec 7 10:24 bin
drwxrwxr-x 2 jjohnson jjohnson 4096 Dec 7 10:24 boot
drwxrwxr-x 2 jjohnson jjohnson 4096 Nov 23 05:50 conf
drwxrwxr-x 2 jjohnson jjohnson 4096 Dec 7 10:24 lib
rw-rr- 1 jjohnson jjohnson 11560 Nov 23 05:50 LICENSE.txt
rw-rr- 1 jjohnson jjohnson 1030 Nov 23 05:50 NOTICE.txt
rw-rr- 1 jjohnson jjohnson 2559 Nov 23 05:50 README.txt

/home/jjohnson/apache-maven-3.0.1/lib

rw-rr- 1 jjohnson jjohnson 77252 Nov 18 15:55 aether-api-1.8.jar
rw-rr- 1 jjohnson jjohnson 28432 Nov 18 15:59 aether-connector-wagon-1.8.jar
rw-rr- 1 jjohnson jjohnson 108886 Nov 18 15:58 aether-impl-1.8.jar
rw-rr- 1 jjohnson jjohnson 14438 Nov 18 15:56 aether-spi-1.8.jar
rw-rr- 1 jjohnson jjohnson 114622 Nov 18 15:57 aether-util-1.8.jar
rw-rr- 1 jjohnson jjohnson 41123 Sep 29 04:19 commons-cli-1.2.jar
rw-rr- 1 jjohnson jjohnson 52151 Nov 23 05:57 maven-aether-provider-3.0.1.jar
rw-rr- 1 jjohnson jjohnson 52010 Nov 23 05:55 maven-artifact-3.0.1.jar
rw-rr- 1 jjohnson jjohnson 285112 Nov 23 06:01 maven-compat-3.0.1.jar
rw-rr- 1 jjohnson jjohnson 530357 Nov 23 05:58 maven-core-3.0.1.jar
rw-rr- 1 jjohnson jjohnson 41781 Nov 23 06:02 maven-embedder-3.0.1.jar
rw-rr- 1 jjohnson jjohnson 164683 Nov 23 05:53 maven-model-3.0.1.jar
rw-rr- 1 jjohnson jjohnson 148105 Nov 23 05:57 maven-model-builder-3.0.1.jar
rw-rr- 1 jjohnson jjohnson 48940 Nov 23 05:56 maven-plugin-api-3.0.1.jar
rw-rr- 1 jjohnson jjohnson 30087 Nov 23 05:55 maven-repository-metadata-3.0.1.jar
rw-rr- 1 jjohnson jjohnson 46676 Nov 23 05:54 maven-settings-3.0.1.jar
rw-rr- 1 jjohnson jjohnson 41026 Nov 23 05:54 maven-settings-builder-3.0.1.jar
rw-rr- 1 jjohnson jjohnson 111869 Sep 29 04:20 nekohtml-1.9.6.2.jar
rw-rr- 1 jjohnson jjohnson 13494 Sep 29 04:12 plexus-cipher-1.4.jar
rw-rr- 1 jjohnson jjohnson 4211 Sep 30 16:14 plexus-component-annotations-1.5.5.jar
rw-rr- 1 jjohnson jjohnson 61072 Sep 29 04:12 plexus-interpolation-1.14.jar
rw-rr- 1 jjohnson jjohnson 28555 Sep 29 04:12 plexus-sec-dispatcher-1.3.jar
rw-rr- 1 jjohnson jjohnson 222137 Sep 29 04:11 plexus-utils-2.0.4.jar
rw-rr- 1 jjohnson jjohnson 477039 Nov 16 06:46 sisu-guice-2.9.1-noaop.jar
rw-rr- 1 jjohnson jjohnson 160424 Nov 16 06:46 sisu-inject-bean-1.4.3.1.jar
rw-rr- 1 jjohnson jjohnson 204886 Nov 16 06:46 sisu-inject-plexus-1.4.3.1.jar
rw-rr- 1 jjohnson jjohnson 11063 Nov 18 14:28 wagon-file-1.0-beta-7.jar
rw-rr- 1 jjohnson jjohnson 14991 Nov 18 14:29 wagon-http-lightweight-1.0-beta-7.jar
rw-rr- 1 jjohnson jjohnson 25516 Nov 18 14:29 wagon-http-shared-1.0-beta-7.jar
rw-rr- 1 jjohnson jjohnson 53227 Nov 18 14:28 wagon-provider-api-1.0-beta-7.jar
rw-rr- 1 jjohnson jjohnson 39798 Sep 29 04:20 xercesMinimal-1.9.6.2.jar

@hakan42 probably not related to our issue but configure plugins versions in your poms (some use snapshots)

[WARNING] 'reporting.plugins.plugin.version' for org.apache.maven.plugins:maven-project-info-reports-plugin is missing.
[WARNING] 'reporting.plugins.plugin.version' for org.apache.maven.plugins:maven-javadoc-plugin is missing.
[WARNING] 'reporting.plugins.plugin.version' for org.apache.maven.plugins:maven-changelog-plugin is missing.
[WARNING] 'reporting.plugins.plugin.version' for org.codehaus.mojo:versions-maven-plugin is missing

@hakan42 fixed in push https://github.com/hudson/hudson/commit/3ab72a8e16c47dcc5653cdc4ad21965810e14c51
removing some TODO

new binaries build available : http://people.apache.org/~olamy/hudson/main-maven3-support/

Hudson ver. 1.389-SNAPSHOT (private-12/17/2010 22:37-olamy)

Have Fun !

@jonathanjohnson I have just pushed some stuff which should for debugging.
You will something like that in the build log :

Found mavenVersion 3.0 from file jar:file:/home/hudson/hudson-slave/tools/maven-3.0/lib/maven-core-3.0.jar!/META-INF/maven/org.apache.maven/maven-core/pom.properties

Please let me know what you see.
No binaries build pushed. You must build (hudson-maven-embedder and hudson itself) stuff manually or wait I have time to push a new build (I have some other things to fix first)

new build pushed which fix issues regarding incremental builds. Issues introduce with the pom parsing optimisation.

@olamy

Just tried the new build you pushed on the 19th. My hudson pages now have "Hudson ver. 1.389-SNAPSHOT (private-12/20/2010 00:08-olamy)". With maven 2.2.1 it still works fine, but the build log for maven 3.0.1 again does not have your debug info:

Here is the short build log:

Started by user anonymous
Updating http://[omitted]/svn/appjava/trunk
At revision 14052
no change for http://[omitted]/svn/appjava/trunk since the previous build
Starting xvnc
[workspace] $ vncserver :10

New 'dbduvdu036:10 (root)' desktop is dbduvdu036:10

Starting applications specified in /root/.vnc/xstartup
Log file is /root/.vnc/dbduvdu036:10.log

Parsing POMs
[modules] $ /home/jjohnson/hudson/tools/_usr_java_jdk1.6.0_20/bin/java -Xmx512M -XX:MaxPermSize=512M -cp /home/jjohnson/hudson/plugins/maven-plugin/WEB-INF/lib/maven-agent-1.389.jar:/home/jjohnson/apache-maven-3.0.1/boot/plexus-classworlds-2.4.jar hudson.maven.agent.Main /home/jjohnson/apache-maven-3.0.1 /home/jjohnson/hudson/war/WEB-INF/lib/remoting-1.389-SNAPSHOT.jar /home/jjohnson/hudson/plugins/maven-plugin/WEB-INF/lib/maven-interceptor-1.389.jar 59023
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)
Terminating xvnc.
$ vncserver -kill :10
Killing Xvnc process ID 14746
ERROR: Failed to launch Maven. Exit code = 1
Archiving artifacts
Finished: FAILURE

As I see (Starting xvnc), you are the xvnc plugin.
So how does-it works without this ?.
Then how your slaves are started ?

I just have a master hudson server. No slaves.
Without xvnc get same error:

Started by user anonymous
Updating http://[omitted]/svn/appjava/trunk
At revision 14052
no change for http://[omitted]/svn/appjava/trunk since the previous build
Parsing POMs
[modules] $ /home/jjohnson/hudson/tools/_usr_java_jdk1.6.0_20/bin/java -Xmx512M -XX:MaxPermSize=512M -cp /home/jjohnson/hudson/plugins/maven-plugin/WEB-INF/lib/maven-agent-1.389.jar:/home/jjohnson/apache-maven-3.0.1/boot/plexus-classworlds-2.4.jar hudson.maven.agent.Main /home/jjohnson/apache-maven-3.0.1 /home/jjohnson/hudson/war/WEB-INF/lib/remoting-1.389-SNAPSHOT.jar /home/jjohnson/hudson/plugins/maven-plugin/WEB-INF/lib/maven-interceptor-1.389.jar 43925
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
Finished: FAILURE

The branch is now build thru a job in http://ci.hudson-labs.org (http://ci.hudson-labs.org/job/hudson_main_maven3_support)
How to get a fresh build is now as simple as :

wget http://ci.hudson-labs.org/job/hudson_main_maven3_support/lastSuccessfulBuild/artifact/war/target/hudson.war

I just wanted to notify you that my site project is working well now with the "Hudson ver. 1.389-SNAPSHOT (private-12/20/2010 00:08-olamy)" release.

Thank you for all your work, hopefully it will find its way into the main trunk.

so merged in master and will be in next release 1.392 .

regarding eclipse-plugin packaging issue, I have created a separate issue JENKINS-8348.
And will work on this next year

to test this before the official release read this : http://olamy.blogspot.com/2010/12/xmas-for-hudson-users.html

I hesitate to reopen the issue but I have the same behavior as with previous releases.
I have an existing m2 job and I try to use maven 3.0 installed by hudson.
It fails to start with :

[workspace] $ /home/swf/vms/sun/jdk1.6.0-i586/bin/java -client -Xshare:auto -Xms512M -Xmx1G -XX:MaxPermSize=256M -Djava.net.preferIPv4Stack=true -Dcom.sun.media.jai.disableMediaLib=true -Djava.io.tmpdir=/home/swfhudson/tmp/ -cp /home/swfhudson/data/plugins/maven-plugin/WEB-INF/lib/maven-agent-1.391.jar:/home/swfhudson/data/tools/maven-3.0.x/boot/plexus-classworlds-2.2.3.jar hudson.maven.agent.Main /home/swfhudson/data/tools/maven-3.0.x /home/swfhudson/tmp/0-ROOT/WEB-INF/lib/remoting-1.391.jar /home/swfhudson/data/plugins/maven-plugin/WEB-INF/lib/maven-interceptor-1.391.jar 57824
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

details : http://ci.exoplatform.org/job/gatein-portal-3.1.x-rebased-ci/8/console
I reproduced the issue with a maven setup manually installed (3.0.1).

aheritier, you have 1.391 written all over the place, and olamy wrote this feature will be available in 1.392 which is not out yet.

You're right. Sorry. I thought it was merged in 1.391 as the release is done each saturday and he did the commit on Friday. Now I have to wait few days more ..

Latest hudson (.392) now fails with:

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: Could not transfer artifact com.edb.finance:parent-pom:pom:1.3.9 from/to central (http://central): Error transferring file: central and 'parent.relativePath' points at wrong local POM @ line 3, column 10

	at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1129)
	at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:983)
	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:441)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at hudson.remoting.Engine$1$1.run(Engine.java:58)
	at java.lang.Thread.run(Thread.java:662)
Caused by: hudson.remoting.ProxyException: org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:

I have this extension in it's parent pom:

   <extensions>
                        <extension>
                                <groupId>org.apache.maven.wagon</groupId>
                                <artifactId>wagon-webdav-jackrabbit</artifactId>
                                <version>1.0-beta-7</version>
                        </extension>
                </extensions>

The problem occurs both with 2.2.1 and 3.0.1 maven installations.

settings.xml uses a mirror like this:

     <mirror>
          <id>nexus</id>
          <url>http://nexus.edb.com/nexus/content/groups/public/</url>
          <mirrorOf>*</mirrorOf>
        </mirror>

@davidkarlsen please do not reopen issue.
Your one is similar to JENKINS-8387.
So it's fixed in master. and you can try a SNAPSHOT

I'm using Hudson ver. 1.393-SNAPSHOT (private-01/03/2011 18:16-olamy) and also (still) have the problem that a parent pom cannot be downloaded from Nexus but with Maven 3.0.1.

It sounds like JENKINS-8387 but since I'm having the problem with Maven 3 I thought I'd reopen this issue instead of JENKINS-8387. I hope this is ok.

Found mavenVersion 3.0.1 from file jar:file:/exports/home/hudson/apache-maven-3.0.1/lib/maven-core-3.0.1.jar!/META-INF/maven/org.apache.maven/maven-core/pom.properties
Parsing POMs
failed to transfer Error transferring file: central
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 transfer artifact myGroupId:myArtifactId:pom:10 from/to central (http://central): Error transferring file: central and 'parent.relativePath' points at wrong local POM @ line 5, column 10

at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:325)
at hudson.maven.MavenEmbedder.readProjects(MavenEmbedder.java:382)
at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1096)
at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:983)
at hudson.FilePath.act(FilePath.java:756)
at hudson.FilePath.act(FilePath.java:738)
at hudson.maven.MavenModuleSetBuild$RunnerImpl.parsePoms(MavenModuleSetBuild.java:690)
at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:526)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:417)
at hudson.model.Run.run(Run.java:1362)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:400)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:145)

@unguiculus please do not reopen.
Your issue is traked by JENKINS-8390.
BTW you can fix your parent declaration if you don't wait the fix

I don't see how this relates to JENKINS-8390. I does rather look like davidkarlsen's problem which was supposedly fixed in JENKINS-8387.

BTW, why would I have to fix the parent declaration? I don't think there is a problem with it. The parent in this case is the corporate pom which is not part of the reactor. Anyways, I tried to add an empty <relativePath /> but that did not help.

@unguiculus I have fixed more stuff in JENKINS-8387 (mirrors not used) so probably you have mirrors where maven should be able to download the parent.
you can try with this build :
wget http://people.apache.org/~olamy/hudson/main-maven3-support/hudson.war

I had the same problem yesterday with a maven project still using 2, with 1.392, so I tried the snapshot to no effect. I think the problem is the maven-plugin was not updated, since when I downgraded, I had to reinstall 1.391's maven-plugin. If I have time to day, I'll try to play with this. I thought hudson would overwrite the maven-plugin, since it is pinned, but it doesn't appear to have done that. Maybe if you also put the maven-plugin.hpi next to your hudson.war that would help too.

@olamy: As I mentioned, this is exactly the version I was trying (1.393-SNAPSHOT (private-01/03/2011 18:16-olamy)) because I was hoping that the fix for JENKINS-8387 would fix the problem, which was not the case.

@lshatzer what is your issue ?
At least logs could be helpfull.

It was a maven 2 project, with just referring to a corporate parent pom. I tried adding <relativePath/> with no luck. I even tried your snapshot, but as I said, I think the problem might have been the maven plugin was not updated to the snapshot version as well.

Here is the log (sorry for not attaching it, as I was at home, and did not have it handy).

Parsing POMs
failed to transfer Error transferring file: central
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 transfer artifact com.company.parentpoms:utilities:pom:4.1.16 from/to central (http://central): Error transferring file: central and 'parent.relativePath' points at wrong local POM @ line 9, column 11

	at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:325)
	at hudson.maven.MavenEmbedder.readProjects(MavenEmbedder.java:382)
	at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1096)
	at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:983)
	at hudson.FilePath.act(FilePath.java:756)
	at hudson.FilePath.act(FilePath.java:738)
	at hudson.maven.MavenModuleSetBuild$RunnerImpl.parsePoms(MavenModuleSetBuild.java:690)
	at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:526)
	at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:417)
	at hudson.model.Run.run(Run.java:1365)
	at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:400)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:145)

@lshatzer have a look at JENKINS-8390 and if last build doesn't put a comment in JENKINS-8390

Code changed in hudson
User: Olivier Lamy
Path:
changelog.html
http://hudson-labs.org/commit/core/18f4a8ebc0516bc1a88b78067a058140a673a152
Log:
update changelog with JENKINS-4988

For the folks having issues with downloading your corporate parent POM - I had the same problem and it turned out to be a regression in Maven (MNG-4963) which is supposed to be fixed in Maven 3.0.3.

I guess for greater searchability for others unfortunate enough to have the same problem as me - The exact error message I got was:

Non-resolvable parent POM: Could not find artifact mycompany:myparent:pom:myversion and 'parent.relativePath' points at wrong local POM

...And the suggested workaround for MNG-4963 worked for me. This was using Jenkins 1.399 which looks like it uses Maven 3.0.2 internally.

as someone requested : fix for 1.392 version