Скачать или смотреть How to Create a Separate Spring Boot JAR and Plain JAR with Specific Classes Using Maven

Learn how to generate a separate `Spring Boot` JAR and a plain JAR containing specific classes using `Maven` to keep your project organized.
---
This video is based on the question https://stackoverflow.com/q/77190368/ asked by the user 'red123' ( https://stackoverflow.com/u/22646936/ ) and on the answer https://stackoverflow.com/a/77192408/ provided by the user 'Andrey B. Panfilov' ( https://stackoverflow.com/u/3426309/ ) 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 create Spring Boot jar and plain jar with specific classes

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.
---
Streamline Your Java Project with Maven: Creating Separate JAR Files

When working with Java projects, particularly with Spring Boot applications, managing your JAR files efficiently can be a challenge. A common dilemma is wanting to share certain classes in different projects without separating them into different modules—while also ensuring that the non-essential classes and resources remain in the executable JAR. This post delves into this problem and offers a clear solution to help you achieve just that.

The Challenge: Two JAR Files with Different Contents

You may have an application that generates two JAR files:

Executable Spring Boot JAR: This JAR contains everything needed to run your Spring Boot application, including dependencies and resources like properties files.

Normal JAR: This JAR should only contain specific classes that you want to share with other projects, without including unnecessary files like the main class or configuration resources.

Currently, your normal JAR may inadvertently include everything from your project, which complicates sharing specific components across other projects. The challenge lies in how to create a normal JAR that only contains selected classes while maintaining the integrity of the executable JAR.

The Solution: Maven Configurations

By making use of Maven's capabilities, particularly two plugins—the spring-boot-maven-plugin and the maven-jar-plugin—you can achieve your goal with a well-structured configuration.

Step 1: Configure the maven-jar-plugin

To generate a normal JAR containing only specific classes, you need to set up the maven-jar-plugin. Here’s how you can do it:

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

Step 2: Understand the Plugin Breakdown

Group and Artifact ID: The plugin you are using is defined with its group and artifact ID.

Execution Block: This block allows you to define how and when the plugin executes. By specifying <id>thin</id>, you can refer to this execution later.

Goals: Specifying <goal>jar</goal> indicates you want to create a JAR file.

Configuration Settings:

Classifier: The thin classifier denotes that this JAR is different from the standard one.

Includes: By listing <include>org/example/stuff/**</include>, you effectively narrow down the contents of this JAR to just the classes within the specified package.

Step 3: Ensure Your Executable JAR Remains Untouched

When you configure the maven-jar-plugin as shown, remember that the spring-boot-maven-plugin handles the executable JAR creation. This means modifications to the maven-jar-plugin will not directly affect how the Spring Boot application within your project is packaged as a runnable JAR.

Conclusion

By utilizing Maven effectively with the above configurations, you can neatly generate both a thin JAR containing only specific classes and the fully operational Spring Boot JAR. This solution paves the way for easier sharing of components across different projects without unnecessary clutter.

Now, you can keep your projects organized while ensuring that they remain efficient and manageable. Coding just got a little easier!