[ 
https://issues.apache.org/jira/browse/SUREFIRE-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17814436#comment-17814436
 ] 

ASF GitHub Bot commented on SUREFIRE-1934:
------------------------------------------

michael-o commented on PR #670:
URL: https://github.com/apache/maven-surefire/pull/670#issuecomment-1927432700

   > Hey @michael-o, according to [a previous 
comment](https://github.com/apache/maven-surefire/pull/670#issuecomment-1863815281)
 it seems that the intention of @NissMoony was to provide an option for 
suppressing all output (irrespective of the type of the result) from the XML 
report.
   > 
   > For our use-case (Apache Hive), I think that disabling all output from the 
**XML report** is sufficient to move our upgrade further assuming that 
`redirectTestOutputToFile` option works as before and will still send the 
STDOUT to a file irrespective of the the changes introduced by this PR.
   > 
   > Having more fine grained configurations (e.g., only apply this on 
successful/failed tests) may be a nice to have feature but not a strong 
requirement from our side at this point. We all understand that complex 
configurations are hard to maintain.
   
   The code contradicts the issue summary. Either one should be picked.




> Ability to disable system-out/system-err for successfuly passed tests
> ---------------------------------------------------------------------
>
>                 Key: SUREFIRE-1934
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1934
>             Project: Maven Surefire
>          Issue Type: Improvement
>          Components: Maven Surefire Plugin
>    Affects Versions: 3.0.0-M5
>            Reporter: Andrey Turbanov
>            Priority: Major
>
> After SUREFIRE-1744 surefire-plugin always reports system-out/system-err even 
> for successfully passed test. A lot of old projects with big amount of tests 
> now have to deal with huge output.
> I think there should be option to disable new behavior.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to