[
https://issues.apache.org/jira/browse/SUREFIRE-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17271023#comment-17271023
]
Alexander Kriegisch edited comment on SUREFIRE-1788 at 1/25/21, 2:08 AM:
-------------------------------------------------------------------------
[~tibordigana], this is still open AFAIK, so may I after 6 months kindly ask
you to fix this? You said before that you know what needs to be done and I
explained why I am not confident to contribute here because I am a mere Maven
user and have never written a mojo or plugin. This still holds true as of today.
Let me know if you wish to have a new issue created for this. I see that the
old feature branch for this issue has been merged and deleted already.
was (Author: kriegaex):
[~tibordigana], this is still open AFAIK, so may I after 6 months kindly ask
you to fix this? You said before that you know what needs to be done and I
explained why I am not confident to contribute here because I am a mere Maven
user and have never written a mojo or plugin. This still holds true as of today.
> 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)
