CAMEL-23510: doc-sync 4.18 upgrade guide for camel-jgroups header rename#23219
Merged
Conversation
Signed-off-by: Andrea Cosentino <ancosen@gmail.com>
Contributor
|
🌟 Thank you for your contribution to the Apache Camel project! 🌟 🐫 Apache Camel Committers, please review the following items:
|
davsclaus
approved these changes
May 14, 2026
Contributor
|
🧪 CI tested the following changed modules:
|
oscerd
added a commit
that referenced
this pull request
May 14, 2026
…eader constant names with Camel naming convention Cherry-pick of #23209 onto camel-4.18.x. Rename the Exchange header string values in JGroupsConstants to the Camel naming convention (CamelJGroupsDest, CamelJGroupsSrc, CamelJGroupsChannelAddress, CamelJGroupsOriginalMessage). The Java field names are unchanged so routes referencing the constants symbolically continue to work. Routes using the literal string value must be updated. The original commit also modified camel-4x-upgrade-guide-4_21.adoc, which does not exist on camel-4.18.x; the corresponding 4.18 upgrade guide entry is added on main via doc-sync PR #23219. Closes #23213
2 tasks
oscerd
added a commit
that referenced
this pull request
May 22, 2026
…hange in 4.18 upgrade guide (#23471) Follow-up to #23209 completing the breaking-change labelling across all affected upgrade guides. The JGroups header rename was backported to camel-4.18.x (#23213) and documented on main's 4.18 guide via doc-sync #23219, but that entry did not flag the rename as a breaking change. - Heading suffixed with " - potential breaking change" (matching the camel-grok convention). - Prose leads with an explicit "This is a breaking change for routes that ..." sentence. Docs only; identical wording to the 4.14 guide (#23422 / #23441) and the 4.21 guide (#23451).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Doc-sync companion to the camel-4.18.x backport PR #23213 for CAMEL-23510.
Per the project policy in
CLAUDE.md:This PR adds the
camel-jgroupsentry todocs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adocunder the
Upgrading from 4.18.1 to 4.18.3section, documenting the renameof the JGroups Exchange header string values to the
CamelJGroups*convention.
Related
Test plan
Claude Code on behalf of Andrea Cosentino