Skip to content

Conversation

@martint
Copy link
Member

@martint martint commented Aug 23, 2025

Going forward, binary artifacts will be available under GitHub releases

Release notes

(x) This is not user-visible or is docs only, and no release notes are required.

'jdbc': ('trino-jdbc', 'jar', None),
'server': ('trino-server', 'tar.gz'),
'server-core': ('trino-server-core', 'tar.gz'),
'cli': ('trino-cli', None),
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, it can be anything we want. We’ll publish those artifacts to github, so we’ll change the name. No need for the “-executable” qualifier

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok .. so the filename will be just trino-cli-476.jar ? If so I have to adjust my PR for the website .. which is fine by my .. just might be confusing for readers of the book or older docs for what they are used to. Just let me know so I can adjust the other PR

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, it will be just “trino-cli-476”. It’s just a binary executable

Copy link
Member

@mosabua mosabua Aug 31, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Uff .. I think thats actually a bad idea. It is not a pure executable .. it still requires a JVM on the path .. and with the .jar extension it can be recognized and run .. without the extension that is harder to figure out and might not work so well.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Kind of feels like a unrelated change that we should not pull in unless we have to.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wdyt @wendigo @electrum ? I know the file works with the name without extension if Java is on the path, but if not it might be a bad experience. Have any of you played with that in the past?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The extension doesn’t actually do anything. The file behaves like a script with a shebang line.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It helps if you are running on Windows (I'm not sure whether we support it or not). We could add a check in the cli itself, to check for required flags if it's run via java -jar).

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess either way should be fine. The instructions in the docs already talk about renaming it so it doesnt matter I guess - see https://trino.io/docs/current/client/cli.html

We just have to adjust the example for Windows in that same doc since it uses the old -executable.jar

@mosabua
Copy link
Member

mosabua commented Aug 30, 2025

Please confirm about expected filenames and then also review and comment in trinodb/trino.io#811 since that assumes identical filenames to what we had in Central

Copy link
Member

@mosabua mosabua left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am good with either approach for the CLI filename .. the rest if fine anyway.. so I am approving.

Going forward, binary artifacts will be available under GitHub releases
@martint martint merged commit 1986bff into trinodb:master Sep 24, 2025
9 checks passed
@github-actions github-actions bot added this to the 477 milestone Sep 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

3 participants