Hi everyone, I wanted to open a discussion about the camel-k extension module and Maven plugins that live in the Camel Quarkus project:
https://github.com/apache/camel-quarkus/tree/main/extensions/camel-k https://github.com/apache/camel-quarkus/tree/main/tooling/camel-k-catalog-model https://github.com/apache/camel-quarkus/tree/main/tooling/camel-k-maven-plugin There was a plan to move the majority of the camel-k-runtime project into either Camel or Camel Quarkus. https://github.com/apache/camel-quarkus/issues/4283 We've had the camel-k extension in Camel Quarkus for almost 12 months. During this time, the CQ camel-k extension and the camel-k-runtime project have diverged. Is it still the intention that camel-k will eventually consume this work? I'm asking because there is a (minor(ish)) overhead in maintaining the CQ camel-k modules. And since the number of Maven modules in CQ is ever increasing, I like to take every opportunity to trim stuff from the project whenever possible. -- James
