dweber019 commented on issue #1821: URL: https://github.com/apache/camel-k/issues/1821#issuecomment-961666076
@lburgazzoli yes sure. We had 4 options on the table: - Using jar with resource and classpath - Using Maven - Using jitpick - Using multiple RouteBuilder files As said our goal is to build small to medium sized routes. Will doing this we found the development process quit tedious. We first checked Maven but found that publishing even SNAPSHOTS every time we change the source code is not what we wanted especially as there can be other process involved in pushing into our artefact storage, e.g. security scans. The same issues we had with Jitpack. Commiting/pushing every change was not what we were looking for and felt not intuitiv. Additionally committing triggers some processes too, we don't need. We then checked if we can split everything into separated route builder files. We almost decided to go with this solution but then we tested the camel-openapi, as you can see in the example project and got errors regarding the POJO User, which could not be processed by the camel-openapi to build the OpenAPI YAML file as User was provided as inner class. Now we think that we will mostly start with the JAR option and try to keep our Camel implementations as small as possible to leverage Camel K but if not possible (e.g. CRD limit), we will switch to Camel with Spring/Quarkus. I hope this helps to understand the reasons. -- 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]
