Skip to content

Refactor release workflow and packaging configuration#2

Merged
diegosilval merged 1 commit intomasterfrom
develop
Feb 2, 2026
Merged

Refactor release workflow and packaging configuration#2
diegosilval merged 1 commit intomasterfrom
develop

Conversation

@diegosilval
Copy link
Contributor

  • Remove application-nomad.properties as it's no longer used.
  • Update Maven pom.xml to set finalName for consistent artifact naming.
  • Enhance release pipeline to:
    • Set permissions for upload actions.
    • Refactor Maven build command to explicitly define uber-jar packaging.
    • Automatically upload the built artifact (java-nomad-example-runner.jar) as a release asset.

- Remove `application-nomad.properties` as it's no longer used.
- Update Maven `pom.xml` to set `finalName` for consistent artifact naming.
- Enhance release pipeline to:
  - Set permissions for upload actions.
  - Refactor Maven build command to explicitly define `uber-jar` packaging.
  - Automatically upload the built artifact (`java-nomad-example-runner.jar`) as a release asset.
@diegosilval diegosilval merged commit a4b42a6 into master Feb 2, 2026
2 checks passed
@github-actions
Copy link

github-actions bot commented Feb 2, 2026

Qodana for JVM

It seems all right 👌

No new problems were found according to the checks applied

View the detailed Qodana report

To be able to view the detailed Qodana report, you can either:

To get *.log files or any other Qodana artifacts, run the action with upload-result option set to true,
so that the action will upload the files as the job artifacts:

      - name: 'Qodana Scan'
        uses: JetBrains/qodana-action@v2025.3.1
        with:
          upload-result: true
Contact Qodana team

Contact us at qodana-support@jetbrains.com

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant