Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Node.js, PHP and APIs

bootJar cannot find the main class of a Spring Boot project

ErrorMain class name has not been configured and it could not be resolved

Short answer

The Spring Boot Gradle plugin looks in the main source set's output for a class with a public static void main method. If it finds none, or the entry point is a Kotlin file with a different generated class name, set mainClass yourself in the springBoot block.

  • Applies to Spring Boot 3.5 and 4.x Gradle plugin, Gradle 8 and 9, Java 17+
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    Confirm that the main source set really contains a class with a main method, and see which tasks the Spring Boot plugin added.

    grep -rn "static void main\|fun main" src/main
    ./gradlew tasks --all | grep -i "boot"
  2. 2Match what you see, then jump to its fix

    1. 1The build fails in bootJar or bootRun, and the grep above finds nothing under src/main.No class with a main method in the main source setFix
    2. 2A main function exists in a .kt file but the configured name does not match any class.The entry point is a Kotlin top-level functionFix

What does the error look like?

  • Main class name has not been configured and it could not be resolved

Cause 1 of 2

No class with a main method in the main source set

1Check

The plugin searches the main source set's output for one class with public static void main(String[]). A module that has none gives it nothing to find.

find src/main -name "*Application*"

2Fix

Name the class explicitly. Use the springBoot block to cover every task at once.

// build.gradle.kts
springBoot {
    mainClass.set("com.example.ExampleApplication")
}

// build.gradle (Groovy)
springBoot {
    mainClass = 'com.example.ExampleApplication'
}

3Verify

Build the executable jar.

./gradlew bootJar

Confirmed by docs.spring.io

Did this fix it?

Cause 2 of 2

The entry point is a Kotlin top-level function

1Check

Kotlin compiles a top-level main in ExampleApplication.kt into a class called ExampleApplicationKt, unless @JvmName changes it.

unzip -l build/libs/*.jar | grep -i "Application"

2Fix

Use the generated class name, with the Kt suffix, in mainClass.

springBoot {
    mainClass.set("com.example.ExampleApplicationKt")
}

3Verify

Build and start the application from the jar.

./gradlew bootJar
java -jar build/libs/my-app-0.0.1-SNAPSHOT.jar

Confirmed by docs.spring.io

Did this fix it?

How do I stop it coming back?

  • Keep one class with the main method per runnable module, and set mainClass when a module has two.
  • Check what a module is meant to be: a library module does not need an executable jar.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.

Which stack is behind this page?

Projects of mine built on the same technologies:

Related fixes

Back end

Spring Boot will not start because port 8080 is already taken

Action: Identify and stop the process that's listening on port 8080 or configure this application to listen on another port.

Spring Boot listens on 8080 unless told otherwise, and only one process can own a port.

3 causes, each with a fix

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.