maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tibor Digana (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (SUREFIRE-1410) Add FAQ and improve Warning message when native stream in forked JVM is corrupted
Date Sat, 09 Sep 2017 11:43:00 GMT

     [ https://issues.apache.org/jira/browse/SUREFIRE-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Tibor Digana closed SUREFIRE-1410.
----------------------------------
    Resolution: Fixed

https://git1-us-west.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=ead22a3d399a5fd608ebae90a079644ab786eae8

> Add FAQ and improve Warning message when native stream in forked JVM is corrupted
> ---------------------------------------------------------------------------------
>
>                 Key: SUREFIRE-1410
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1410
>             Project: Maven Surefire
>          Issue Type: Improvement
>          Components: Maven Failsafe Plugin, Maven Surefire Plugin
>            Reporter: Tibor Digana
>            Assignee: Tibor Digana
>              Labels: documentation
>             Fix For: 2.20.1
>
>
> Related to the discussion with contributors in SUREFIRE-1359.
> The message {{Corrupted stdin stream in forked JVM}} would become more specific {{Corrupted
STDOUT by directly writing to native stream in forked JVM}}.
> Then {{See the dump file}} would be extended to {{See FAQ web page and the dump file}}.
> These messages would appear just once in the console and not per fork as it was in prior
versions.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message