luigidemasi commented on issue #163: URL: https://github.com/apache/camel-kit/issues/163#issuecomment-6741991135
@janihur thanks for raising this. You’re right that the documentation doesn’t clearly explain this scenario. The intended scope includes adding substantial functionality to existing Camel applications. That is a good fit for the design → plan → execute → validate workflow. However, the current guidance focuses on greenfield development and migration, and the brownfield path needs more explicit treatment. The approach I have in mind is: - Understand the existing application: routes, dependencies, configuration, contracts and tests. - Define the new functionality and its integration points, including existing behavior that must remain unchanged. - Produce a design and implementation plan scoped to that addition. - Implement and verify the change, including regression tests for the affected existing flows. I’d like to turn this into a documented workflow with a concrete example. There are still gaps to address: the brainstorm guidance assumes greenfield work, and code generation currently focuses on YAML routes, so I wouldn’t claim seamless support for every existing project layout or DSL. Could you share your Camel version, runtime (Spring Boot, Quarkus or Camel Main), route DSL, and an example of the functionality you want to add? That would help identify a useful first trial. I’d suggest doing it on a branch and reviewing the initialization changes, since init can replace existing Maven wrapper files. -- 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]
