Current Behavior
The Maven build process currently generates two JAR files in the target directory during the release:
- A "standard" JAR without dependencies.
- A "shaded" (Fat) JAR containing all necessary dependencies for execution.
Both files are being uploaded to the GitHub Release, which can lead to confusion for end-users who might download the non-functional standard JAR.
Desired Improvement
We should refine the build and release process to only package and distribute the shaded JAR. This ensures that users always receive a standalone, executable artifact.
Current Behavior
The Maven build process currently generates two JAR files in the target directory during the release:
Both files are being uploaded to the GitHub Release, which can lead to confusion for end-users who might download the non-functional standard JAR.
Desired Improvement
We should refine the build and release process to only package and distribute the shaded JAR. This ensures that users always receive a standalone, executable artifact.