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 3d641d1c077d CAMEL-23576: docs - sync camel-jira upgrade-guide entry
to main 4_18/4_14 and flag as potential breaking change (#23475)
3d641d1c077d is described below
commit 3d641d1c077d2f6fd1a3216487897a9b25e1c2c0
Author: Andrea Cosentino <[email protected]>
AuthorDate: Fri May 22 13:45:33 2026 +0200
CAMEL-23576: docs - sync camel-jira upgrade-guide entry to main 4_18/4_14
and flag as potential breaking change (#23475)
Doc-only sync of the camel-jira header-rename entry into
camel-4x-upgrade-guide-4_18.adoc and _4_14.adoc on main (canonical history),
mirroring backports #23460 / #23472. Also flags the 4.21 entry as a potential
breaking change. Part of CAMEL-23577.
---
.../ROOT/pages/camel-4x-upgrade-guide-4_14.adoc | 60 ++++++++++++++++++++++
.../ROOT/pages/camel-4x-upgrade-guide-4_18.adoc | 60 ++++++++++++++++++++++
.../ROOT/pages/camel-4x-upgrade-guide-4_21.adoc | 2 +-
3 files changed, 121 insertions(+), 1 deletion(-)
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 1cf1b467a7ae..717d5a5971ab 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
@@ -202,6 +202,66 @@ Even with the opt-in, route authors should still strip the
namespace with
In addition, the inbound `MailHeaderFilterStrategy` now blocks the
`mail.smtp.` / `mail.smtps.`
prefix as well, so an external mail message can no longer inject these into a
downstream exchange.
+=== camel-jira - potential breaking change
+
+The Exchange header constants in `JiraConstants` 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
+| `JiraConstants.ISSUE_ASSIGNEE_ID` | `IssueAssigneeId` |
`CamelJiraIssueAssigneeId`
+| `JiraConstants.ISSUE_ASSIGNEE` | `IssueAssignee` | `CamelJiraIssueAssignee`
+| `JiraConstants.ISSUE_COMPONENTS` | `IssueComponents` |
`CamelJiraIssueComponents`
+| `JiraConstants.ISSUE_COMMENT` | `IssueComment` | `CamelJiraIssueComment`
+| `JiraConstants.ISSUE_CHANGED` | `IssueChanged` | `CamelJiraIssueChanged`
+| `JiraConstants.ISSUE_KEY` | `IssueKey` | `CamelJiraIssueKey`
+| `JiraConstants.ISSUE_PRIORITY_ID` | `IssuePriorityId` |
`CamelJiraIssuePriorityId`
+| `JiraConstants.ISSUE_PRIORITY_NAME` | `IssuePriorityName` |
`CamelJiraIssuePriorityName`
+| `JiraConstants.ISSUE_PROJECT_KEY` | `ProjectKey` | `CamelJiraIssueProjectKey`
+| `JiraConstants.ISSUE_SUMMARY` | `IssueSummary` | `CamelJiraIssueSummary`
+| `JiraConstants.ISSUE_TRANSITION_ID` | `IssueTransitionId` |
`CamelJiraIssueTransitionId`
+| `JiraConstants.ISSUE_TYPE_ID` | `IssueTypeId` | `CamelJiraIssueTypeId`
+| `JiraConstants.ISSUE_TYPE_NAME` | `IssueTypeName` | `CamelJiraIssueTypeName`
+| `JiraConstants.ISSUE_WATCHED_ISSUES` | `IssueWatchedIssues` |
`CamelJiraIssueWatchedIssues`
+| `JiraConstants.ISSUE_WATCHERS_ADD` | `IssueWatchersAdd` |
`CamelJiraIssueWatchersAdd`
+| `JiraConstants.ISSUE_WATCHERS_REMOVE` | `IssueWatchersRemove` |
`CamelJiraIssueWatchersRemove`
+| `JiraConstants.PARENT_ISSUE_KEY` | `ParentIssueKey` |
`CamelJiraParentIssueKey`
+| `JiraConstants.CHILD_ISSUE_KEY` | `ChildIssueKey` | `CamelJiraChildIssueKey`
+| `JiraConstants.LINK_TYPE` | `linkType` | `CamelJiraLinkType`
+| `JiraConstants.MINUTES_SPENT` | `minutesSpent` | `CamelJiraMinutesSpent`
+|===
+
+Routes that reference the constants symbolically (for example
+`setHeader(JiraConstants.ISSUE_KEY, ...)`) continue to work without changes.
+Routes that set the header by its literal string value (for example
+`setHeader("IssueKey", ...)`) must be updated to use the new value
+(`setHeader("CamelJiraIssueKey", ...)`).
+
+As a consequence, the generated Endpoint DSL header accessors on
+`JiraHeaderNameBuilder` have been renamed accordingly:
+
+* `issueAssigneeId()` -> `jiraIssueAssigneeId()`
+* `issueAssignee()` -> `jiraIssueAssignee()`
+* `issueComponents()` -> `jiraIssueComponents()`
+* `issueChanged()` -> `jiraIssueChanged()`
+* `issueKey()` -> `jiraIssueKey()`
+* `issuePriorityId()` -> `jiraIssuePriorityId()`
+* `issuePriorityName()` -> `jiraIssuePriorityName()`
+* `projectKey()` -> `jiraIssueProjectKey()`
+* `issueSummary()` -> `jiraIssueSummary()`
+* `issueTransitionId()` -> `jiraIssueTransitionId()`
+* `issueTypeId()` -> `jiraIssueTypeId()`
+* `issueTypeName()` -> `jiraIssueTypeName()`
+* `issueWatchedIssues()` -> `jiraIssueWatchedIssues()`
+* `issueWatchersAdd()` -> `jiraIssueWatchersAdd()`
+* `issueWatchersRemove()` -> `jiraIssueWatchersRemove()`
+* `parentIssueKey()` -> `jiraParentIssueKey()`
+* `childIssueKey()` -> `jiraChildIssueKey()`
+* `linkType()` -> `jiraLinkType()`
+* `minutesSpent()` -> `jiraMinutesSpent()`
+
== Upgrading from 4.14.2 to 4.14.3
=== camel-tika
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 f2a1f558a29d..8d86e6960dc4 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
@@ -234,6 +234,66 @@ Even with the opt-in, route authors should still strip the
namespace with
In addition, the inbound `MailHeaderFilterStrategy` now blocks the
`mail.smtp.` / `mail.smtps.`
prefix as well, so an external mail message can no longer inject these into a
downstream exchange.
+=== camel-jira - potential breaking change
+
+The Exchange header constants in `JiraConstants` 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
+| `JiraConstants.ISSUE_ASSIGNEE_ID` | `IssueAssigneeId` |
`CamelJiraIssueAssigneeId`
+| `JiraConstants.ISSUE_ASSIGNEE` | `IssueAssignee` | `CamelJiraIssueAssignee`
+| `JiraConstants.ISSUE_COMPONENTS` | `IssueComponents` |
`CamelJiraIssueComponents`
+| `JiraConstants.ISSUE_COMMENT` | `IssueComment` | `CamelJiraIssueComment`
+| `JiraConstants.ISSUE_CHANGED` | `IssueChanged` | `CamelJiraIssueChanged`
+| `JiraConstants.ISSUE_KEY` | `IssueKey` | `CamelJiraIssueKey`
+| `JiraConstants.ISSUE_PRIORITY_ID` | `IssuePriorityId` |
`CamelJiraIssuePriorityId`
+| `JiraConstants.ISSUE_PRIORITY_NAME` | `IssuePriorityName` |
`CamelJiraIssuePriorityName`
+| `JiraConstants.ISSUE_PROJECT_KEY` | `ProjectKey` | `CamelJiraIssueProjectKey`
+| `JiraConstants.ISSUE_SUMMARY` | `IssueSummary` | `CamelJiraIssueSummary`
+| `JiraConstants.ISSUE_TRANSITION_ID` | `IssueTransitionId` |
`CamelJiraIssueTransitionId`
+| `JiraConstants.ISSUE_TYPE_ID` | `IssueTypeId` | `CamelJiraIssueTypeId`
+| `JiraConstants.ISSUE_TYPE_NAME` | `IssueTypeName` | `CamelJiraIssueTypeName`
+| `JiraConstants.ISSUE_WATCHED_ISSUES` | `IssueWatchedIssues` |
`CamelJiraIssueWatchedIssues`
+| `JiraConstants.ISSUE_WATCHERS_ADD` | `IssueWatchersAdd` |
`CamelJiraIssueWatchersAdd`
+| `JiraConstants.ISSUE_WATCHERS_REMOVE` | `IssueWatchersRemove` |
`CamelJiraIssueWatchersRemove`
+| `JiraConstants.PARENT_ISSUE_KEY` | `ParentIssueKey` |
`CamelJiraParentIssueKey`
+| `JiraConstants.CHILD_ISSUE_KEY` | `ChildIssueKey` | `CamelJiraChildIssueKey`
+| `JiraConstants.LINK_TYPE` | `linkType` | `CamelJiraLinkType`
+| `JiraConstants.MINUTES_SPENT` | `minutesSpent` | `CamelJiraMinutesSpent`
+|===
+
+Routes that reference the constants symbolically (for example
+`setHeader(JiraConstants.ISSUE_KEY, ...)`) continue to work without changes.
+Routes that set the header by its literal string value (for example
+`setHeader("IssueKey", ...)`) must be updated to use the new value
+(`setHeader("CamelJiraIssueKey", ...)`).
+
+As a consequence, the generated Endpoint DSL header accessors on
+`JiraHeaderNameBuilder` have been renamed accordingly:
+
+* `issueAssigneeId()` -> `jiraIssueAssigneeId()`
+* `issueAssignee()` -> `jiraIssueAssignee()`
+* `issueComponents()` -> `jiraIssueComponents()`
+* `issueChanged()` -> `jiraIssueChanged()`
+* `issueKey()` -> `jiraIssueKey()`
+* `issuePriorityId()` -> `jiraIssuePriorityId()`
+* `issuePriorityName()` -> `jiraIssuePriorityName()`
+* `projectKey()` -> `jiraIssueProjectKey()`
+* `issueSummary()` -> `jiraIssueSummary()`
+* `issueTransitionId()` -> `jiraIssueTransitionId()`
+* `issueTypeId()` -> `jiraIssueTypeId()`
+* `issueTypeName()` -> `jiraIssueTypeName()`
+* `issueWatchedIssues()` -> `jiraIssueWatchedIssues()`
+* `issueWatchersAdd()` -> `jiraIssueWatchersAdd()`
+* `issueWatchersRemove()` -> `jiraIssueWatchersRemove()`
+* `parentIssueKey()` -> `jiraParentIssueKey()`
+* `childIssueKey()` -> `jiraChildIssueKey()`
+* `linkType()` -> `jiraLinkType()`
+* `minutesSpent()` -> `jiraMinutesSpent()`
+
== Upgrading from 4.18.0 to 4.18.1
=== camel-bom
diff --git
a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_21.adoc
b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_21.adoc
index 25aacb7fc001..132102d0006c 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_21.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_21.adoc
@@ -720,7 +720,7 @@ to work without changes. Routes that set the header by its
literal string value
(for example `setHeader("JGROUPSRAFT_SET_TIMEOUT", ...)`) must be updated to
use the new value (`setHeader("CamelJGroupsRaftSetTimeout", ...)`).
-=== camel-jira
+=== camel-jira - potential breaking change
The Exchange header constants in `JiraConstants` have been renamed to follow
the
Camel naming convention used across the rest of the component catalog. The Java
