[GitHub] [camel-k] squakez commented on issue #4124: How to use JVM classpaths in Native mode?

["squakez (via GitHub)" <gi...@apache.org>]

squakez commented on issue #4124:
URL: https://github.com/apache/camel-k/issues/4124#issuecomment-1465719356

   Yeah, your impressions are correct although not directly related to the usage of Java reflection. The problem here is that the jar you're providing is only used at runtime, so it works fine when using JVM mode. When you want to go Quarkus native, you need to pass that jar to the build so that it can be considered by the ahead of time compilation (you may have additional problems because reflection, but that would be a different problem). The only kind of workaround you can try to adopt at this stage is to try embedding all your dependency source into the same Java class you're using for your Integration (it may be difficult if it's a lot of code, I know). I think this kind of problem may be mitigated if change the design to [make a Camel K build a generic phase](https://github.com/apache/camel-k/issues/4024).
   
   Marking this as a feature.


-- 
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-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org