In simple words, the Failsafe plugin is designed to run **integration tests** while Surefire to run **unit tests**.


This is further explained in [Maven FAQ][1]:

&gt; - [`maven-surefire-plugin`][2] is designed for running **unit tests** and if any of the tests fail then it will fail the build immediately.

&gt; - [`maven-failsafe-plugin`][3] is designed for running **integration tests**, and decouples failing the build if there are test failures from actually running the tests.

&gt;   The name &quot;*failsafe*&quot; was chosen both because it is a synonym of surefire and because it implies that when it fails, it does so in a safe way.

&gt;  The **Failsafe Plugin** has two goals:

&gt;   - [`failsafe:integration-test`][4] runs the integration tests of an application,
&gt;   - [`failsafe:verify`][5] verifies that the integration tests of an application passed.

See also:

- [Benefits of Maven FailSafe Plugin][6] at SO


  [1]: http://maven.apache.org/surefire/maven-surefire-plugin/faq.html#surefire-v-failsafe
  [2]: https://maven.apache.org/surefire/maven-surefire-plugin/
  [3]: https://maven.apache.org/surefire/maven-failsafe-plugin/
  [4]: https://maven.apache.org/surefire/maven-failsafe-plugin/integration-test-mojo.html
  [5]: https://maven.apache.org/surefire/maven-failsafe-plugin/verify-mojo.html
  [6]: https://stackoverflow.com/q/9339086/55075

From https://maven.apache.org/surefire/maven-failsafe-plugin/, I would say that the difference between Surefire and Failsafe is the way they fail:

&gt; If you use the Surefire Plugin for running tests, then when you have a test failure, the build will stop at the integration-test phase and your integration test environment will not have been torn down correctly.
&gt;
&gt; The Failsafe Plugin is used during the integration-test and verify phases of the build lifecycle to execute the integration tests of an application. The Failsafe Plugin will not fail the build during the integration-test phase, thus enabling the post-integration-test phase to execute. 

 

In my country its the second google result when searching for &quot;maven failsafe maven surefire&quot; to get to this FAQ: [Difference between maven-failsafe-plugin and maven-surefire-plugin][1] which states:

&gt;*maven-surefire-plugin is designed for running unit tests and if any of the tests fail then it will fail the build immediately.*
&gt; 
&gt; *maven-failsafe-plugin is designed for running integration tests, and
&gt; decouples failing the build if there are test failures from actually
&gt; running the tests.&quot;*


  [1]: http://maven.apache.org/surefire/maven-surefire-plugin/faq.html#surefire-v-failsafe

Here are a series of cases where `echo $var` can show a different value than what was just assigned. This happens regardless of whether the assigned value was &quot;double quoted&quot;, &#39;single quoted&#39; or unquoted. 

How do I get the shell to set my variable correctly?

**Asterisks**

The expected output is `/* Foobar is free software */`, but instead I get a list of filenames:

    $ var=&quot;/* Foobar is free software */&quot;
    $ echo $var 
    /bin /boot /dev /etc /home /initrd.img /lib /lib64 /media /mnt /opt /proc ...



**Square brackets**

The expected value is `[a-z]`, but sometimes I get a single letter instead!

    $ var=[a-z]
    $ echo $var
    c

**Line feeds (newlines)**

The expected value is a  a list of separate lines, but instead all the values are on one line!

    $ cat file
    foo
    bar
    baz

    $ var=$(cat file)
    $ echo $var
    foo bar baz

**Multiple spaces**

I expected a carefully aligned table header, but instead multiple spaces either disappear or are collapsed into one!

    $ var=&quot;       title     |    count&quot;
    $ echo $var
    title | count

**Tabs**

I expected two tab separated values, but instead I get two space separated values!

    $ var=$&#39;key\tvalue&#39;
    $ echo $var
    key value


I just assigned a variable, but echo $variable shows something else

As I understand a promise is something that can resolve() or reject() but I was suprised to find out that code in the promise continues to execute after a resolve or reject is called.

I considered resolve or reject being an async-friendly version of exit &lt;n&gt; or return &lt;x&gt;, that would halt all immediate function execution.

Can someone explain the thought behind why the following example sometimes shows the console.log after a resolve call:

    var call = function() {
        return new Promise(function(resolve, reject) {
            resolve();
            console.log(&quot;Doing more stuff, should not be visible after a resolve!&quot;);
        });
    };
    
    call().then(function() {
        console.log(&quot;resolved&quot;);
    });

[jsbin][1]


  [1]: http://jsbin.com/sukacinayu/1/edit?js,console,output

Why does javascript ES6 Promises continue execution after a resolve?

What is the difference between Maven Surefire and Maven Failsafe plugins?  
I have searched all over web, but did not get the answer.

What is the difference between the Maven Surefire and Maven Failsafe plugins?

<p>What is the difference between Maven Surefire and Maven Failsafe plugins?<br>
I have searched all over web, but did not get the answer.</p>


I am looking at few maven tutorial videos and then I ran into this command after installing maven:

    mvn archetype:create -DgroupId=com.di.maven -DartifactId=hello-world

The build fails and throws the following error:

&lt;!-- language: none --&gt;

    Failed to execute goal org.apache.maven.plugins:maven-archetype-plugin:2.3:create 
    (default-cli) on project standalone-pom: Unable to parse configuration of mojo 
    org.apache.maven.plugins:maven-archetype-plugin:2.3:create for parameter #: Abstract 
    class or interface &#39;org.apache.maven.artifact.repository.ArtifactRepository&#39; cannot be 
    instantiated -&gt; [Help 1]

What is the reason and how can I fix it? I am running as an user in Ubuntu.

Unable to create a new maven hello-world project

I installed maven by following this steps:(a tutorial)

    JAVA_HOME=/Library/Java/Home
    export M2_HOME=/Users/steven/zimmermann/maven
    export M2=$M2_HOME/bin
    export PATH=$M2:$PATH

    echo $JAVA_HOME
    echo $M2_HOME
    echo $M2
    echo $PATH

    nano .bash_profile

then I wrote the echo in the .bash_profile sth like this:

    JAVA_HOME=/usr/libexec/java_home
    M2_HOME=/path/to/your/apache-maven-3.x.x
    M2=/path/to/your/apache-maven-3.x.x/bin
    PATH=/path/to/maven/bin:/$….bla-bla-bla…

and also I wrote this in the .bashrc

    export M2_HOME=/Users/steven/zimmermann/maven
    export M2=$M2_HOME/bin
    export PATH=$M2:$PATH

now when I want to check the version (`mvn -v`) I get the following exception:
I think there are some versions wrong, but I don&#39;t know. 

    Exception in thread &quot;main&quot; java.lang.UnsupportedClassVersionError: org/apache/maven/cli/MavenCli : Unsupported major.minor version 51.0
    	at java.lang.ClassLoader.defineClass1(Native Method)
    	at java.lang.ClassLoader.defineClassCond(ClassLoader.java:637)
    	at java.lang.ClassLoader.defineClass(ClassLoader.java:621)
    	at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141)
    	at java.net.URLClassLoader.defineClass(URLClassLoader.java:283)
    	at java.net.URLClassLoader.access$000(URLClassLoader.java:58)
    	at java.net.URLClassLoader$1.run(URLClassLoader.java:197)
    	at java.security.AccessController.doPrivileged(Native Method)
    	at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
    	at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClassFromSelf(ClassRealm.java:401)
    	at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:42)
    	at org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271)
    	at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:254)
    	at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239)
    	at org.codehaus.plexus.classworlds.launcher.Launcher.getMainClass(Launcher.java:144)
    	at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:266)
    	at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
    	at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
    	at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)

Additional information:

    java -version

&gt;     java version &quot;1.8.0_40&quot;
    Java(TM) SE Runtime Environment (build 1.8.0_40-b27)
    Java HotSpot(TM) 64-Bit Server VM (build 25.40-b25, mixed mode)

    javac -version

&gt;     javac 1.8.0_40


Maven Installation OSX Error Unsupported major.minor version 51.0

I&#39;m using maven in IntelliJ, JDK1.8, maven 3.2.5. Got compilation error: use -source 7 or higher to enable diamond opera. details are as follows: 

      [ERROR] COMPILATION ERROR : 
      [INFO] -------------------------------------------------------------
      [ERROR] TrainingConstructor.java:[31,55] diamond operator is not supported in -source 1.5 (use -source 7 or higher to enable diamond operator)
      [ERROR] DTM.java:[79,21] try-with-resources is not supported in -source 1.5  (use -source 7 or higher to enable try-with-resources)
      [ERROR] ticons.java:[53,44] diamond operator is not supported in -source 1.5  (use -source 7 or higher to enable diamond operator)

Any suggestions? Is there any other configuration to set this -source level? seems it doesn&#39;t use java 1.8. 

Maven Compilation Error: (use -source 7 or higher to enable diamond operator)

I just installed Maven 3.3.1 on Mac OS X, and building a Maven Project with Eclipse is giving me this error:
 
    -Dmaven.multiModuleProjectDirectory system property is not set.
    Check $M2_HOME environment variable and mvn script match.


It did not happen before with Maven 3.2.5.

Is there any way to fix this (except downgrading to 3.2.5) ?

Where exactly can I set this &quot;multiModuleProjectDirectory&quot; property in Eclipse?

Maven 3.3.1 ECLIPSE: -Dmaven.multiModuleProjectDirectory system propery is not set

I recently found out that the lombok.jar ends up in our final artifact, which shouldn&#39;t be necessary. In my understanding lombok is compile-time only.

            &lt;dependency&gt;
                &lt;groupId&gt;org.projectlombok&lt;/groupId&gt;
                &lt;artifactId&gt;lombok&lt;/artifactId&gt;
                &lt;version&gt;1.14.4&lt;/version&gt;
            &lt;/dependency&gt;

But when I set it to scope provided, I get strange behaviour in unit tests. They crash with ClassNotFoundExceptions then when trying to resolve 

    java.lang.NoClassDefFoundError: com/svv/esp/serviceimpl/dataimport/common/validation/LongValidator

Which maven scope is in general used for lombok?

I&#39;m using Oracle JDK build 1.8.0_25-b17 on MacOSX 10.9


Maven Scope for Lombok (Compile vs. Provided)

What is the use of the Maven Surefire Plugin? 
I can not find a proper example.



What is the use of Maven-Surefire plugin

I wrote a simple test method with JUnit 5:

    public class SimlpeTest {
        @Test
        @DisplayName(&quot;Some description&quot;)
        void methodName() {
            // Testing logic for subject under test
        }
    }
But when I run `mvn test`, I got:

    -------------------------------------------------------
     T E S T S
    -------------------------------------------------------
    Running SimlpeTest
    Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec
    
    Results :
    
    Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
Somehow, surefire didn&#39;t recognize that test class. My `pom.xml` looks like:

    &lt;properties&gt;
        &lt;java.version&gt;1.8&lt;/java.version&gt;
        &lt;junit.version&gt;5.0.0-SNAPSHOT&lt;/junit.version&gt;
    &lt;/properties&gt;

    &lt;dependencies&gt;
        &lt;dependency&gt;
            &lt;groupId&gt;org.junit&lt;/groupId&gt;
            &lt;artifactId&gt;junit5-api&lt;/artifactId&gt;
            &lt;version&gt;${junit.version}&lt;/version&gt;
            &lt;scope&gt;test&lt;/scope&gt;
        &lt;/dependency&gt;
    &lt;/dependencies&gt;

    &lt;repositories&gt;
        &lt;repository&gt;
            &lt;id&gt;snapshots-repo&lt;/id&gt;
            &lt;url&gt;https://oss.sonatype.org/content/repositories/snapshots&lt;/url&gt;
            &lt;releases&gt;
                &lt;enabled&gt;false&lt;/enabled&gt;
            &lt;/releases&gt;
            &lt;snapshots&gt;
                &lt;updatePolicy&gt;always&lt;/updatePolicy&gt;
                &lt;enabled&gt;true&lt;/enabled&gt;
            &lt;/snapshots&gt;
        &lt;/repository&gt;
    &lt;/repositories&gt;
           
    &lt;build&gt;
        &lt;plugins&gt;
            &lt;plugin&gt;
                &lt;artifactId&gt;maven-compiler-plugin&lt;/artifactId&gt;
                &lt;configuration&gt;
                    &lt;source&gt;${java.version}&lt;/source&gt;
                    &lt;target&gt;${java.version}&lt;/target&gt;
                &lt;/configuration&gt;
            &lt;/plugin&gt;
        &lt;/plugins&gt;
    &lt;/build&gt;
Any idea how to make this work?
       

Surefire is not picking up Junit 5 tests

Running maven (3.5.2) build of a **Spring Boot** 2.0.2.RELEASE applicaton (generated by web initialiser with web dependencies) fails executing the **maven-surefire-plugin** saying just:

&gt; Error: Could not find or load main class
org.apache.maven.surefire.booter.ForkedBooter

&gt;Caused by: java.lang.**ClassNotFoundException**: org.apache.maven.surefire.booter.**ForkedBooter**

Why is this happening? Is it a problem in boot + surefire integration = a bug? 

For reference, the dependencies that seem relevant are:

    &lt;parent&gt;
		&lt;groupId&gt;org.springframework.boot&lt;/groupId&gt;
		&lt;artifactId&gt;spring-boot-starter-parent&lt;/artifactId&gt;
		&lt;version&gt;2.0.2.RELEASE&lt;/version&gt;
		&lt;relativePath/&gt;
	&lt;/parent&gt;
    ...
    &lt;dependency&gt;
            &lt;groupId&gt;org.springframework.boot&lt;/groupId&gt;
            &lt;artifactId&gt;spring-boot-starter-test&lt;/artifactId&gt;
            &lt;scope&gt;test&lt;/scope&gt;
    &lt;/dependency&gt;
    ...
    &lt;dependency&gt;
			&lt;groupId&gt;org.springframework.boot&lt;/groupId&gt;
			&lt;artifactId&gt;spring-boot-starter-web&lt;/artifactId&gt;
    &lt;/dependency&gt;
    ...
    &lt;build&gt;
		&lt;plugins&gt;
            &lt;plugin&gt;
                &lt;groupId&gt;org.springframework.boot&lt;/groupId&gt;
                &lt;artifactId&gt;spring-boot-maven-plugin&lt;/artifactId&gt;
            &lt;/plugin&gt;
        &lt;/plugins&gt;
    &lt;/build&gt;


Spring Boot fails to run maven-surefire-plugin ClassNotFoundException org.apache.maven.surefire.booter.ForkedBooter

Recently coming to a new project, I&#39;m trying to compile our source code. Everything worked fine yesterday, but today is another story.

Every time I&#39;m running `mvn clean install` on a module, once reaching the tests, it crashes into an error:

    [INFO] --- maven-surefire-plugin:2.18.1:test (default-test) @ recorder ---
    [INFO] Surefire report directory: /lhome/code/recorder/target/surefire-reports
    [INFO] Using configured provider org.apache.maven.surefire.junitcore.JUnitCoreProvider
    [INFO] parallel=&#39;none&#39;, perCoreThreadCount=true, threadCount=0, useUnlimitedThreads=false, threadCountSuites=0,     threadCountClasses=0, threadCountMethods=0, parallelOptimized=true

    -------------------------------------------------------
     T E S T S
    -------------------------------------------------------
    Error: Could not find or load main class org.apache.maven.surefire.booter.ForkedBooter

    Results :

    Tests run: 0, Failures: 0, Errors: 0, Skipped: 0

and later on:

    [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.18.1:test (default-test) on project recorder: Execution default-test of goal org.apache.maven.plugins:maven-surefire-plugin:2.18.1:test failed: The forked VM terminated without properly saying goodbye. VM crash or System.exit called?

I&#39;m running on [Debian&amp;nbsp;9][1] (Stretch) 64-bits with OpenJDK 1.8.0_181, [Maven][2] 3.5.4, working behind my company proxy which I configured in my `~/.m2/settings.xml`.

A strange thing it that the latest Surefire version is 2.22.1 if I remember correctly. I tried to specify the plugin version, but it does not get updated, otherwise there&#39;s no plugin version specification in any [POM][3] (parent, grand-parent or this one).

I managed to force Maven to change the Surefire version to the latest, but now it&#39;s even worse:

    [INFO] -------------------------------------------------------
    [INFO]  T E S T S
    [INFO] -------------------------------------------------------
    [INFO]
    [INFO] Results:
    [INFO]
    [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0

    [...]

    [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.22.1:test (default-test) on project recorder:     There are test failures.
    [ERROR]
    [ERROR] Please refer to /lhome/code/recorder/target/surefire-reports for the individual test results.
    [ERROR] Please refer to dump files (if any exist) [date].dump, [date]-jvmRun[N].dump and [date].dumpstream.
    [ERROR] The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
    [ERROR] Command was /bin/sh -c cd /lhome/code/recorder/ &amp;&amp; /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java     &#39;-javaagent:/lhome1/johndoe/.m2/repository/org/jacoco/org.jacoco.agent/0.7.4.201502262128/org.jacoco.agent-0.7.4.201502262128-runt    ime.jar=destfile=/lhome/code/recorder/target/jacoco.exec,append=true,includes=esa/*,excludes=**/api/**/*.class&#39; -jar     /lhome/code/recorder/target/surefire/surefirebooter7426165516226884923.jar /lhome/code/recorder/target/surefire     2018-10-26T16-16-12_829-jvmRun1 surefire1721866559613511529tmp surefire_023400764142672144tmp
    [ERROR] Error occurred in starting fork, check output in log
    [ERROR] Process Exit Code: 1
    [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: The forked VM terminated without properly saying goodbye.     VM crash or System.exit called?
    [ERROR] Command was /bin/sh -c cd /lhome/code/recorder/ &amp;&amp; /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java     &#39;-javaagent:/lhome1/johndoe/.m2/repository/org/jacoco/org.jacoco.agent/0.7.4.201502262128/org.jacoco.agent-0.7.4.201502262128-runt    ime.jar=destfile=/lhome/code/recorder/target/jacoco.exec,append=true,includes=esa/*,excludes=**/api/**/*.class&#39; -jar     /lhome/code/recorder/target/surefire/surefirebooter7426165516226884923.jar /lhome/code/recorder/target/surefire     2018-10-26T16-16-12_829-jvmRun1 surefire1721866559613511529tmp surefire_023400764142672144tmp
    [ERROR] Error occurred in starting fork, check output in log
    [ERROR] Process Exit Code: 1
    [ERROR]     at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:669)
    [ERROR]     at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:282)
    [ERROR]     at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245)
    [ERROR]     at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1183)
    [ERROR]     at     org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:1011)
    [ERROR]     at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:857)
    [ERROR]     at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
    [ERROR]     at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
    [ERROR]     at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
    [ERROR]     at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
    [ERROR]     at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
    [ERROR]     at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
    [ERROR]     at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
    [ERROR]     at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
    [ERROR]     at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
    [ERROR]     at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
    [ERROR]     at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
    [ERROR]     at org.apache.maven.cli.MavenCli.execute(MavenCli.java:954)
    [ERROR]     at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
    [ERROR]     at org.apache.maven.cli.MavenCli.main(MavenCli.java:192)
    [ERROR]     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [ERROR]     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    [ERROR]     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    [ERROR]     at java.lang.reflect.Method.invoke(Method.java:498)
    [ERROR]     at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
    [ERROR]     at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
    [ERROR]     at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
    [ERROR]     at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)

  [1]: https://en.wikipedia.org/wiki/Debian_version_history#Debian_9_(Stretch)
  [2]: http://en.wikipedia.org/wiki/Apache_Maven
  [3]: https://en.wikipedia.org/wiki/Apache_Maven#Project_Object_Model



Maven surefire could not find ForkedBooter class

My JUnit tests are failing when running them through Maven and the Surefire plugin (version information below). I see the error message:

    Corrupted STDOUT by directly writing to native stream in forked JVM 4. See FAQ web page and the dump file C:\(...)\target\surefire-reports\2019-03-20T18-57-17_082-jvmRun4.dumpstream

The FAQ page points out some possible reasons but I don&#39;t see how I can use this information to start solving this problem:

&gt; Corrupted STDOUT by directly writing to native stream in forked JVM
&gt;
&gt; If your tests use native library which prints to STDOUT this warning message appears because the library corrupted the channel used by the plugin in order to transmit events with test status back to Maven process. It would be even worse if you override the Java stream by System.setOut because the stream is also supposed to be corrupted but the Maven will never see the tests finished and build may hang.
&gt;
&gt; This warning message appears if you use FileDescriptor.out or JVM prints GC summary.
&gt;
&gt; In that case the warning is printed &quot;Corrupted STDOUT by directly writing to native stream in forked JVM&quot;, and a dump file can be found in Reports directory.
&gt;
&gt; If debug level is enabled then messages of corrupted stream appear in the console. 


It refers to some native library printing out to STDOUT directly but how can I figure out which one, and even if I do, how do I deal with this issue if I need the library for my project?

It mentions &quot;debug level&quot; but it is unclear if this means Maven&#39;s debug level or Surefire plugin&#39;s debug level. I enabled Maven&#39;s debug but I don&#39;t see the console outputs as mentioned by the FAQ. And Surefire&#39;s debug option seems to be about pausing tests and waiting for a debugger to be connected to the process, not simply showing more information on the console.

The dump files also don&#39;t seem very helpful:

    # Created on 2019-03-20T18:42:58.323
    Corrupted STDOUT by directly writing to native stream in forked JVM 2. Stream &#39;FATAL ERROR in native method: processing of -javaagent failed&#39;.
    java.lang.IllegalArgumentException: Stream stdin corrupted. Expected comma after third character in command &#39;FATAL ERROR in native method: processing of -javaagent failed&#39;.
        at org.apache.maven.plugin.surefire.booterclient.output.ForkClient$OperationalData.&lt;init&gt;(ForkClient.java:511)
        at org.apache.maven.plugin.surefire.booterclient.output.ForkClient.processLine(ForkClient.java:209)
        at org.apache.maven.plugin.surefire.booterclient.output.ForkClient.consumeLine(ForkClient.java:176)
        at org.apache.maven.plugin.surefire.booterclient.output.ThreadedStreamConsumer$Pumper.run(ThreadedStreamConsumer.java:88)
        at java.base/java.lang.Thread.run(Thread.java:834)

So, how can I solve this problem?

**Update**: requested configuration information below.

I&#39;m using OpenJDK 11 (Zulu distribution) on Windows 10, Maven 3.5.3, and Surefire 2.21.0 (full configuration below).

I&#39;m running Maven from Eclipse using the &quot;Run As...&quot; context menu option on the `pom.xml` file, but obtain the same results when running it on the console.

I had never heard of JaCoco before the first comment to this question, but I see several error messages mentioning it:

    [ERROR] ExecutionException The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
    [ERROR] Command was cmd.exe /X /C &quot;&quot;C:\Program Files\Zulu\zulu-11\bin\java&quot; -javaagent:C:\\Users\\E26638\\.m2\\repository\\org\\jacoco\\org.jacoco.agent\\0.8.0\\org.jacoco.agent-0.8.0-runtime.jar=destfile=C:\\Users\\E26638\\git\\aic-expresso\\target\\jacoco.exec -Xms256m -Xmx1028m -jar C:\Users\E26638\AppData\Local\Temp\surefire10089630030045878403\surefirebooter8801585361488929382.jar C:\Users\E26638\AppData\Local\Temp\surefire10089630030045878403 2019-03-21T21-26-04_829-jvmRun12 surefire10858509118810158083tmp surefire_115439010304069944813tmp&quot;
    [ERROR] Error occurred in starting fork, check output in log
    [ERROR] Process Exit Code: 1

This is the Surefire Maven plugin configuration:

        &lt;plugin&gt;
            &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
            &lt;artifactId&gt;maven-surefire-plugin&lt;/artifactId&gt;
            &lt;version&gt;2.21.0&lt;/version&gt;
            &lt;configuration&gt;
                &lt;skipTests&gt;${skipUnitTests}&lt;/skipTests&gt;
                &lt;testFailureIgnore&gt;false&lt;/testFailureIgnore&gt;
                &lt;forkCount&gt;1.5C&lt;/forkCount&gt;
                &lt;reuseForks&gt;true&lt;/reuseForks&gt;
                &lt;parallel&gt;methods&lt;/parallel&gt;
                &lt;threadCount&gt;4&lt;/threadCount&gt;
                &lt;perCoreThreadCount&gt;true&lt;/perCoreThreadCount&gt;
                &lt;reportFormat&gt;plain&lt;/reportFormat&gt;
                &lt;trimStackTrace&gt;false&lt;/trimStackTrace&gt;
                &lt;redirectTestOutputToFile&gt;true&lt;/redirectTestOutputToFile&gt;
            &lt;/configuration&gt;
        &lt;/plugin&gt;








Content Type	Original Author	Original Content on Stackoverflow
Question	bugCracker	View Question on Stackoverflow
Solution 1 - Maven	kenorb	View Answer on Stackoverflow
Solution 2 - Maven	Jonas Wolf	View Answer on Stackoverflow
Solution 3 - Maven	JBA	View Answer on Stackoverflow

What is the difference between the Maven Surefire and Maven Failsafe plugins?

Maven Problem Overview

Maven Solutions

Solution 1 - Maven

Solution 2 - Maven

Solution 3 - Maven

Why does javascript ES6 Promises continue execution after a resolve?

I just assigned a variable, but echo $variable shows something else

Attributions