[
http://jira.codehaus.org/browse/SUREFIRE-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105895
]
Brett Porter commented on SUREFIRE-339:
---------------------------------------
that seems to be a different problem - perhaps there is already an open
surefire bug for that?
The fix I put in pace for this is simply to say that the test failures can be
found in "target/surefire-reports" (or other directory if that is configured)
> Surefire plugin error message does not indicate the source of the error.
> ------------------------------------------------------------------------
>
> Key: SUREFIRE-339
> URL: http://jira.codehaus.org/browse/SUREFIRE-339
> Project: Maven Surefire
> Issue Type: Bug
> Affects Versions: 2.3
> Environment: maven 2.0.6
> jdk 1.5.0_08
> Windows 2003
> Reporter: md
> Assignee: Brett Porter
> Fix For: 2.3.1
>
>
> I have been getting test failures. But maven provides no hints as to the root
> cause of the failures. I have tried using the -X and the -e options, but all
> I get is this. I don't konw if this is a maven issue or a surefire plugin
> issue. But, the exceptions should have enough data on what tests failed. This
> has made it impossible for us to track down the issue. This doesn't happend
> on developer machines. It only happens on teh build machine that we are
> trying to setup.
> The command we ran was:
> mvn -e clean test
> [ERROR] BUILD FAILURE
> INFO] ------------------------------------------------------------------------
> INFO] There are test failures.
> INFO] ------------------------------------------------------------------------
> INFO] Trace
> rg.apache.maven.BuildFailureException: There are test failures.
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:560)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.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.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.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)
> aused by: org.apache.maven.plugin.MojoFailureException: There are test
> failures.
> at
> org.apache.maven.plugin.surefire.SurefirePlugin.execute(SurefirePlugin.java:425)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
> ... 16 more
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
