You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2007/01/21 23:29:26 UTC
[jira] Moved: (SUREFIRE-235) failure reason not displayed
[ http://jira.codehaus.org/browse/SUREFIRE-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter moved MSUREFIRE-137 to SUREFIRE-235:
-------------------------------------------------
Affects Version/s: (was: 2.0 (2.2 plugin))
Key: SUREFIRE-235 (was: MSUREFIRE-137)
Project: Maven Surefire (was: Maven 2.x Surefire Plugin)
> failure reason not displayed
> ----------------------------
>
> Key: SUREFIRE-235
> URL: http://jira.codehaus.org/browse/SUREFIRE-235
> Project: Maven Surefire
> Issue Type: Improvement
> Reporter: Jörg Hohwiller
> Assigned To: Carlos Sanchez
>
> Neigther with "mvn test" nor with "mvn -X test" I get the reason why a unit test fails.
> Of course I can run the test within my IDE but in my case it worked within the IDE and only did NOT work in maven2.
> After times of digging I found that there is a bug in sufrefire (MSUREFIRE-115) causing this problem.
> It would have saved me a lot of time if surefire would log the reason if a test fails. This should include stacktraces of Exceptions if started with -X. Currently I only get:
> Caused by: org.apache.maven.plugin.MojoFailureException: There are test failure.
> at org.apache.maven.plugin.surefire.SurefirePlugin.execute(SurefirePlugn.java:403)
> what is absolutely useless to track down the problem.
--
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