Maven is a powerful build automation tool that also handles project management. The Spring Boot repackage is a plugin provided by Maven. This article explains the spring-boot:repackage goal and the Maven package phase. For this, you should have a good understanding of the Spring Framework and Maven build tool. In this article, we will learn spring-boot:repackage vs Maven package.

spring-boot:repackage

The spring-boot:repackage goal is provided by the Spring Boot Maven Plugin. This goal is specifically designed to support the creation of executable JAR or WAR files for Spring Boot applications. An executable JAR or WAR file created by spring-boot:repackage includes not only the compiled application code but also all the dependencies required to run the application.

Example:

<build>
    <plugins>
        <plugin>
            <groupId>org.springframework.boot</groupId>
            <artifactId>spring-boot-maven-plugin</artifactId>
        </plugin>
    </plugins>
</build>

Maven Package

The Maven package phase is part of the standard Maven build lifecycle. During this phase, Maven compiles the project’s source code, processes the resources, and packages the compiled code and resources into a distributable format, such as a JAR or WAR file. This packaged artifact is typically placed in the target directory of the project.

Example:

<build>
    <plugins>
        <!-- Other plugins may be configured here -->
    </plugins>
</build>

Prerequisites:

• Maven Installation
• JDK Installation
• Maven Project Structure
• pom.xml Configuration
• Spring Boot Dependencies
• Build Plugins
• Internet Access
• Project Compilation

Difference Between spring-boot:repackage and Maven package

Below is the difference table of spring-boot:repackage and Maven package.