Hi, camel-k-runtime project was created to have several camel components (and the related quarkus extensions) suitable for Camel K, however all camel components are already into camel, and only the quarkus extensions are in camel-k-runtime.
Today we have to manage camel-k-runtime releases and align versions to camel and camel-quarkus. Also from a Camel K perspective we currently depend on camel-k-runtime and when we need a new fix provided by either camel-quarkus or camel, we should have those versions aligned in camel-k-runtime first. It seems appropriate to think about merging camel-k-runtime remaining quarkus extensions into camel-quarkus. Having Camel K to depend only on camel-quarkus would improve our development cadence and quicker releases. And this is what I would like to propose and receive feedback. I see the current quarkus extensions in camel-k-runtime must be tailored to follow camel-quarkus way and I will create a camel epic task to outline the main points. All of this should be in a specific branch for later review. So I would appreciate your feedback on this. Thanks -- Claudio Miranda clau...@claudius.com.br http://www.claudius.com.br
