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

Tibor Digana commented on SUREFIRE-1788:
----------------------------------------

That's worth we can see the user experience.
Now you can see the native calls penetration, not normally handled as std/out 
and std/err in Java, but we can give you more control over the console.

This is the configuration, as an example, taken from our 
[documentation|https://maven.apache.org/surefire/maven-failsafe-plugin/examples/junit-platform.html].
 We can add anything here. For instance a control for the unhandled console 
logs which penetrated from the fork JVM to your console. So we may design new 
parameters in M6 to switch on/off this penetration.

{noformat}
<consoleOutputReporter 
implementation="org.apache.maven.plugin.surefire.extensions.junit5.JUnit5ConsoleOutputReporter">
    <disable>false</disable>
    <encoding>UTF-8</encoding>
    <usePhrasedFileName>false</usePhrasedFileName>
</consoleOutputReporter>
{noformat}


> Unhandled native logs in SurefireForkChannel
> --------------------------------------------
>
>                 Key: SUREFIRE-1788
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1788
>             Project: Maven Surefire
>          Issue Type: Task
>          Components: Maven Failsafe Plugin, Maven Surefire Plugin, process 
> forking
>            Reporter: Tibor Digana
>            Assignee: Tibor Digana
>            Priority: Major
>             Fix For: 3.0.0-M5
>
>
> This is related only to the internal change of the version 3.0.0-M5 itself.
> The 
> [stdOut|https://github.com/apache/maven-surefire/blob/master/maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/extensions/SurefireForkChannel.java#L153]
>  should be printed to INFO on the console.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to