[
https://issues.apache.org/jira/browse/SUREFIRE-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17165247#comment-17165247
]
Alexander Kriegisch commented on SUREFIRE-1788:
-----------------------------------------------
Just to clarify and because I am just preparing a trip for 5 days and cannot
look into the source code now: In your last comment you were describing what
you discovered and what you are going to do in order to fix it, not suggesting
me to do that kind of stuff in order to customise Surefire on my own box,
correct? Because if there was any actionable item for me in your comment, I did
not get it. _(Sorry if this is a dumb question, writing this in the middle of
packing a suitcase.)_
> 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)
