• Icon: New Feature New Feature
    • Resolution: Fixed
    • Icon: Major Major
    • maven-plugin
    • None

      Hudson maven-plugin doesn't work with Maven 3 on Linux. On Linux Hudson builds its own Java command line and does some additional magic to launch Maven. On Windows it works fine because mvn.bat is used instead.

      The mechanism on Linux fails for two reasons:

      1. classworlds-*.jar was upgraded to plexus-classworlds-2.2.2 with Maven 3, so the classpath is wrong.

      2. plexus-classworlds-2.2.2 is not fully backward compatible. After renaming the jar to classworlds-2.2.2.jar the error is:

      $ /opt/java/x86_64/jdk1.6.0_16/bin/java -Xmx768m -XX:MaxPermSize=256m -cp /home/hudson/plugins/maven-plugin/WEB-INF/lib/maven-agent-1.335.jar:/opt/maven/3.0-alpha-5/boot/classworlds-2.2.2.jar hudson.maven.agent.Main /opt/maven/3.0-alpha-5 /usr/share/tomcat5/webapps/hudson/WEB-INF/lib/remoting-1.335.jar /home/hudson/plugins/maven-plugin/WEB-INF/lib/maven-interceptor-1.335.jar 32917
      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
      Skipping sonar analysis due to bad build status FAILURE
      Finished: FAILURE

      Reason for the above error is that getWorld() returns a different type in 2.2.2 which isn't assignable to the type returned in 1.x.

      A general question: Why does Hudson use different mechanisms for launching Maven on Windows and Linux?

      Tested with 1.335

          [JENKINS-4988] Maven 3 support in maven-plugin

          aldaris added a comment -

          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..

          aldaris added a comment - 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..

          Olivier Lamy added a comment -

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

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

          Olivier Lamy added a comment - - edited

          @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.

          Olivier Lamy added a comment - - edited @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.

          aldaris added a comment -

          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.

          aldaris added a comment - 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.

          Olivier Lamy added a comment -

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

          Olivier Lamy added a comment - Ok I see the "that site-plugin failed". So my last push should fix that.

          aldaris added a comment -

          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!

          aldaris added a comment - 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 added a comment - 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

          Olivier Lamy added a comment -

          @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
          

          Olivier Lamy added a comment - @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

          marcus888 added a comment -

          It works for me now, thanks a lot

          marcus888 added a comment - It works for me now, thanks a lot

          Olivier Lamy added a comment -

          Olivier Lamy added a comment - 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
          

          Robert Munteanu added a comment - 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.

          Robert Munteanu added a comment - 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 added a comment - @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?

          Olivier Lamy added a comment -

          @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.

          Olivier Lamy added a comment - @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.

          hakan42 added a comment -

          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)

          hakan42 added a comment - 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)

          Olivier Lamy added a comment -

          @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.

          Olivier Lamy added a comment - @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.

          Olivier Lamy added a comment -

          @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)

          Olivier Lamy added a comment - @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)

          hakan42 added a comment -

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

          hakan42 added a comment - 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
          

          Robert Munteanu added a comment - 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.

          Robert Munteanu added a comment - Forgot to mention that I also changed the relative paths as you suggested.

          Olivier Lamy added a comment -

          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).

          Olivier Lamy added a comment - 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!

          Robert Munteanu added a comment - @olamy :There's no rush, many thanks for looking into this!

          hakan42 added a comment -

          @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>

          hakan42 added a comment - @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>

          hakan42 added a comment -

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

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

          Olivier Lamy added a comment -

          @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 .

          Olivier Lamy added a comment - @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 added a comment - @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)

          Olivier Lamy added a comment -

          @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

          Olivier Lamy added a comment - @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

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

          Olivier Lamy added a comment -

          @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
          

          Olivier Lamy added a comment - @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

          Olivier Lamy added a comment -

          @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 !

          Olivier Lamy added a comment - @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 !

          Olivier Lamy added a comment -

          @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)

          Olivier Lamy added a comment - @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)

          Olivier Lamy added a comment -

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

          Olivier Lamy added a comment - 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

          jonathanjohnson added a comment - @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

          Olivier Lamy added a comment -

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

          Olivier Lamy added a comment - 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

          jonathanjohnson added a comment - 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

          Olivier Lamy added a comment -

          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
          

          Olivier Lamy added a comment - 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

          hakan42 added a comment -

          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.

          hakan42 added a comment - 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.

          Olivier Lamy added a comment -

          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

          Olivier Lamy added a comment - 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

          Olivier Lamy added a comment -

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

          Olivier Lamy added a comment - 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).

          Arnaud Héritier added a comment - 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.

          Stevo Slavić added a comment - 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 ..

          Arnaud Héritier added a comment - 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 ..

          davidkarlsen added a comment - - edited

          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 added a comment - - edited 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>

          Olivier Lamy added a comment -

          @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

          Olivier Lamy added a comment - @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

          unguiculus added a comment -

          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 added a comment - 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)

          Olivier Lamy added a comment -

          @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

          Olivier Lamy added a comment - @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

          unguiculus added a comment -

          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 added a comment - 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.

          Olivier Lamy added a comment -

          @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

          Olivier Lamy added a comment - @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.

          Larry Shatzer, Jr. added a comment - 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.

          unguiculus added a comment -

          @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.

          unguiculus added a comment - @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.

          Olivier Lamy added a comment -

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

          Olivier Lamy added a comment - @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)
          
          

          Larry Shatzer, Jr. added a comment - 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)

          Olivier Lamy added a comment -

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

          Olivier Lamy added a comment - @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

          SCM/JIRA link daemon added a comment - Code changed in hudson User: Olivier Lamy Path: changelog.html http://hudson-labs.org/commit/core/18f4a8ebc0516bc1a88b78067a058140a673a152 Log: update changelog with JENKINS-4988

          Nathan Parry added a comment -

          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.

          Nathan Parry added a comment - 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.

          Nathan Parry added a comment -

          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.

          Nathan Parry added a comment - 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.

          Olivier Lamy added a comment -

          as someone requested : fix for 1.392 version

          Olivier Lamy added a comment - as someone requested : fix for 1.392 version

            olamy Olivier Lamy
            zlosch zlosch
            Votes:
            155 Vote for this issue
            Watchers:
            138 Start watching this issue

              Created:
              Updated:
              Resolved: