[
https://issues.apache.org/jira/browse/SUREFIRE-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17100375#comment-17100375
]
Alexander Kriegisch commented on SUREFIRE-1788:
-----------------------------------------------
I saw your commit this morning and created a new local build. Now I see:
{code}
[INFO] -------------------------------------------------------
[INFO] T E S T S
[INFO] -------------------------------------------------------
[INFO] premain
[ERROR] premain ERR
[INFO] Running de.scrum_master.bytebuddy.aspect.CommandLineAgentIT
{code}
I.e. it is working for both _stdOut_ and _stdErr_ now. BTW, the _stdErr_ output
always appears, the _stdOut_ only if I set {{<forkNode
implementation="org.apache.maven.plugin.surefire.extensions.SurefireForkNodeFactory"/>}}
as suggested by you. So I am looking forward to Surefire 3.0, even though I
wish it would somehow be possible to port it back to the 2.2 development line
and just "make it work" without having to configure a new protocol for the fork
node. Wishful thinking.
Thank you for your support in resolving this issue. :)
> 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)
