squakez commented on code in PR #4456:
URL: https://github.com/apache/camel-k/pull/4456#discussion_r1219761826
##########
resources/camel-catalog-2.16.0-SNAPSHOT.yaml:
##########
@@ -38,6 +38,14 @@ spec:
- groupId: org.apache.camel.k
artifactId: camel-k-runtime
capabilities:
Review Comment:
> We can use capabilities in this traits context and once we have a clear
view of the traits/capabilities, we can interactively separate them with a
clear contract in the api and catalog.
No. This is a design choice we need to take now as we don't want to break
future compatibility. I think the most conservative approach is to split the
concepts as they may evolve differently in the future.
--
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-unsubscr...@camel.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
