Description
I would like the ability for Quarkus to produce a native image source jar without also running a native-image build. The scenario in mind is the following, with two machines:
Maven builder machine with all needed dependencies, but no GraalVM/Mandrel.
Container builder machine using a Mandrel builder image, but no Maven or dependencies. It has access to the output from the first machine.
I cannot find a way to perform a Maven build with Quarkus, such that the output jar can be passed to native-image and produce a working executable. When I give native-image the standard runner jar, or uber-jar, the executable exits immediately with exit code 1.
Implementation ideas
This functionality could perhaps be added as a package type selection for the quarkus.package.type property.
Description I would like the ability for Quarkus to produce a native image source jar without also running a
native-imagebuild. The scenario in mind is the following, with two machines:I cannot find a way to perform a Maven build with Quarkus, such that the output jar can be passed to
native-imageand produce a working executable. When I givenative-imagethe standard runner jar, or uber-jar, the executable exits immediately with exit code 1.Implementation ideas This functionality could perhaps be added as a package type selection for the
quarkus.package.typeproperty.https://github.com/quarkusio/quarkus/issues/15208
$upstream:15208$