Philippe Deslauriers created MNG-7130:
-----------------------------------------
Summary: Integration with Jansi and windows console create JVM
fork errors with lots of output during tests
Key: MNG-7130
URL: https://issues.apache.org/jira/browse/MNG-7130
Project: Maven
Issue Type: Bug
Components: core
Affects Versions: 3.6.3
Reporter: Philippe Deslauriers
see my answer to this thread
[https://stackoverflow.com/a/66801171/1634131]
Build with lots of console ouput (15Mb+ in my case) in surefire / failsafe
tests fails with this error :
{{The forked VM terminated without saying properly goodbye. VM crash or
System.exit called}}
This happens even with -B (batch) option.
On a given project this would *fails systematically* in a new windows console
(cmd.exe)
{quote}[path_to_jdk]\java.exe -Dmaven.home=[path_to_maven]\apache-maven-3.6.3
-Dclassworlds.conf=[path_to_maven]\bin..\bin\m2.conf
-Dmaven.multiModuleProjectDirectory=[path_to_myproject] -Dfile.encoding=UTF-8
-Djansi.force=true -Djansi.passthrough=true -classpath
[path_to_maven]\boot\plexus-classworlds-2.6.0.jar
org.codehaus.plexus.classworlds.launcher.Launcher clean install -B
{quote}
This will *always works* in a new console window (cmd.exe).
{quote}[path_to_jdk]\java.exe -Dmaven.home=[path_to_maven]\apache-maven-3.6.3
-Dclassworlds.conf=[path_to_maven]\bin..\bin\m2.conf
-Dmaven.multiModuleProjectDirectory=[path_to_myproject] -Dfile.encoding=UTF-8
-Djansi.force=true -Djansi.passthrough=true -classpath
[path_to_maven]\boot\plexus-classworlds-2.6.0.jar
org.codehaus.plexus.classworlds.launcher.Launcher clean install -B
{quote}
Notice that both command have -B (batch mode which should turn off coloring),
and the only difference is
{{-Djansi.force=true -Djansi.passthrough=true}}
{{maven-surefire-plugin/useSystemClassLoader does not have an impact on test
results}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
