Currently, Hudson does not seem to play well with Maven 2.1.0. When using a
Maven2 project type, the following is output at the beginning of the build log:

> [src] $ /etc/java-config-2/current-system-vm/bin/java -Xms128m -Xmx768m
-XX:MaxPermSize=256M -cp
/home/hudson-slave/work/maven-agent.jar:/usr/share/maven-bin-2.0/boot/classworlds-1.1.jar
hudson.maven.agent.Main /usr/share/maven-bin-2.0/
/home/hudson-slave/work/slave.jar /home/hudson-slave/work/maven-interceptor.jar
42007
> channel started
> Executing Maven: -B -B -f
/home/hudson-slave/work/workspace/endx_stats/src/pom.xml clean
checkstyle:checkstyle pmd:pmd pmd:cpd cobertura:cobertura compiler:compile
> [WARNING]
> ************ WARNING ************
>
> This Maven runtime contains a LifecycleExecutor component with an incomplete
configuration.
>
> LifecycleExecutor class: org.apache.maven.lifecycle.LifecycleExecutorInterceptor
> Missing component requirement: org.apache.maven.project.MavenProjectBuilder
>
> NOTE: This seems to be a third-party Maven derivative you are using. If so, please
> notify the developers for this derivative project of the problem. The Apache
Maven team is not
> responsible for maintaining the integrity of third-party component overrides.
>
>
> [WARNING]
> ************ WARNING ************
>
> This Maven runtime contains a LifecycleExecutor component with an incomplete
configuration.
>
> LifecycleExecutor class: org.apache.maven.lifecycle.LifecycleExecutorInterceptor
> Missing component requirement:
org.apache.maven.project.interpolation.ModelInterpolator
>
> NOTE: This seems to be a third-party Maven derivative you are using. If so, please
> notify the developers for this derivative project of the problem. The Apache
Maven team is not
> responsible for maintaining the integrity of third-party component overrides.
>
>
> [INFO] Scanning for projects...

About this, Kohsuke commented:

> Right, Hudson does indeed put some components inside Plexus to monitor
> what's going on. I guess that needs to be updated.

Using Maven 2.1 also seems to cause other issues during builds. When I disable
all build plugins for a job, I still get an exception that I don't get when I
run the same build from the command line:

> [INFO] Velocity successfully started.
> [INFO] [checkstyle:checkstyle]
> [INFO] Source directory does not exist - skipping report.
> [INFO] [pmd:pmd]
> [INFO] [pmd:cpd]
> [INFO] Preparing cobertura:cobertura
> [HUDSON] Archiving /home/hudson-slave/work/workspace/endx_stats/src/pom.xml to
/var/lib/hudson/jobs/endx_stats/modules/us.ms.state.deq.endx$endx/builds/2009-03-24_08-03-33/archive/us.ms.state.deq.endx/endx/1.5.0-SNAPSHOT/pom.xml
> [INFO] ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] null
> [INFO] ------------------------------------------------------------------------
> [INFO] Trace
> java.lang.NullPointerException
> at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.calculateConcreteConfiguration(DefaultLifecycleExecutor.java:747)
> at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:578)
> at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540)
> at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:1168)
> at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:1009)
> at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:627)
> at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553)
> at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523)
> at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
> at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
> at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
> at
org.apache.maven.lifecycle.LifecycleExecutorInterceptor.execute(LifecycleExecutorInterceptor.java:65)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:356)
> 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.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at hudson.maven.agent.Main.launch(Main.java:158)
> at hudson.maven.MavenBuilder.call(MavenBuilder.java:162)
> at hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:577)
> at hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:523)
> at hudson.remoting.UserRequest.perform(UserRequest.java:92)
> at hudson.remoting.UserRequest.perform(UserRequest.java:46)
> at hudson.remoting.Request$2.run(Request.java:236)
> 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:619)
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 15 seconds
> [INFO] Finished at: Tue Mar 24 08:03:55 CDT 2009
> [INFO] Final Memory: 15M/127M
> [INFO] ------------------------------------------------------------------------
> channel stopped
> Finished: FAILURE

Reference thread: http://www.nabble.com/Hudson-support-for-Maven-2.1-td22680184.html