squakez commented on PR #5090: URL: https://github.com/apache/camel-k/pull/5090#issuecomment-1914749075
> > Also, there is no need anymore to the [camel-k extension in camel-quarkus](https://github.com/apache/camel-quarkus/tree/main/extensions/camel-k). > > When I first saw this change, I wondered about that. > > Does this mean we could remove the camel-k bits from CQ? > > And could that change be done now so that it's complete in time for the next CQ LTS release? AFAIK, camel-k has not consumed the camel-k-runtime extension from CQ yet. That's correct. As soon as this development is complete, we can remove the related ck-runtime bits from CQ and in general make the dependency process much smoother. It's possible that however we'll need to include the catalog into CQ or extend the one available there, but it should be done via maven plugin. Not reached yet that part, I expect this development to last still a bit :) -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
