You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would you be open to publishing a shaded jar for the transformer CLI? (org.eclipse.transformer.cli-<version>-shaded.jar)
The current workflow with the distribution jar is to download it (org.eclipse.transformer.cli-<version>-distribution.jar), extract it, then run the CLI that is part of it (org.eclipse.transformer.cli-<version>.jar).
A shaded jar would save a step because it could be downloaded and run directly without the need to extract, since all the required dependencies would be part of the jar itself.
The text was updated successfully, but these errors were encountered:
This seems a bit niche. If we really want to make it easier to install/use the CLI, perhaps something else like a brew formula or sdkman support would be in order?
Thanks for the response. Yeah it's a bit niche. My use case may be unusual as well. I'm running the CLI in an intermediate docker image build before including the OS (which uses microdnf and not homebrew/sdkman), and I'd like to avoid putting a new package/sdk in the final image.
Would you be open to publishing a shaded jar for the transformer CLI? (
org.eclipse.transformer.cli-<version>-shaded.jar
)The current workflow with the distribution jar is to download it (
org.eclipse.transformer.cli-<version>-distribution.jar
), extract it, then run the CLI that is part of it (org.eclipse.transformer.cli-<version>.jar
).A shaded jar would save a step because it could be downloaded and run directly without the need to extract, since all the required dependencies would be part of the jar itself.
The text was updated successfully, but these errors were encountered: