[
https://jira.codehaus.org/browse/SUREFIRE-772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=283978#comment-283978
]
Stephen Connolly commented on SUREFIRE-772:
-------------------------------------------
By default failsafe reports will not be generated unless the
target/failsafe-reports directory exists and contains at least one report .xml
file
surefire reports will retain their legacy behaviour of being generated always...
the new configuration elements
alwaysGenerateFailsafeReports (defaults to false)
alwaysGenerateSurefireReports (defaults to true)
can be used to invert this behaviour
Additionally, the configuration elements
skipFailsafeReport
skipSurefireReport
can be used to force skip the reports even when the data files are present
> [Report Goal] Skip Maven Failsafe Report
> ----------------------------------------
>
> Key: SUREFIRE-772
> URL: https://jira.codehaus.org/browse/SUREFIRE-772
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Maven Surefire Report Plugin
> Affects Versions: 2.10
> Reporter: Shelley Baker
> Fix For: 2.11
>
>
> With the release of the Maven Surefire Report Plugin 2.10, the failsafe
> report is now always generated along with the surefire report when the
> "report" goal is executed. Since our projects do not contain any integration
> tests run with the failsafe plugin, we do not want this report generated by
> default. It would be nice if the report goal exposed a configuration
> parameter that could be used to include/exclude individual reports (surefire
> / failsafe).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
