[
http://jira.codehaus.org/browse/SUREFIRE-741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chad Wilson closed SUREFIRE-741.
--------------------------------
Resolution: Fixed
Fix Version/s: 2.9
I have tested this in 2.8.2-SNAPSHOT (now 2.9-SNAPSHOT) and the behaviour has
been restored. Also, see Kristian's comment on SUREFIRE-704.
> Stdout/stderr is now not being included in XML test reports for test failures
> -----------------------------------------------------------------------------
>
> Key: SUREFIRE-741
> URL: http://jira.codehaus.org/browse/SUREFIRE-741
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Failsafe Plugin, Maven Surefire Plugin
> Affects Versions: 2.8, 2.8.1
> Reporter: Chad Wilson
> Fix For: 2.9
>
>
> In Surefire 2.8 and 2.8.1 there is no std-out and std-err being included in
> test reports for either the Surefire or Failsafe plugins. This means that
> tools like TeamCity cannot provide you with the associated test logging
> alongside your stacktrace when a test fails, making debugging on large CI
> builds very difficult.
> This appears to be caused inadvertently by some changes related to
> SUREFIRE-732.
--
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
