[REQ] Publish openapi-generator-cli JAR to GitHub Release Assets

[ogaclejapan]

Is your feature request related to a problem? Please describe.

https://github.com/aquaproj/aqua, a declarative CLI version manager, recently added support for executing JAR-based tools (aquaproj/aqua#4625). To use openapi-generator-cli via aqua, the JAR needs to be available as a GitHub Release asset, which it currently is not.

Describe the solution you'd like

Upload openapi-generator-cli.jar as an asset to each GitHub Release tag going forward.

This would allow tools like https://github.com/aquaproj/aqua and other GitHub-Releases-based version managers to install and manage the CLI directly. With the JAR available as a release asset, users could manage openapi-generator-cli versions per project via a simple configuration file, improving reproducibility across teams and CI environments.

Describe alternatives you've considered

• Docker image (https://hub.docker.com/r/openapitools/openapi-generator): Available, but Docker Desktop requires a paid subscription for commercial use, which may not be acceptable in all organizations.
• Homebrew (https://github.com/Homebrew/homebrew-core/blob/main/Formula/o/openapi-generator.rb): Available, but Homebrew is not a first-class per-project pinning workflow, making it difficult to enforce a consistent version across team members.
• Manual download from Maven Central: The JAR is published to Maven Central as part of the existing release workflow, but tools like aqua currently rely on GitHub Release assets for automatic version resolution.

Additional context

For reference, https://github.com/aquaproj/aqua-registry/blob/main/pkgs/facebook/ktfmt/registry.yaml is an example of a JAR-based tool already registered in the aqua registry, demonstrating that this pattern is established and working.

[sakshar2303]

Hi, I'd like to work on this — could it be assigned to me?

This is a well-scoped CI/release pipeline change. The JAR is already being published to Maven Central as part of the existing release workflow, so this is essentially about adding one extra upload step to attach openapi-generator-cli.jar as a GitHub Release asset during the same pipeline run.

My plan:

1. Locate the existing release workflow (likely in .github/workflows/)
2. Add a step to upload openapi-generator-cli-{version}.jar as a release asset after the Maven publish step
3. Verify the asset appears correctly on a test tag
4. Once merged, the aqua registry can be updated to register openapi-generator-cli using the same pattern as ktfmt

Happy to get this done!

[wing328]

Welcome PRs from the community for this enhancement

Here is the maven release workflow: https://github.com/OpenAPITools/openapi-generator/blob/master/.github/workflows/maven-release.yml

[sakshar2303]

Hi! I've submitted a PR #23524 that implements this enhancement.

Here's what the PR does:

• Adds a tags: 'v*' trigger to the existing Maven release workflow so it
  also fires on version tag pushes
• Adds a new upload-release-asset job that builds openapi-generator-cli.jar
  and uploads it as openapi-generator-cli-{version}.jar to the corresponding
  GitHub Release asset — right after the Maven Central publish step succeeds
• No changes to any existing jobs or build logic, purely an additive CI change

Once merged, the aqua registry can be updated to register openapi-generator-cli
following the same pattern already used by ktfmt.

Happy to make any changes based on feedback!

[wing328]

@ogaclejapan i just manually uploaded the CLI JAR to https://github.com/OpenAPITools/openapi-generator/releases/tag/v7.21.0. can you please test to see if that works with aqua ?

if that works, then i think the workflow update done by @sakshar2303 PR should also work.

[ogaclejapan]

@wing328 @sakshar2303 Awesome, thanks 🙌
Everything worked as expected! I'll also open a PR to aqua-registry to add it as a standard package.

I've confirmed this works with aqua using the following minimal local registry setup:

# aqua-registry.yaml
packages:
  - name: OpenAPITools/openapi-generator-cli
    type: github_release
    repo_owner: OpenAPITools
    repo_name: openapi-generator
    asset: openapi-generator-cli-{{trimV .Version}}.jar
    format: raw
    complete_windows_ext: false
    files:
      - name: openapi-generator-cli
        src: openapi-generator-cli-{{trimV .Version}}.jar

# aqua.yaml
registries:
  - name: local
    type: local
    path: aqua-registry.yaml
packages:
  - name: OpenAPITools/openapi-generator-cli@v7.21.0
    registry: local

# aqua policy allow is required once to approve the local registry.
$ aqua policy allow
$ aqua install
$ openapi-generator-cli version
7.21.0

With aqua's bin directory in PATH (https://aquaproj.github.io/docs/install), openapi-generator-cli is available directly.