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
Description
It would be nice to restore ability to specify additional command line arguments for the native build in build.gradle file. This is most useful in the cases, when you are turning into the native mode applications, which are using libraries, for which quarkus extensions are not ready/not planned.
Starting from 1.4.0 there are only 2 ways to specify additional arguments:
using application.properties.
using command line arguments.
The option regarding application.properties, is not very desirable, because it would mean, that command line arguments needed for compilation of native application, will be present in configuration of application, which is needed only for execution of application.
The option regarding command line arguments is not portable across different environments. If before we needed to execute just one command to create native application on different environments (gradlew buildNative), now in each case we should specify additional command line arguments, and this list could be rather big (or create a wrapper for the gradle build -Dquarkus.package.type=native).
Implementation ideas
It would be nice to restore (if it is possible) ability to specify list of additional command line arguments for native build.
Something like:
Description
It would be nice to restore ability to specify additional command line arguments for the native build in build.gradle file. This is most useful in the cases, when you are turning into the native mode applications, which are using libraries, for which quarkus extensions are not ready/not planned.
Starting from 1.4.0 there are only 2 ways to specify additional arguments:
The option regarding application.properties, is not very desirable, because it would mean, that command line arguments needed for compilation of native application, will be present in configuration of application, which is needed only for execution of application.
The option regarding command line arguments is not portable across different environments. If before we needed to execute just one command to create native application on different environments (gradlew buildNative), now in each case we should specify additional command line arguments, and this list could be rather big (or create a wrapper for the gradle build -Dquarkus.package.type=native).
Implementation ideas
It would be nice to restore (if it is possible) ability to specify list of additional command line arguments for native build.
Something like:
The text was updated successfully, but these errors were encountered: