[fix] Publish executable jar as github release

[unidevel]

Tested with https://github.com/unix280/presto-release-tools/actions/runs/23662465220/job/68935989447

Published execuable jars like https://github.com/unix280/presto-release-tools/releases

[sourcery-ai]

Reviewer's Guide

This PR moves the executable JAR build logic into a dedicated Maven profile and updates the GitHub Actions release workflow to build with that profile and upload the generated executable JARs (and tarballs) as release assets for the tagged version.

Flow diagram for Maven executable-jar profile build

flowchart TD
    A[Invoke Maven: mvn clean package -Pexecutable-jar -DskipTests] --> B[Activate profile executable-jar]
    B --> C[maven-shade-plugin execution in package phase]
    C --> D[Create shaded JAR]
    D --> E[Attach shaded artifact with classifier executable]

    B --> F[really-executable-jar-maven-plugin execution in package phase]
    F --> G[Wrap shaded JAR as really executable JAR with -Xmx1G]

    E --> H[Artifacts in presto-release-tools/target/]
    G --> H

Loading

File-Level Changes

Change	Details	Files
Isolate executable JAR packaging into an opt‑in Maven profile.	Remove always-on maven-shade-plugin and really-executable-jar-maven-plugin configurations from the main build plugins section. Introduce a new Maven profile named 'executable-jar' that redefines the shade and really-executable-jar plugin executions bound to the package phase. Ensure the shaded JAR is attached with the 'executable' classifier and Main-Class taken from the existing ${main-class} property.	presto-release-tools/pom.xml
Extend the release GitHub Actions workflow to build and publish executable artifacts for the release tag.	Add a step to check out the release tag (RELEASE_VERSION) and run 'mvn clean package -Pexecutable-jar -DskipTests' to produce executable JARs. Add a step using softprops/action-gh-release@v2 to upload executable JARs and tar.gz artifacts from the presto-release-tools target directory to the GitHub Release corresponding to the tag. Configure the release upload step to fail if the expected artifact files are not found, and to authenticate using the provided GITHUB_TOKEN secret.	.github/workflows/release.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've found 1 issue, and left some high level feedback:

• Moving the shade/really-executable plugins into the executable-jar profile means the default build no longer produces the executable JAR; if any existing automation or consumers rely on that default behavior, consider either keeping the plugins active by default or documenting/renaming the profile to make the change in behavior explicit.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Moving the shade/really-executable plugins into the `executable-jar` profile means the default build no longer produces the executable JAR; if any existing automation or consumers rely on that default behavior, consider either keeping the plugins active by default or documenting/renaming the profile to make the change in behavior explicit.

## Individual Comments

### Comment 1
<location path=".github/workflows/release.yml" line_range="90-93" />
<code_context>
           git log --pretty="format:%ce: %s" -5
           git push origin master --tags
+
+      - name: Build executable jars
+        run: |
+          git checkout ${{ env.RELEASE_VERSION }}
+          mvn clean package -Pexecutable-jar -DskipTests
+
+      - name: Publish executable jars to GitHub Release
</code_context>
<issue_to_address>
**suggestion (performance):** Limit the Maven build to the `presto-release-tools` module to avoid unnecessary work.

Since only `presto-release-tools/target/...` artifacts are used later, you can restrict the build to that module by either:

- Adding `-pl presto-release-tools -am` to the Maven command, or
- Setting `working-directory: presto-release-tools` and running `mvn clean package -Pexecutable-jar -DskipTests` there.

This keeps the build focused and faster.

```suggestion
      - name: Build executable jars
        run: |
          git checkout ${{ env.RELEASE_VERSION }}
          mvn clean package -pl presto-release-tools -am -Pexecutable-jar -DskipTests
```
</issue_to_address>

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[yhwang]

/LGTM

[tdcmeehan]

Thanks a lot @unidevel!