ppalaga commented on issue #5006: URL: https://github.com/apache/camel-quarkus/issues/5006#issuecomment-1619059577
> > @zakkak, I see that `quarkus.native.additional-build-args` is somehow not powerful enough to override the value present in gax-grpc jar. But it is still not clear to me why? Could you perhaps shed some light on that? > > If you run `native-image` with `--verbose` you can see the options that end up being passed to the native image builder after combining options given by the user, the libraries, and the application. These options are passed in the following order: > > 1. Options automatically passed by Quarkus > 2. User options passed through `quarkus.native.additional-build-args` (these can override the ones in 1) > 3. Options automatically passed by Quarkus that we don't want to allow the users to override (see https://github.com/quarkusio/quarkus/blob/5382a3de02facc6f1be2f55d8fdb7d5c1fce8dc2/core/deployment/src/main/java/io/quarkus/deployment/pkg/steps/NativeImageBuildStep.java#L795-L799) > 4. Options passed through native-image.properties of dependencies > 5. Options passed through native-image.properties of the application > > with each category being able to override the previous categories. So, since `quarkus.native.additional-build-args` are applied before the `native-image.properties` there is no way for them to override the values passed through native-image.properties. AFAIK there is no way to make command line options to apply after options defined in native-image.properties. Thanks a lot for the informative answer, @zakkak! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
