luigidemasi opened a new issue, #168: URL: https://github.com/apache/camel-kit/issues/168
## Description Allow an existing Camel application to adopt Camel Kit and rerun initialization without silently replacing project-owned files or user customizations. ## Expected behavior Preserve existing build files, Maven wrappers, configuration, agent instructions and application sources. Detect conflicts before changing existing files. Any intentional replacement must be explicit and limited to the selected files. Reuse the current initialization and asset-generation mechanisms. ## Acceptance criteria - [ ] Initial adoption preserves the existing build tooling, configuration, instructions and application code unless a replacement was explicitly selected. - [ ] Conflicts produce an actionable result before conflicting files are changed. - [ ] Reinitialization preserves user customizations and unrelated files. - [ ] Automated tests exercise initial adoption, conflicting files and reinitialization; existing greenfield initialization retains its behavior. ## Scope and coordination Parent: #164. Initial scope: an existing Camel 4 application with YAML routes and one currently supported runtime. Broader runtime, DSL and project-layout coverage remains follow-up work. Coordinate with Jinal-Sarvaiya's existing work linked from #164. Share the representative application with the end-to-end example task. ## Website impact **Required.** Document safe adoption, conflict handling and reinitialization in `docs/modules/ROOT/**`; the documentation follow-up is #167. Keep it linked until the behavior is documented. _AI-generated by Codex on behalf of @luigidemasi._ -- 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]
