This is an automated email from the ASF dual-hosted git repository.
oscerd pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/main by this push:
new 39fc460d3213 CAMEL-23629: docs - sync camel-irc 4.18 and 4.14
upgrade-guide entries to main (#23991)
39fc460d3213 is described below
commit 39fc460d3213155fceeb4ed01654019f0f9f2e98
Author: Andrea Cosentino <[email protected]>
AuthorDate: Fri Jun 12 18:33:20 2026 +0200
CAMEL-23629: docs - sync camel-irc 4.18 and 4.14 upgrade-guide entries to
main (#23991)
The camel-irc Exchange header rename (CAMEL-23629) was backported to
camel-4.18.x and camel-4.14.x, which added the upgrade-guide entry to the
4_18 and 4_14 guides on those maintenance branches. Per the upgrade-guide
policy, the version-specific guides on main are the canonical history and
must carry the same entries.
This syncs the camel-irc 'potential breaking change' entry into
camel-4x-upgrade-guide-4_18.adoc and camel-4x-upgrade-guide-4_14.adoc on
main, matching the existing 4_21 entry.
---
.../ROOT/pages/camel-4x-upgrade-guide-4_14.adoc | 38 ++++++++++++++++++++++
.../ROOT/pages/camel-4x-upgrade-guide-4_18.adoc | 38 ++++++++++++++++++++++
2 files changed, 76 insertions(+)
diff --git
a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_14.adoc
b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_14.adoc
index 73142b2eaf49..33272e01268b 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_14.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_14.adoc
@@ -803,6 +803,44 @@ The generated Endpoint DSL header accessors on each
component's
`openstackOperation()`, `password()` -> `openstackKeystonePassword()`,
`adminPassword()` -> `openstackNovaAdminPassword()`, etc.).
+=== camel-irc - potential breaking change
+
+The Exchange header constants in `IrcConstants` have been renamed to follow the
+Camel naming convention used across the rest of the component catalog. The Java
+field names are unchanged; only the header string values have changed:
+
+[options="header"]
+|===
+| Constant | Previous value | New value
+| `IrcConstants.IRC_MESSAGE_TYPE` | `irc.messageType` |
`CamelIrcMessageType`
+| `IrcConstants.IRC_TARGET` | `irc.target` |
`CamelIrcTarget`
+| `IrcConstants.IRC_SEND_TO` | `irc.sendTo` |
`CamelIrcSendTo`
+| `IrcConstants.IRC_USER_KICKED` | `irc.user.kicked` |
`CamelIrcUserKicked`
+| `IrcConstants.IRC_USER_HOST` | `irc.user.host` |
`CamelIrcUserHost`
+| `IrcConstants.IRC_USER_NICK` | `irc.user.nick` |
`CamelIrcUserNick`
+| `IrcConstants.IRC_USER_SERVERNAME` | `irc.user.servername` |
`CamelIrcUserServername`
+| `IrcConstants.IRC_USER_USERNAME` | `irc.user.username` |
`CamelIrcUserUsername`
+| `IrcConstants.IRC_NUM` | `irc.num` | `CamelIrcNum`
+| `IrcConstants.IRC_VALUE` | `irc.value` | `CamelIrcValue`
+|===
+
+Routes that reference the constant symbolically (for example
+`header(IrcConstants.IRC_SEND_TO)` or
+`setHeader(IrcConstants.IRC_TARGET, ...)`) continue to work without changes.
+Routes that set or read the header by its literal string value (for example
+`setHeader("irc.sendTo", ...)`) must be updated to use the new value:
+
+[source,java]
+----
+// before
+template.sendBodyAndHeader("irc:[email protected]/#chan", "hello",
+ "irc.sendTo", "#otherchan");
+
+// after
+template.sendBodyAndHeader("irc:[email protected]/#chan", "hello",
+ "CamelIrcSendTo", "#otherchan");
+----
+
=== camel-mongodb-gridfs - potential breaking change
The Exchange header values exposed by `GridFsConstants` have been renamed to
follow the standard
diff --git
a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc
b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc
index 476a5a79f1a4..479ed71ecaf5 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc
@@ -905,6 +905,44 @@ Routes that set the header by its literal string value
(for example
As a consequence, the generated Endpoint DSL header accessor `await()` on
`MiloClientHeaderNameBuilder` has been renamed to `miloAwait()`.
+=== camel-irc - potential breaking change
+
+The Exchange header constants in `IrcConstants` have been renamed to follow the
+Camel naming convention used across the rest of the component catalog. The Java
+field names are unchanged; only the header string values have changed:
+
+[options="header"]
+|===
+| Constant | Previous value | New value
+| `IrcConstants.IRC_MESSAGE_TYPE` | `irc.messageType` |
`CamelIrcMessageType`
+| `IrcConstants.IRC_TARGET` | `irc.target` |
`CamelIrcTarget`
+| `IrcConstants.IRC_SEND_TO` | `irc.sendTo` |
`CamelIrcSendTo`
+| `IrcConstants.IRC_USER_KICKED` | `irc.user.kicked` |
`CamelIrcUserKicked`
+| `IrcConstants.IRC_USER_HOST` | `irc.user.host` |
`CamelIrcUserHost`
+| `IrcConstants.IRC_USER_NICK` | `irc.user.nick` |
`CamelIrcUserNick`
+| `IrcConstants.IRC_USER_SERVERNAME` | `irc.user.servername` |
`CamelIrcUserServername`
+| `IrcConstants.IRC_USER_USERNAME` | `irc.user.username` |
`CamelIrcUserUsername`
+| `IrcConstants.IRC_NUM` | `irc.num` | `CamelIrcNum`
+| `IrcConstants.IRC_VALUE` | `irc.value` | `CamelIrcValue`
+|===
+
+Routes that reference the constant symbolically (for example
+`header(IrcConstants.IRC_SEND_TO)` or
+`setHeader(IrcConstants.IRC_TARGET, ...)`) continue to work without changes.
+Routes that set or read the header by its literal string value (for example
+`setHeader("irc.sendTo", ...)`) must be updated to use the new value:
+
+[source,java]
+----
+// before
+template.sendBodyAndHeader("irc:[email protected]/#chan", "hello",
+ "irc.sendTo", "#otherchan");
+
+// after
+template.sendBodyAndHeader("irc:[email protected]/#chan", "hello",
+ "CamelIrcSendTo", "#otherchan");
+----
+
=== camel-mongodb-gridfs
The Exchange header values exposed by `GridFsConstants` have been renamed to
follow the standard
