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
currently the runner gets named something like: quarkus-cli-999-SNAPSHOT-runner.jar i.e. project-version-runner.jar
For the .jar that is fine, but for the native executable its unfortunate - especially on windows and mac since if I do:
mvn package -Pnative I get a OSX executable named quarkus-cli-999-SNAPSHOT-runner but I get the a ELF/linux binary when doing mvn package -Dquarkus.native.container-build=true also with same name.
we should use the format project-version-platform-runner.jar so it would something like quarkus-cli-999-SNAPSHOT-darwin-runner for osx and quarkus-cli-999-SNAPSHOT-win64-runner.exe for windows and similar for linux.
Then it is explicit and when you do multiple builds in i.e. github action or on win/osx you end up with actual separate binaries per platform rather than overwriting.
note: just using darwin and win64 as examples - there is a convention I just don't recall it by heart :)
The text was updated successfully, but these errors were encountered:
currently the runner gets named something like:
quarkus-cli-999-SNAPSHOT-runner.jar
i.e.project-version-runner.jar
For the .jar that is fine, but for the native executable its unfortunate - especially on windows and mac since if I do:
mvn package -Pnative
I get a OSX executable namedquarkus-cli-999-SNAPSHOT-runner
but I get the a ELF/linux binary when doingmvn package -Dquarkus.native.container-build=true
also with same name.we should use the format
project-version-platform-runner.jar
so it would something likequarkus-cli-999-SNAPSHOT-darwin-runner
for osx andquarkus-cli-999-SNAPSHOT-win64-runner.exe
for windows and similar for linux.Then it is explicit and when you do multiple builds in i.e. github action or on win/osx you end up with actual separate binaries per platform rather than overwriting.
note: just using darwin and win64 as examples - there is a convention I just don't recall it by heart :)
The text was updated successfully, but these errors were encountered: