jamesnetherton opened a new issue, #7587: URL: https://github.com/apache/camel-quarkus/issues/7587
One of the challenges we face is to ensure we have consistent UX when users start prototyping with UI designers like Kaoto / Camel JBang and then export their apps to the chosen runtime. This becomes difficult if the runtime enforces additional requirements and constraints on top of the vanilla Camel component UX. E.g requiring additional runtime specific configuration properties, CDI beans, dependencies etc. Therefore, it may be desirable to stop depending on `quarkus-langchain4j` and just use the Camel component functionality as-is so that the UX stays identical across all runtimes. Some things to consider: * We'd have to implement native support * We loose some build time optimisations * We need to ensure we stay compatible with the LangChain4j version used in the Quarkus Platform (this is an existing concern TBH) * We'd probably have to deprecate / remove `camel-quarkus-langchain4j`. See https://github.com/apache/camel-quarkus/issues/7586. I can do some initial investigation into how difficult it is to remove `quarkus-langchain4j` and restore native mode support. We should try to make a decision on whether we want to go ahead with this change before the 3.27.0 LTS. Maybe even for 3.26.0 but I'm not sure there's time... -- 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]
