-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support fast-jar packaging for quarkus #360
Comments
I can try to take a look at this one. Do we think there is anything required on the The operator can set a maven property for |
The issue I see is that - if I'm not mistaking - the fast-jar packaging assumes the dependencies are in a specific location relative to the bootstrap jar but that does not hold true for camel-k as we don't deploy quarkus based application using the layout the plugin generates but we assemble the classpath. I don't know if the location of the jars can be configured or if we need a specific BuildItem to control the fast-jar set-up so we may need to do something here. |
Right - that makes sense, thanks for clarifying. I'll have a look. |
I will probably have to revert the change I made to support fast-jar. There's a problem with loading Kotlin integrations. The Kotlin bootstrap tries to do
|
@jamesnetherton maybe we can improve the catalog to be able to set specific property per artefact |
For reference the bug is fixed in Quarkus 1.12.x quarkusio/quarkus#14583. |
Also for reference, in Quarkus 1.12, seems |
This has been implemented here and in the camel-k project. |
https://quarkus.io/blog/quarkus-1-5-final-released/#fast-jar-packaging-format
The text was updated successfully, but these errors were encountered: