Maven build failing after tests, but only in Jenkins

[Craig S. Cottingham]

Today, two of our Maven build jobs started failing upon completion of
the test phase, with this error:

[JENKINS] Recording test results
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:
158)
at hudson.maven.Maven3Builder.call(Maven3Builder.java:128)
at hudson.maven.Maven3Builder.call(Maven3Builder.java:75)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
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.NoSuchMethodError:
org.apache.tools.ant.types.FileSet.getDirectoryScanner()Lorg/apache/
tools/ant/DirectoryScanner;
at
hudson.maven.reporters.SurefireArchiver.postExecute(SurefireArchiver.java:
135)
at hudson.maven.Maven3Builder
$MavenExecutionListener.reccordMojoSucceeded(Maven3Builder.java:599)
at hudson.maven.Maven3Builder
$MavenExecutionListener.mojoSucceeded(Maven3Builder.java:562)
at
org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:
87)
at
org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:
42)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:
228)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:
153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:
145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:
84)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:
59)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:
183)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:
161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at
org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:
79)
... 18 more

The odd thing is, I can run the same goal in the same Maven (3.0.3) in
the same JVM version (1.6.0_24) with the same local repository as the
same user from the command line, and I don't get this error.

One of the first things I did when we started getting this error was
to update Jenkins to 1.413 (from 1.4.12), to no effect.

I get the feeling I'm missing something obvious, but I've been poking
and prodding this all day with no success. I finally told Maven to
skip the tests so the job would stop failing, but that's clearly not a
long-term solution.