[GitHub] [camel-k] tadayosi commented on pull request #4402: fix(#4361): Avoid errors when components not available in Camel catalog

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

tadayosi commented on PR #4402:
URL: https://github.com/apache/camel-k/pull/4402#issuecomment-1560429923

   > I noticed this in the newly created E2E tests where camel:resilience4j is not available as Camel Quarkus extension but got resolved to camel-quarkus-resilience4j which is simply not available. This was causing the integration to fail at build time with Maven dependency resolving errors. I have fixed that so now Camel dependencies get resolved to camel-xxx instead when there are no Camel Quarkus extensions for this specific dependency available.
   
   What does it mean to use a `camel-xxx` dependecy on a Quarkus runtime, since in Camel K 1.12.x Quarkus is still the default and only runtime?  Doesn't trying to use `camel-resilience4j` directly mean running a library not yet ready for Quarkus, as the raw Camel dependency shouldn't yet go through stripping of possible runtime usages of reflection or dynamic loading which aren't allowed on Quarkus?


-- 
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