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

Alexander Kriegisch edited comment on SUREFIRE-1788 at 1/25/21, 5:29 AM:
-------------------------------------------------------------------------

I gladly agree to re-test, of course. 😀

The project in question is [Sarek|https://github.com/SarekTest/Sarek]. Starting 
[here|https://github.com/SarekTest/Sarek/blob/master/pom.xml#L180], you can see 
my current configuration and also some comments concerning open issues. Change 
it to your heart's content, just play around with the settings in order to test 
different things. But the project has many modules, I did not create a 
dedicated, small reproducer. Maybe I could do that, but I was alway testing the 
real thing so far. Feel free to follow up with questions.


was (Author: kriegaex):
I gladly agree to re-test, of course. 😀

The project in question is [Sarek|https://github.com/SarekTest/Sarek]. Starting 
[here|https://github.com/SarekTest/Sarek/blob/master/pom.xml#L180], you can see 
my current configuration and play around with the settings.

> 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