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

Question

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:

Error: Could not find or load main class org.apache.maven.surefire.booter.ForkedBooter

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:

<parent>
    <groupId>org.springframework.boot</groupId>
    <artifactId>spring-boot-starter-parent</artifactId>
    <version>2.0.2.RELEASE</version>
    <relativePath/>
</parent>
...
<dependency>
        <groupId>org.springframework.boot</groupId>
        <artifactId>spring-boot-starter-test</artifactId>
        <scope>test</scope>
</dependency>
...
<dependency>
        <groupId>org.springframework.boot</groupId>
        <artifactId>spring-boot-starter-web</artifactId>
</dependency>
...
<build>
    <plugins>
        <plugin>
            <groupId>org.springframework.boot</groupId>
            <artifactId>spring-boot-maven-plugin</artifactId>
        </plugin>
    </plugins>
</build>

The upstream issue shows three workarounds (the two listed here, plus forkCount 0), but none are without problems ☹ — mirabilos
– mirabilos, Commented Oct 31, 2018 at 14:44

jediz · Accepted Answer · 2018-06-02 22:21:14Z

132

Workaround for the issue was to override Spring Boot's maven-surefire-plugin definition and set useSystemClassLoader to false. Read Surefire docs for more details

<build>
    <plugins>
        ...
        <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-surefire-plugin</artifactId>
            <configuration>
                <useSystemClassLoader>false</useSystemClassLoader>
            </configuration>
        </plugin>
    </plugins>
</build>

answered Jun 2, 2018 at 22:21

jediz

4,7175 gold badges42 silver badges42 bronze badges

Sign up to request clarification or add additional context in comments.

6 Comments

agassner Over a year ago

Yes, I can confirm the solutions fixes the problem, but what is the issue behind the scenes? - The nightly builds on our CI system were suddenly red without any code changes. Is it an issue with Spring Boot?

Ordiel Over a year ago

@agassner take a look at this, I arrived here by this post

mirabilos Over a year ago

As said in the other answer and the upstream issue this workaround is not without problems.

Mark Over a year ago

This fix worked for me, however, I got a warning that a version should be supplied/indicated. To avoid future errors I'd recommend adding one. As of now, <version>2.22.1</version> seems to be the latest.

Kaspatoo Over a year ago

one should set the version not to get maven warnings on build. edit: as still said in previuous comment

|

Andreas Presthammer · Accepted Answer · 2018-10-31 12:52:16Z

22

The <useSystemClassLoader>false</useSystemClassLoader> solution provideded by jediz did allow my surefire tests to run, but broke class loading in some of my Spring Boot integration tests.

The following maven-surefire-plugin configuration worked for me:

<plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-surefire-plugin</artifactId>
    <configuration>
        <argLine>-Djdk.net.URLClassPath.disableClassPathURLCheck=true</argLine>
    </configuration>
</plugin>

answered Oct 31, 2018 at 12:52

Andreas Presthammer

1,9932 gold badges19 silver badges31 bronze badges

2 Comments

mirabilos Over a year ago

As said in the upstream issue this workaround is also not without problems ☹

Wedson Quintanilha da Silva Over a year ago

This simple option solved my problem that occurred in both 1.8 and 11. Tks!

Raedwald · Accepted Answer · 2020-07-27 11:20:00Z

16

This is due to a known bug in the Maven Surefire plugin. It was fixed in version 3.0.0-M1, which was released in November 2018. So the simplest and most reliable fix is to upgrade which version of the plugin you use.

Updating the maven-surefire-plugin from 2.12.4 to 3.0.0-M1 worked for me. The project did not explicitly use the plugin, so I had to add a new plugin dependency.

<plugins>
   ...
   <plugin>
      <artifactId>maven-surefire-plugin</artifactId>
      <version>3.0.0-M1</version>
   </plugin>
   ...
</plugins>

edited Jul 27, 2020 at 11:20

Raedwald

49.2k49 gold badges162 silver badges250 bronze badges

answered Nov 12, 2018 at 11:42

rvange

2,6222 gold badges21 silver badges23 bronze badges

Comments

peterh · Accepted Answer · 2020-02-19 11:50:48Z

To me, the solution was to run mvn as

_JAVA_OPTIONS=-Djdk.net.URLClassPath.disableClassPathURLCheck=true mvn clean compile package

Other ideas (giving the system property to the maven argument list, different changes in pom.xml, settings.xml) did not work.

Despite that it didn't contain the exact solution, also this answer was very helpful for me to make it clear, that it is an unfortunate cooperation of two independent, alone harmless bugs in the Ubuntu JDK and the Maven Surefire Plugin.

Recent Debian (buster) with the same JDK and Maven versions doesn't seem affected by the problem, but Ubuntu (xenial) did.

The exact solution is coming from this answer.

_{Update from the future: with Debian Buster is alles okay and this workaround is not needed any more.}

GlenPeterson · Accepted Answer · 2020-02-19 20:02:22Z

1

I was able to remove the maven-surefire-plugin from my POM after adding this to the top of my POM (inside the <project> node)

<prerequisites>
    <maven>3.6.3</maven>
</prerequisites>

Why do I think this is the right answer?

It specifies the version of Maven that Maven recommends using: https://maven.apache.org/download.cgi
when you run mvn versions:display-plugin-updates it shows that it's taking the maven-surefire-plugin 3.0.0-M3 from super-pom, which so far seems to have this issue fixed.
You don't have to manage individual plugin versions independently going forward. Just your minimum maven version which controls the super-pom version.

edited Feb 19, 2020 at 20:02

answered Jan 30, 2019 at 18:39

GlenPeterson

5,2965 gold badges47 silver badges55 bronze badges

3 Comments

Raymund Arthur Over a year ago

I tried this solution and here's what I got:

[WARNING] The project com.example:pom:0.0.2 uses prerequisites which is only intended for maven-plugin projects but not for non maven-plugin projects. For such purposes you should use the maven-enforcer-plugin. See https://maven.apache.org/enforcer/enforcer-rules/requireMavenVersion.html

Raymund Arthur Over a year ago

i tested it with maven 3.6.0, OpenJDK11, and Spring boot 2.1.X parent. I managed to solve the issue by using rvange's answer above.

GlenPeterson Over a year ago

I'm sorry that my answer didn't work for you, but glad that you found one that did! My answer is still working well for me though, on several projects, so I'm going to leave it there.

the Tin Man · Accepted Answer · 2020-03-23 21:58:13Z

1

Adding this to the maven-surefire-plugin I resolved the problem:

<plugin>    
  <groupId>org.apache.maven.plugins</groupId>   
  <artifactId>maven-surefire-plugin</artifactId>    
  <configuration>
    <forkCount>0</forkCount>
  </configuration>
</plugin>

edited Mar 23, 2020 at 21:58

the Tin Man

161k44 gold badges222 silver badges308 bronze badges

answered Mar 23, 2020 at 20:25

Ruben Romero

311 bronze badge

2 Comments

the Tin Man Over a year ago

Welcome to SO! When answering, please do more than toss out code. Instead, explain why the code should be the selected solution. The goal is to educate, to teach the OP how to fish, not just solve this current problem with a single fish.

Matthew Read Over a year ago

I've only seen the need for this when running an older version of the plugin under a newer version of Java, like 11. Try the latest version of the plugin instead.

Andrzej Szeląg · Accepted Answer · 2025-01-26 16:39:43Z

0

In my case, such a warning appeared:

[WARNING] useSystemClassLoader setting has no effect when not forking [WARNING] The parameter forkCount should likely not be 0. Forking a JVM for tests improves test accuracy. Ensure to have a >= 1.

It's OK:

            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-surefire-plugin</artifactId>
                <configuration>
                    <forkCount>1</forkCount>
                </configuration>
            </plugin>

edited Jan 26 at 16:39

answered Jan 26 at 16:28

Andrzej Szeląg

11 bronze badge

1 Comment

Jeremy Caney Jan 28 at 2:28

Thank you for contributing to the Stack Overflow community. This may be a correct answer, but it’d be really useful to provide additional explanation of your configuration so developers can understand your reasoning. This is especially useful for new developers who aren’t as familiar with the syntax or struggling to understand the concepts. Would you kindly edit your answer to include additional details for the benefit of the community?

Collectives™ on Stack Overflow

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

7 Answers 7

6 Comments

2 Comments

Comments

Comments

3 Comments

2 Comments

1 Comment

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

7 Answers 7

6 Comments

2 Comments

Comments

Comments

3 Comments

2 Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest

Linked

Related