[ http://jira.codehaus.org/browse/MSUREFIRE-137?page=all ]
     
Carlos Sanchez closed MSUREFIRE-137:
------------------------------------

     Assign To: Carlos Sanchez
    Resolution: Won't Fix

The output of tests goes to files in target/surefire-reports by default, or set 
-Dsurefire.useFile=false.

> failure reason not displayed
> ----------------------------
>
>          Key: MSUREFIRE-137
>          URL: http://jira.codehaus.org/browse/MSUREFIRE-137
>      Project: Maven 2.x Surefire Plugin
>         Type: Improvement

>     Versions: 2.2
>     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(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

Reply via email to