Thanks for the response. I tried that, here's what I got:
-----Original Message----- From: Andrew Williams [mailto:[EMAIL PROTECTED] Sent: Saturday, May 12, 2007 12:40 AM To: Maven Users List Subject: Re: test failures they are logged to a file, do mvn test -Dsurefire.useFile=false to log them to stdout - no need for -e or -X Andy On 12 May 2007, at 00:30, [EMAIL PROTECTED] wrote: > I am getting a test failure message from maven: > > [INFO] Trace > org.apache.maven.BuildFailureException: There are test failures. > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals > (Default > LifecycleExecutor.java:560) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLif > ec > ycle(DefaultLifecycleExecutor.java:480) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal > (DefaultL > ifecycleExecutor.java:459) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHand > le > Failures(DefaultLifecycleExecutor.java:311) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegment > s( > DefaultLifecycleExecutor.java:278) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute > (DefaultLifec > ycleExecutor.java:143) > at > org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java: > 125) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:272) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke > (NativeMethodAccessorImpl.jav > a:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke > (DelegatingMethodAccessor > Impl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at > org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > Caused by: org.apache.maven.plugin.MojoFailureException: There are > test failures. > at > org.apache.maven.plugin.surefire.SurefirePlugin.execute > (SurefirePlugin.j > ava:425 > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo > (DefaultPluginMa > nager.java:443) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals > (Default > LifecycleExecutor.java:539) > ... 16 more > > This happens on teh build machine. It works fine on all the other > developer's machine. I have confirmed that the versions of maven, the > settings.xml are the same. This is with maven 2.0.6. > > Why won't maven print the real reason for the error? This stack trace > is useless. mvn -X doesn't provide any information that is useful > either. > > How do I debug this? > > -Moiz --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
