[backport camel-4.14.x] CAMEL-23629: camel-irc - align Exchange header constant names with Camel naming convention#23635
Open
oscerd wants to merge 1 commit into
Open
Conversation
…mel naming convention Rename the Exchange header string values in IrcConstants from the non-Camel-prefixed "irc.*" namespace to the project-wide "CamelIrc*" PascalCase convention, keeping the Java field names unchanged so symbolic references keep working. Part of the CAMEL-23577 global header-naming sweep. Updates the integration tests, component docs and setNamesOnJoin Javadoc, regenerates the camel-catalog and endpoint DSL artifacts, and adds a 4.14 upgrade-guide "potential breaking change" entry. Backport of apache#23594. (cherry picked from commit 0be886b) Signed-off-by: Andrea Cosentino <ancosen@gmail.com>
davsclaus
approved these changes
May 29, 2026
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.
Backport of #23594 to
camel-4.14.xCherry-pick of #23594 (
CAMEL-23629) ontocamel-4.14.x, part of the CAMEL-23577 header-naming sweep. Target release: 4.14.8.Original PR: #23594 — CAMEL-23629: camel-irc - align Exchange header constant names with Camel naming convention
Jira: https://issues.apache.org/jira/browse/CAMEL-23629
4.18.x backport: #23616 (merged)
Constants renamed
IrcConstants.IRC_MESSAGE_TYPEirc.messageTypeCamelIrcMessageTypeIrcConstants.IRC_TARGETirc.targetCamelIrcTargetIrcConstants.IRC_SEND_TOirc.sendToCamelIrcSendToIrcConstants.IRC_USER_KICKEDirc.user.kickedCamelIrcUserKickedIrcConstants.IRC_USER_HOSTirc.user.hostCamelIrcUserHostIrcConstants.IRC_USER_NICKirc.user.nickCamelIrcUserNickIrcConstants.IRC_USER_SERVERNAMEirc.user.servernameCamelIrcUserServernameIrcConstants.IRC_USER_USERNAMEirc.user.usernameCamelIrcUserUsernameIrcConstants.IRC_NUMirc.numCamelIrcNumIrcConstants.IRC_VALUEirc.valueCamelIrcValueCompatibility
Java field names are unchanged — routes referencing the constants symbolically keep working. Routes using the literal
irc.*string values must move toCamelIrc*.Backport notes
camel-4x-upgrade-guide-4_21.adoc(absent oncamel-4.14.x). Per the sweep convention, that hunk was dropped and the equivalent "camel-irc - potential breaking change" entry (rename table + cross-transportHeaderFilterStrategynote) was added tocamel-4x-upgrade-guide-4_14.adoc, in theUpgrading from 4.14.7 to 4.14.8section alongside the sibling sub-task entries. The canonical 4_14 guide onmainis doc-synced separately as part of CAMEL-23577.IrcConstantson 4.14.x is not@Deprecated(deprecation is 4.21-only).Local build
Full reactor
mvn clean install -DskipTestsoncamel-4.14.x— green (11810 goals, 10275 executed, 1535 cached), no uncommitted regen drift.Claude Code on behalf of Andrea Cosentino