[
https://issues.apache.org/jira/browse/SUREFIRE-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17264759#comment-17264759 ]
Tibor Digana commented on SUREFIRE-1780:
----------------------------------------
[~vaik.duhautois]
Previously the error stream went to the dump file and nobody was watching it.
Now it goes to the console.
I do not know why the Junit library writes to the error stream, or why the JVM pipeline std/out is corrupted.
Can you provide more details about your project and Maven command?
> Print JPMS errors from native stream of the fork JVM
> ----------------------------------------------------
>
> Key: SUREFIRE-1780
> URL:
https://issues.apache.org/jira/browse/SUREFIRE-1780> Project: Maven Surefire
> Issue Type: Improvement
> Components: process forking
> Environment: Java 9+
> Reporter: Tibor Digana
> Assignee: Tibor Digana
> Priority: Major
> Fix For: 3.0.0-M5
>
>
> When JVM prints own logs to the native stream, the surefire stream becomes corrupted. These are printed in a dump file and they are supposed a stream corruption. We can extract some special logs from this corrupted stream.
> This issue is based on the last discussion in SUREFIRE-1262.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
Locked
