Скачать или смотреть How to Pack an Executable JAR in ZIP Format Using Maven Assembly Plugin

Discover how to resolve the issue with Maven Assembly Plugin that packs the `.jar.original` file instead of the `executable jar` by adjusting the order in your POM file.
---
This video is based on the question https://stackoverflow.com/q/68858209/ asked by the user 'Divya Kampasi' ( https://stackoverflow.com/u/9451118/ ) and on the answer https://stackoverflow.com/a/68859626/ provided by the user 'slauth' ( https://stackoverflow.com/u/6756090/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Maven assembly plugin zips the jar.original content and not the executable jar

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Introduction

When working with Maven in a Spring Boot project, it’s common to use the maven-assembly-plugin for packaging your applications into ZIP files. A common problem many developers face is the plugin packing the .jar.original file instead of the desired executable JAR. This can lead to confusion and extra work. In this guide, we will address this issue and guide you through a simple solution to ensure the correct JAR file is included in your ZIP package.

The Problem

The core issue arises when the maven-assembly-plugin is configured to create a ZIP file that should contain the executable JAR. However, it mistakenly includes the original JAR file (.jar.original). This usually happens due to the execution order of the Maven plugins specified in the pom.xml file. Specifically, the spring-boot-maven-plugin generates the executable JAR, but it is executed after the maven-assembly-plugin, which leads to an empty or incorrect output.

The Solution

To ensure the proper creation of the executable JAR and its inclusion in the ZIP file, you must adjust the order of the plugin definitions in your pom.xml. Here’s how to do it:

Step-by-Step Instructions

1. Find Your pom.xml File

Locate your project’s pom.xml file, which is typically found in the root directory of your Maven project.

2. Identify Plugin Definitions

In your pom.xml, look for the <build> section where plugins are defined. You will see the maven-assembly-plugin and the spring-boot-maven-plugin listed.

3. Change the Order of Plugins

The solution is simple: ensure the spring-boot-maven-plugin is defined before the maven-assembly-plugin. Here’s an excerpt of what your plugins section should look like:

[[See Video to Reveal this Text or Code Snippet]]

4. Save Changes and Rebuild

After changing the order, save your pom.xml, and then run your Maven build again. This time, the maven-assembly-plugin will find the executable JAR created by spring-boot-maven-plugin and package the correct file in the ZIP.

Conclusion

By simply rearranging the plugin order in your pom.xml file, you can resolve the issue of the maven-assembly-plugin packaging the .jar.original file instead of the executable JAR. This adjustment not only simplifies your build process but also ensures that you get the correct artifacts packaged for deployment. Enjoy seamless packaging with Maven!

Now you're equipped with the knowledge to tackle this common Maven challenge. Happy coding!