arthurdm commented on issue #1821: URL: https://github.com/apache/camel-k/issues/1821#issuecomment-874892031
hey everyone - I agree with a lot of points made here from both sides. There should be a way to reuse POJOs that is lightweight and doesn't require a lot of process, to enable development teams that are pulling from a common source repo within an organization. At the same time, having all of those POJOs duplicated inside different CRs definitely can quickly hit size limitations. I guess the CR size ceiling is something we could hit even without POJOs, just with an extremely long Route class. There may be some higher architectural decisions there in terms of is Camel K well suitable for complex projects versus smaller re-routing / transformation module? I think @zregvart made some very good arguments for solving this via container images that have the code + dependencies. The Camel K CR could then just reference the source code image, and the Operator would take over from there in terms of creating a runnable image that has the compiled code + dependencies. -- 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
