Hello,

>From https://camel.apache.org/camel-k/2.0.x/architecture/cr/camel-catalog.html
I understood that the Camel K Operator uses the CamelCatalog to
determine the dependencies of the Camel route. Then the Camel K
Operator uses these dependencies in a Maven build to assembly the
transitive dependencies of the camel route. I want to leverage this
process also for my Custom Camel Quarkus components, dataformats, so
that I do not have to specify the custom dependencies during the
deployment of the Camel route in the command line with the "-d"
option. Is this possible?

Can I enhance the CamelCatalog with custom Camel components, dataformats?

Regards Franz

Reply via email to