-
Feature
-
Resolution: Done
-
Major
-
None
-
False
-
False
-
0
-
0%
-
Todo
-
Undefined
-
The recent upstream discussion [1] sparked a conversation about the support for camel components in Camel K and Camel Quarkus.
Long story short, we intend to suppress the use of camel components and want to enforce the use of Camel Quarkus extensions.
- How can we accomplish this and improve the user experience ?
- What are a users touchpoints where he or she can intentionally or accidentally leave the supported path?