maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jörg Hohwiller (JIRA) <>
Subject [jira] Commented: (SUREFIRE-235) failure reason not displayed
Date Wed, 20 Aug 2008 12:01:26 GMT


Jörg Hohwiller commented on SUREFIRE-235:

According to the following link, this is the tracker category also for maven-surefire-report-plugin
and maven-surefire-plugin:

Beside its an Issue about maven-surefire-plugin as far as I understand.

Did I get something wrong?

> failure reason not displayed
> ----------------------------
>                 Key: SUREFIRE-235
>                 URL:
>             Project: Maven Surefire
>          Issue Type: Improvement
>    Affects Versions: 2.0 (2.2 plugin)
>            Reporter: Jörg Hohwiller
>            Assignee: 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(
> 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:
For more information on JIRA, see:


View raw message