[
http://jira.codehaus.org/browse/SUREFIRE-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=145542#action_145542
]
Jörg Hohwiller commented on SUREFIRE-235:
-----------------------------------------
Using a JVM option is unsuiteable in my situation because we need a solution
for the entire team.
Acording to the documentation:
http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html
I could do this in my pom.xml
<build>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<configuration>
<useFile>false</useFile>
</configuration>
</plugin>
...
However it does NOT work (has no effect at all).
> failure reason not displayed
> ----------------------------
>
> Key: SUREFIRE-235
> URL: http://jira.codehaus.org/browse/SUREFIRE-235
> 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(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
