I&#39;m using Jenkins, Maven 3.1, and Java 1.6.  I have the following Maven job set up in Jenkins with the following goals and options ...

    clean install -U -P cloudbees -P qa

below is my pom.xml surefire 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.17&lt;/version&gt;
            &lt;configuration&gt;
                    &lt;reuseForks&gt;true&lt;/reuseForks&gt;
                    &lt;argLine&gt;-Xmx2048m -XX:MaxPermSize=512M &lt;/argLine&gt;
                    &lt;skipTests&gt;false&lt;/skipTests&gt;
            &lt;/configuration&gt;
    &lt;/plugin&gt;

However, when my unit tests fail, the Jenkins console output still says &quot;BUILD SUCCESS&quot; and the build is marked as &quot;unstable&quot; instead of outright failing.  How do I configure things in Jenkins (or Maven if taht&#39;s what it turns out to be) so that my build fails (not becomes unstable or passes) if any of the unit tests fail?

Below is what the console output says

	17:08:04   MyProjectOrganizationControllerTest.testRecoverFromError &#187; IllegalState Failed to...
	17:08:04   MyProjectOrganizationControllerTest.testVerifyDistrictListPopulated &#187; IllegalState
	17:08:04   MyProjectOrganizationControllerTest.testUpdateSchool &#187; IllegalState Failed to loa...
	17:08:04   MyProjectOrganizationControllerTest.testDeleteSchool &#187; IllegalState Failed to loa...
	17:08:04   MyProjectOrganizationControllerTest.testVerifyOrgListPopulatedPrivateSchoolOrgType &#187; IllegalState
	17:08:04   MyProjectOrganizationControllerTest.testSubmitMultipleParams &#187; IllegalState Faile...
	17:08:04 
	17:08:04 Tests run: 155, Failures: 0, Errors: 154, Skipped: 1
	17:08:04 
	17:08:04 [ERROR] There are test failures.
	17:08:04 
	17:08:04 Please refer to /scratch/jenkins/workspace/MyProject/MyProject/target/surefire-reports for the individual test results.
	17:08:04 [JENKINS] Recording test results
	17:08:07 log4j:WARN No appenders could be found for logger (org.apache.commons.beanutils.converters.BooleanConverter).
	17:08:07 log4j:WARN Please initialize the log4j system properly.
	17:08:14 [INFO] 
	17:08:14 [INFO] --- maven-war-plugin:2.4:war (default-war) @ MyProject ---
	17:08:15 [INFO] Packaging webapp
	17:08:15 [INFO] Assembling webapp [MyProject] in [/scratch/jenkins/workspace/MyProject/MyProject/target/MyProject]
	17:08:15 [INFO] Processing war project
	17:08:15 [INFO] Copying webapp resources [/scratch/jenkins/workspace/MyProject/MyProject/src/main/webapp]
	17:08:15 [INFO] Webapp assembled in [662 msecs]
	17:08:15 [INFO] Building war: /scratch/jenkins/workspace/MyProject/MyProject/target/MyProject.war
	17:08:20 [INFO] 
	17:08:20 [INFO] --- maven-failsafe-plugin:2.17:integration-test (default) @ MyProject ---
	17:08:20 [JENKINS] Recording test results
	17:08:25 [INFO] 
	17:08:25 [INFO] --- maven-failsafe-plugin:2.17:verify (default) @ MyProject ---
	17:08:25 [INFO] Failsafe report directory: /scratch/jenkins/workspace/MyProject/MyProject/target/failsafe-reports
	17:08:25 [JENKINS] Recording test results[INFO] 
	17:08:25 [INFO] --- maven-install-plugin:2.4:install (default-install) @ MyProject ---
	17:08:25 
	17:08:25 [INFO] Installing /scratch/jenkins/workspace/MyProject/MyProject/target/MyProject.war to /home/jenkins/.m2/repository/org/mainco/subco/MyProject/76.0.0-SNAPSHOT/MyProject-76.0.0-SNAPSHOT.war
	17:08:25 [INFO] Installing /scratch/jenkins/workspace/MyProject/MyProject/pom.xml to /home/jenkins/.m2/repository/org/mainco/subco/MyProject/76.0.0-SNAPSHOT/MyProject-76.0.0-SNAPSHOT.pom
	17:08:26 Started calculate disk usage of build
	17:08:26 Finished Calculation of disk usage of build in 0 seconds
	17:08:26 Started calculate disk usage of workspace
	17:08:26 Finished Calculation of disk usage of workspace in 0 seconds
	17:08:26 [INFO] ------------------------------------------------------------------------
	17:08:26 [INFO] BUILD SUCCESS
	17:08:26 [INFO] ------------------------------------------------------------------------
	17:08:26 [INFO] Total time: 11:00.616s
	17:08:26 [INFO] Finished at: Mon Feb 23 17:08:26 UTC 2015
	17:08:27 [INFO] Final Memory: 90M/414M
	17:08:27 [INFO] ------------------------------------------------------------------------
	17:08:27 Waiting for Jenkins to finish collecting data
	17:08:28 [JENKINS] Archiving /scratch/jenkins/workspace/MyProject/MyProject/pom.xml to org.mainco.subco/MyProject/76.0.0-SNAPSHOT/MyProject-76.0.0-SNAPSHOT.pom
	17:08:28 [JENKINS] Archiving /scratch/jenkins/workspace/MyProject/MyProject/target/MyProject.war to org.mainco.subco/MyProject/76.0.0-	SNAPSHOT/MyProject-76.0.0-SNAPSHOT.war
	17:08:31 channel stopped
	17:08:31 Started calculate disk usage of build
	17:08:31 Finished Calculation of disk usage of build in 0 seconds
	17:08:31 Started calculate disk usage of workspace
	17:08:31 Finished Calculation of disk usage of workspace in 0 seconds
	17:08:31 Finished: UNSTABLE


How do I make Jenkins build fail when Maven unit tests fail?

We have a hundreds of tests defined for our integration-test phase lifecycle in maven, and they take a long time to finish.

What I want to do is run just one test in the `integration-test`. I tried doing :

    mvn -Dtest=&lt;my-test&gt; integration-test

but that does not work. The `-Dtest` runs only the tests in the unit test goal, not the integration-test phase. I tried the `-Dintegration-test=&lt;my-test&gt;` instead, and that was ignored.

Is there a way to do that ? 

---

My configuration is:

	&lt;plugin&gt; 
		&lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt; 
		&lt;artifactId&gt;maven-surefire-plugin&lt;/artifactId&gt; 
		&lt;executions&gt; 
			&lt;execution&gt; 
				&lt;id&gt;surefire-it&lt;/id&gt; 
				&lt;phase&gt;integration-test&lt;/phase&gt; 
				&lt;goals&gt; 
					&lt;goal&gt;test&lt;/goal&gt; 
				&lt;/goals&gt; 
				&lt;configuration&gt; 
					&lt;excludes&gt; 
						&lt;exclude&gt;none&lt;/exclude&gt; 
					&lt;/excludes&gt; 
					&lt;includes&gt;
						&lt;include&gt;**/api/**&lt;/include&gt; 
					&lt;/includes&gt; 
		..... 

How to run individual test in the integration-test target in maven

I have a project with several modules. When all tests pass, Maven test runs them all.

When tests fail in the first module, maven will not continue to the next project. I have testFailureIgnore set to true in Surefire settings, but it doesn&#39;t help.

How do I make maven run all tests regardless of earlier failures?

Making Maven run all tests, even when some fail

Please help me to solve this issue. I do not exactly understand what the error in the log means.

    [INFO] ------------------------------------------------------------------------
    [INFO] BUILD FAILURE
    [INFO] ------------------------------------------------------------------------
    [INFO] Total time: 21.749s
    [INFO] Finished at: Thu Apr 24 10:10:20 IST 2014
    [INFO] Final Memory: 15M/37M
    [INFO] ------------------------------------------------------------------------
    [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.15:test (default-test) on project samples.simpleforwarding: Execution default-test of goal org.apache.maven.plugins:maven-surefire-plugin:2.15:test failed: The forked VM terminated without saying properly goodbye. VM crash or System.exit called ?
    [ERROR] Command wascmd.exe /X /C &quot;&quot;C:\Program Files\Java\jdk1.7.0_55\jre\bin\java&quot; -Xmx1024m -XX:MaxPermSize=256m -jar E:\OpenDayLight\controller\opendaylight\samples\simpleforwarding\target\surefire\surefirebooter53410321571238933.jar E:\OpenDayLight\controller\opendaylight\samples\simpleforwarding\target\surefire\surefire86076271125218001tmp E:\OpenDayLight\controller\opendaylight\samples\simpleforwarding\target\surefire\surefire_01846991116135903536tmp&quot;
    [ERROR] -&gt; [Help 1]
    [ERROR] 
    [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
    [ERROR] Re-run Maven using the -X switch to enable full debug logging.
    [ERROR] 
    [ERROR] For more information about the errors and possible solutions, please read the following articles:
    [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException



The forked VM terminated without saying properly goodbye. VM crash or System.exit called

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

How can I get the maven-release-plugin to run without triggering the tests?  

I have tried

    -Dmaven.test.skip=true 
and 

    -DskipTests 
and 

    -DpreparationGoals=clean

...yet none work.


Yes, I know I shouldn&#39;t release if the tests don&#39;t pass, but I don&#39;t have control over making my coworkers write reliable tests.  



How can I get maven-release-plugin to skip my tests?

I&#39;ve a Maven build in which I use the SureFire plugin to run some unit tests, and the FailSafe plugin to run some integration tests.  I would like a way to run just the FailSafe plugin&#39;s tests.

It&#39;s not a good solution for me to add different profiles or anything in the pom, because it&#39;s a multimodule build and I don&#39;t want to have to edit every module&#39;s pom.

There are `skip.tests` and `maven.test.skip` and `skipTests` which stop _all_ tests, and [`skipITs`][1], which stops only the failsafe plugin.

So, is there a command-line flag for Maven like `skipITs`, but instead with the functionality of &quot;onlyITs&quot;?


  [1]: http://maven.apache.org/plugins/maven-failsafe-plugin/verify-mojo.html#skipITs


Prevent unit tests but allow integration tests in Maven

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

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?

I&#39;d like to see the stacktrace of unit tests in the console. Does surefire support this?

Make maven&#39;s surefire show stacktrace in console

I get the following error when running Unit tests in IntelliJ:
Error: Could not find or load main class ${surefireArgLine}.
I am using maven and in pom.xml I have:

    &lt;properties&gt;
        ...
        &lt;surefire.argLine /&gt;
    &lt;/properties&gt;

	&lt;build&gt;
		&lt;plugins&gt;
			&lt;plugin&gt;
				&lt;groupId&gt;com.mysema.maven&lt;/groupId&gt;
				&lt;artifactId&gt;apt-maven-plugin&lt;/artifactId&gt;
				&lt;version&gt;1.1.1&lt;/version&gt;
				&lt;executions&gt;
					&lt;execution&gt;
						&lt;goals&gt;
							&lt;goal&gt;process&lt;/goal&gt;
						&lt;/goals&gt;
						&lt;configuration&gt;
							&lt;outputDirectory&gt;target/generated-sources/java&lt;/outputDirectory&gt;
							&lt;processor&gt;com.mysema.query.apt.jpa.JPAAnnotationProcessor&lt;/processor&gt;
						&lt;/configuration&gt;
					&lt;/execution&gt;
				&lt;/executions&gt;
			&lt;/plugin&gt;

			&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.17&lt;/version&gt;
			&lt;configuration&gt;
				 &lt;!--Sets the VM argument line used when unit tests are run.--&gt;
                &lt;argLine&gt;${surefire.argLine}&lt;/argLine&gt;
			&lt;/configuration&gt;
		&lt;/plugin&gt;
      &lt;plugin&gt;
                &lt;groupId&gt;org.jacoco&lt;/groupId&gt;
                &lt;artifactId&gt;jacoco-maven-plugin&lt;/artifactId&gt;
                &lt;version&gt;0.7.1.201405082137&lt;/version&gt;
                &lt;executions&gt;
                    &lt;!--
                        Prepares the property pointing to the JaCoCo runtime agent which
                        is passed as VM argument when Maven the Surefire plugin is executed.
                    --&gt;
                    &lt;execution&gt;
                        &lt;id&gt;pre-unit-test&lt;/id&gt;
                        &lt;goals&gt;
                            &lt;goal&gt;prepare-agent&lt;/goal&gt;
                        &lt;/goals&gt;
                        &lt;configuration&gt;
                            &lt;!--Sets the path to the file which contains the execution data.--&gt;
                            &lt;destFile&gt;${project.build.directory}/coverage-reports/jacoco-ut.exec&lt;/destFile&gt;
                            &lt;!--
                                Sets the name of the property containing the settings
                                for JaCoCo runtime agent.
                            --&gt;
                            &lt;propertyName&gt;surefireArgLine&lt;/propertyName&gt;
                        &lt;/configuration&gt;
                    &lt;/execution&gt;
       ...

Did anyone have similiar problem? How to set value for surefireArgLine?

IntelliJ Error when running unit test: Could not find or load main class ${surefireArgLine}

Using JUnit 4.8 and the new `@Category` annotations, is there a way to choose a subset of categories to run with Maven&#39;s Surefire plugin?

For example I have:

    @Test
    public void a() {
    }

    @Category(SlowTests.class)
    @Test
    public void b() {
    }

And I&#39;d like to run all non-slow tests as in: (note that the -Dtest.categories was made up by me...).

    mvn test -Dtest.categories=!SlowTests // run non-slow tests
    mvn test -Dtest.categories=SlowTests // run only slow tests
    mvn test -Dtest.categories=SlowTests,FastTests // run only slow tests and fast tests
    mvn test // run all tests, including non-categorized

So the point is that I don&#39;t want to have to create test suites (Maven just picks up all unit tests in the project which is very convenient) and I&#39;d like Maven to be able to pick the tests by category.
I think I just made up the -Dtest.categories, so I was wondering if there&#39;s a similar facility I can use?

How to run JUnit tests by category in Maven?

I am using maven with the _jacoco_ plugin to generate code coverage metrics. I am having some difficulty in configuring the _surefire_ plugin with the java options required by the _jacoco_ plugin. I&#39;ve seen some answers about this already on Stack Overflow but something is not working for me.

I have a multi-module project, and one of my modules configures the _surefire_ plugin as follows:

`foo/pom.xml`:

    &lt;plugins&gt;
      &lt;plugin&gt;
        &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
        &lt;artifactId&gt;maven-surefire-plugin&lt;/artifactId&gt;
        &lt;configuration&gt;
          &lt;argLine&gt;-XX:MaxPermSize=512m&lt;/argLine&gt;
        &lt;/configuration&gt;
      &lt;/plugin&gt;
    &lt;/plugins&gt;

This works as expected.

Now I want to incorporate jacoco to get code coverage metrics, so I added a _CodeCoverage_ profile that handles all the jacoco configuration:

`parent/pom.xml`:

    &lt;profile&gt;
      &lt;id&gt;CodeCoverage&lt;/id&gt;
      &lt;build&gt;
        &lt;pluginManagement&gt;
          &lt;plugins&gt;
            &lt;plugin&gt;
              &lt;groupId&gt;org.jacoco&lt;/groupId&gt;
              &lt;artifactId&gt;jacoco-maven-plugin&lt;/artifactId&gt;
              &lt;executions&gt;
                &lt;execution&gt;
                  &lt;id&gt;jacoco-initialize&lt;/id&gt;
                  &lt;goals&gt;&lt;goal&gt;prepare-agent&lt;/goal&gt;&lt;/goals&gt;
                  &lt;configuration&gt;
                    &lt;propertyName&gt;surefire.argLine&lt;/propertyName&gt;
                  &lt;/configuration&gt;
                  ...
                &lt;/execution&gt;
              &lt;executions&gt; 
            &lt;/plugin&gt;
          &lt;/plugins&gt;
        &lt;/pluginManagement&gt;
      &lt;/build&gt;   
    &lt;/profile&gt;

It is seen here that if the _CodeCoverage_ profile is specified, then the _jacoco_ plugin is configured to use the `surefire.argLine` property, and that property is used to configure the `argLine` for the _surefire_ plugin.

I then updated the _pom.xml_ file for the _foo_ module to use the `surefire.argLine` property generated by the _jacoco_ plugin:

`foo/pom.xml`:

    &lt;plugins&gt;
      &lt;plugin&gt;
        &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
        &lt;artifactId&gt;maven-surefire-plugin&lt;/artifactId&gt;
        &lt;configuration&gt;
          &lt;argLine&gt;${surefire.argLine} -XX:MaxPermSize=512m&lt;/argLine&gt;
        &lt;/configuration&gt;
      &lt;/plugin&gt;
    &lt;/plugins&gt;

This approach is specified in the _jacoco_ plugin documentation (see [1]).

When I build the _foo_ module with the _CodeCoverage_ profile, I see the following:

    [foo] $ mvn clean install -X -PCodeCoverage
    ...
    [INFO] --- jacoco-maven-plugin:0.7.0.201403182114:prepare-agent (jacoco-initialize) @ foo ---
    [INFO] surefire.argLine set to -javaagent:...\\org.jacoco.agent\\0.7.0.201403182114\\org.jacoco.agent-0.7.0.201403182114-runtime.jar=destfile=...\foo\\\target\\coverage-reports\\jacoco-ut.exec
    ...
    [DEBUG] Configuring mojo &#39;org.apache.maven.plugins:maven-surefire-plugin:2.13:test&#39; with basic configurator --&gt;
    [DEBUG]   (s) argLine = -javaagent:...\\org.jacoco.agent\\0.7.0.201403182114\\org.jacoco.agent-0.7.0.201403182114-runtime.jar=destfile=...\\foo\\target\\coverage-reports\\jacoco-ut.exec -XX:MaxPermSize=512m
    ...
    [INFO] --- jacoco-maven-plugin:0.7.0.201403182114:report (jacoco-site) @ foo ---
    [INFO] Analyzed bundle &#39;Foo&#39; with 59 classes`

So the _jacoco_ plugin is executed, a `surefire.argLine` property is created, the `argLine` for the _surefire_ plugin uses the `surefire.argLine` property and the local `MaxPermSize` argument, and a `target\code-coverage\jacoc-ut-exec` file is generated, as expected.

However, if I do not use the _CodeCoverage_ profile, then I get an error, because the `${surefire.argLine}` property (used in `foo/pom.xml`) is not created by the _jacoco_ plugin, and is not defined anywhere:

    [foo] $ mvn clean install -X
    ...
    [DEBUG] Configuring mojo &#39;org.apache.maven.plugins:maven-surefire-plugin:2.13:test&#39; with basic configurator --&gt;
    [DEBUG]   (s) argLine = ${surefire.argLine} -XX:MaxPermSize=512m
    ...
    Error: Could not find or load main class ${surefire.argLine}`

Sinec the _jacoco_ plugin was not invoked, there&#39;s no `surefire.argLine` property created, hence the error. 

So, I go back to the `parent/pom.xml` and create this property, with no initial value:

`parent/pom.xml`:

    &lt;properties&gt;
      &lt;surefire.argLine&gt;&lt;/surefire.argLine&gt;
    &lt;/properties&gt;

Now when I build the _foo_ module without using the _CodeCoverage_ profile, I get no errors:

    [foo] $ mvn clean install -X
    ...
    [DEBUG] Configuring mojo &#39;org.apache.maven.plugins:maven-surefire-plugin:2.13:test&#39; with basic configurator --&gt;
    [DEBUG]   (s) argLine =  -XX:MaxPermSize=512m
    ...
    [INFO] BUILD SUCCESS`

The _surefire_ argline is now correct (using the empty `surefire.argLine` property) and there is no `target\code-coverage` directory, as expected.

So now I go back to generating code metrics, using the _CodeCoverage_ profile:

    [foo] $ mvn clean install -X -PCodeCoverage
    ...
    [INFO] --- jacoco-maven-plugin:0.7.0.201403182114:prepare-agent (jacoco-initialize) @ foo ---
    [INFO] surefire.argLine set to -javaagent:...\\org.jacoco.agent\\0.7.0.201403182114\\org.jacoco.agent-0.7.0.201403182114-runtime.jar=destfile=...\\foo\\target\\coverage-reports\\jacoco-ut.exec
    ...
    [DEBUG] Configuring mojo &#39;org.apache.maven.plugins:maven-surefire-plugin:2.13:test&#39; with basic configurator --&gt;
    [DEBUG]   (s) argLine =  -XX:MaxPermSize=512m
    ...
    [INFO] --- jacoco-maven-plugin:0.7.0.201403182114:report (jacoco-site) @ foo ---
    [INFO] Skipping JaCoCo execution due to missing execution data file:...\foo\target\coverage-reports\jacoco-ut.exec

It can be observed here that the _jacoco_ plugin is invoked and sets the `surefire.argLine` property, but the `surefire.argLine` property with the empty value defined in the `parent/pom.xml` file is actually used to create the argline for the _surefire_ plugin.

As a result, there is no `jacoco-ut.exec` file, and no `target\code-coverage` directory, when I use the _CodeCoverage_ profile.

I&#39;m not sure what I am doing wrong here. I&#39;m declaring an `argLine` property as suggested by the _jacoco_ documentation, and using it whenever a _surefire_ plugin needs to specify additional argument. Other answers on Stack Overflow suggest creating a property with the same name as the _jacoco_ argLine property to handle the case when _jacoco_ is not invoked.

Any suggestions?


**edit** 

Maybe one solution is to explicitly declare the `surefire.argLine` property in the _CodeCoverage_ profile, and forget about using the `argLine` of the _jacoco_ plugin:

    &lt;profile&gt;
      &lt;id&gt;CodeCoverage&lt;/id&gt;
      &lt;properties&gt;
        &lt;surefire.argLine&gt;-javaagent:${jacoco.agent.jar}=destfile=${jacoco.report.path}&lt;/surefire.argLine&gt;
      &lt;/properties&gt;
      &lt;build&gt;
        &lt;plugins&gt;
          &lt;plugin&gt;
            &lt;groupId&gt;org.jacoco&lt;/groupId&gt;
            &lt;artifactId&gt;jacoco-maven-plugin&lt;/artifactId&gt;
            &lt;executions&gt;
              &lt;execution&gt;
                &lt;id&gt;jacoco-initialize&lt;/id&gt;
                &lt;goals&gt;
                  &lt;goal&gt;prepare-agent&lt;/goal&gt;
                &lt;/goals&gt;
                &lt;!-- no longer specifying &#39;argLine&#39; for jacoco plugin ... --&gt;  
              &lt;/execution&gt;
            &lt;executions&gt; 
          &lt;/plugin&gt;
          &lt;plugin&gt;
            &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
            &lt;artifactId&gt;maven-surefire-plugin&lt;/artifactId&gt;
            &lt;configuration&gt;
              &lt;!-- ... instead the arg line is configured explicitly for surefire plugin. --&gt;
              &lt;argLine&gt;${surefire.argLine}&lt;/argLine&gt;
            &lt;/configuration&gt;
          &lt;/plugin&gt;
        &lt;/plugins&gt;
      &lt;/plugin&gt;
    &lt;/build&gt;
  &lt;/profile&gt;

This will create the _surefire.argLine_ property to use the java agent required by the _jacoco_ plugin, and configure the _surefire_ plugin to use that property for its JVM args. The _jacoco_ plugin will now create a _argLine_ property, but this will be ignored. It&#39;s not an elegant solution (since I&#39;m making assumptions about how the _jacoco_ plugin works, and this may change in a future version).

**edit** 

The `jacoco.agent.jar` property must also be set, by pointing to its location in the local repository (not sure if this is robust) or by using the _dependency_ plugin to copy the _jacoco_ agent jar to the local build directory:

    &lt;profile&gt;
      &lt;id&gt;CodeCoverage&lt;/id&gt;
      &lt;properties&gt;
        &lt;jacoco.agent.jar&gt;${project.build.directory}/jacoco-agent.jar&lt;/jacoco.agent.jar&gt;
        ...
      &lt;/project&gt;
      &lt;build&gt;
        ...
        &lt;plugins&gt;
          &lt;plugin&gt;
            &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
            &lt;artifactId&gt;maven-dependency-plugin&lt;/artifactId&gt;
            &lt;executions&gt;
              &lt;execution&gt;
                &lt;id&gt;download-jacoco-agent&lt;/id&gt;
                &lt;phase&gt;process-test-resources&lt;/phase&gt;
                &lt;goals&gt;
                  &lt;goal&gt;copy&lt;/goal&gt;
                &lt;/goals&gt;
                &lt;configuration&gt;
                  &lt;artifactItems&gt;
                    &lt;artifactItem&gt;
                      &lt;groupId&gt;org.jacoco&lt;/groupId&gt;
                      &lt;artifactId&gt;org.jacoco.agent&lt;/artifactId&gt;
                      &lt;version&gt;${jacoco.version}&lt;/version&gt;
                      &lt;classifier&gt;runtime&lt;/classifier&gt;
                      &lt;outputDirectory&gt;${project.build.directory}&lt;/outputDirectory&gt;
                      &lt;destFileName&gt;jacoco-agent.jar&lt;/destFileName&gt;
                    &lt;/artifactItem&gt;
                  &lt;/artifactItems&gt;
                &lt;/configuration&gt;
              &lt;/execution&gt;
            &lt;/executions&gt;
          &lt;/plugin&gt;
        &lt;/plugins&gt;
      &lt;/build&gt;
    &lt;/profile&gt;

**edit** 

Not sure if using the _dependency_ plugin is the right approach, or pointing to the jacoco agent artifact in the local repository:

    &lt;profile&gt;
      &lt;id&gt;CodeCoverage&lt;/id&gt;
      &lt;properties&gt;
        &lt;jacoco.agent.jar&gt;${settings.localRepository}/org/jacoco/org.jacoco.agent/${jacoco.version}/org.jacoco.agent-${jacoco.version}-runtime.jar&lt;/jacoco.agent.jar&gt;
      &lt;/properties&gt;
      ...
    &lt;/profile&gt;
   
This is simpler, and does not require copying an artifact to the local build directory, but is fragile: changes in the repository layout will break this.

[1] http://www.eclemma.org/jacoco/trunk/doc/prepare-agent-mojo.html

Cannot use jacoco JVM args and surefire JVM args together in maven

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;








Surefire Maven plugin: &quot;Corrupted STDOUT by directly writing to native stream in forked JVM&quot;

I have a multi-module maven project with both integration and unit tests in the same folder (src/test/java). Integration tests are marked with `@Category(IntegrationTest.class)`. I want to end up with the following setup:

 1. If I run `mvn install`, I want all tests to compile, but I do not want to execute any.
 2. If I run `mvn test`, I want all tests to compile, but execute only unit tests.
 3. If I run `mvn integration-test`, I want to compile and execute all tests.

**The important point is, I want this configured in the `pom.xml` without any extra commandline arguments.**

Currently I came up with the following setup in my parent pom.xml, where the only problem is #1, where all tests are executed:

    
	&lt;build&gt;
        &lt;pluginManagement&gt;
			&lt;plugins&gt;
				&lt;plugin&gt;
					&lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
                    &lt;artifactId&gt;maven-compiler-plugin&lt;/artifactId&gt;
					&lt;configuration&gt;
                        &lt;source&gt;${project.java.version}&lt;/source&gt;
                        &lt;target&gt;${project.java.version}&lt;/target&gt;
					&lt;/configuration&gt;
				&lt;/plugin&gt;
				
				&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.14.1&lt;/version&gt;
					&lt;dependencies&gt;
						&lt;dependency&gt;
							&lt;groupId&gt;org.apache.maven.surefire&lt;/groupId&gt;
							&lt;artifactId&gt;surefire-junit47&lt;/artifactId&gt;
							&lt;version&gt;2.14.1&lt;/version&gt;
						&lt;/dependency&gt;
					&lt;/dependencies&gt;
					&lt;configuration&gt;
						&lt;includes&gt;
							&lt;include&gt;**/*.class&lt;/include&gt;
						&lt;/includes&gt;
						&lt;excludedGroups&gt;cz.cuni.xrg.intlib.commons.IntegrationTest&lt;/excludedGroups&gt;
					&lt;/configuration&gt;
				&lt;/plugin&gt;

				&lt;plugin&gt;
					&lt;artifactId&gt;maven-failsafe-plugin&lt;/artifactId&gt;
					&lt;version&gt;2.14.1&lt;/version&gt;
					&lt;dependencies&gt;
						&lt;dependency&gt;
							&lt;groupId&gt;org.apache.maven.surefire&lt;/groupId&gt;
							&lt;artifactId&gt;surefire-junit47&lt;/artifactId&gt;
							&lt;version&gt;2.14.1&lt;/version&gt;
						&lt;/dependency&gt;
					&lt;/dependencies&gt;
					&lt;configuration&gt;
						&lt;groups&gt;cz.cuni.xrg.intlib.commons.IntegrationTest&lt;/groups&gt;
					&lt;/configuration&gt;
					&lt;executions&gt;
						&lt;execution&gt;
							&lt;goals&gt;
								&lt;goal&gt;integration-test&lt;/goal&gt;
								&lt;goal&gt;verify&lt;/goal&gt;
							&lt;/goals&gt;
							&lt;configuration&gt;
								&lt;includes&gt;
									&lt;include&gt;**/*.class&lt;/include&gt;
								&lt;/includes&gt;
							&lt;/configuration&gt;
						&lt;/execution&gt;
					&lt;/executions&gt;
				&lt;/plugin&gt;
			&lt;/plugins&gt;
        &lt;/pluginManagement&gt;
    &lt;/build&gt;

All child modules have the following plugin configuration in their pom.xml, which I believe should inherit from the parent pom:

    
	&lt;build&gt;	
        &lt;plugins&gt;
			&lt;plugin&gt;
				&lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
				&lt;artifactId&gt;maven-surefire-plugin&lt;/artifactId&gt;
			&lt;/plugin&gt;
			
			&lt;plugin&gt;
				&lt;artifactId&gt;maven-failsafe-plugin&lt;/artifactId&gt;
			&lt;/plugin&gt;
        &lt;/plugins&gt;
	&lt;/build&gt;

I tried using `&lt;skipTests&gt;true&lt;/skipTests&gt;`, but it disables test execution for all goals, which is not what I want (violates #2 and #3). It is also quite weird, that `mvn test` honors the `skipTests=true` option...why would I want to run it in the first place??

After hours of googling and trying different combinations, I am hesitant whether it is even possible to not run tests in `mvn install`, while at the same time run them in `mvn test`. I hope someone proves this wrong. ;)

I am also willing to accept a solution, where `mvn install` would execute only unit tests, but I don&#39;t think it makes much difference.

How can I skip tests in maven install goal, while running them in maven test goal?

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

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


All Maven Surefire-Plugin Solutions on Gang of Coders

Total of 17 Maven Surefire-Plugin Solutions