[
https://issues.apache.org/jira/browse/SUREFIRE-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17271066#comment-17271066
]
Tibor Digana commented on SUREFIRE-1788:
----------------------------------------
[~kriegaex]
Sorry, I have been working on totally different topic in Surefire project where
we are reworking the architecture and this is the biggest milestone release for
me.
I can interrupt my working copy and switch to this problem. After seen mine
comment I have understood what change is necessary to do. So I will create a PR
on GitHub and we can agree that you will make a test with the SNAPSHOT version.
I think this issue can be joined together with SUREFIRE-1801.
Can you push some a project at GH with a reproducible problem?
I am afraid if we redirect all the native stream of JVM to the console, the
users will obtain messy console logs.
T
> 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)
