-
In a new Gradle Quarkus project using 3.10.1, I am unable to produce a native executable:
This also happens when using Interestingly, the native executable is built perfectly when running Any ideas what could be wrong here? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
The short answer is, if you're building for native, set The long answer is that the Gradle tooling (specifically) doesn't support multiple outputs very well and in fact the integration isn't as good as I'd like. I'd like to discuss a plan to improve matters but it doesn't look to be very simple, so for now I think the workaround is what we have. |
Beta Was this translation helpful? Give feedback.
The short answer is, if you're building for native, set
quarkus.package.jar.enabled=false
and that should get you past the error. N.b.quarkus.jar.enabled
is not the correct config key.The long answer is that the Gradle tooling (specifically) doesn't support multiple outputs very well and in fact the integration isn't as good as I'd like. I'd like to discuss a plan to improve matters but it doesn't look to be very simple, so for now I think the workaround is what we have.