k-krawczyk commented on PR #25409: URL: https://github.com/apache/camel/pull/25409#issuecomment-5228424813
Thanks @davsclaus, @orpiske, @oscerd and @Croway for the reviews. All three points are addressed in f9b994720. **Required change — upgrade guide moved to 4.23.** The entry is now in a new `camel-4x-upgrade-guide-4_23.adoc`, created with the same header as the other guides and a `== Upgrading Camel 4.22 to 4.23` section, and removed from the 4.22 guide. I also added the `xref` for it in `camel-4x-upgrade-guide.adoc`, otherwise the new page would be orphaned from the index. On the timing: I created the 4.23 guide here so the PR is complete, but I understand the merge should wait until `main` has been prepared for 4.23. If you would rather create that file yourself as part of preparing the branch, say so and I will drop it from this PR and rebase. **Suggestion 1 — deprecated Spring archetype.** Both the `README.md` and the `AGENTS.md` of `camel-archetype-spring` now state that the archetype is deprecated and point at Camel on Spring Boot or `camel init`, so an agent knows before investing effort. Good catch. **Suggestion 2 — data format link.** The `camel-archetype-dataformat` docs now reference https://camel.apache.org/manual/data-format.html for the concept, next to the existing `writing-components` page for the implementation details. Link verified. Re-verified after the change: archetypes rebuild, `apache-rat-plugin:check` reports 0 unapproved, and I regenerated projects from the `spring` and `dataformat` archetypes to confirm the new content lands correctly. _Reported by Claude Code on behalf of Karol Krawczyk_ -- 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]
