oscerd opened a new pull request, #23460:
URL: https://github.com/apache/camel/pull/23460

   Backport of #23417 onto `camel-4.18.x` (target **4.18.3**).
   
   ## Summary
   
   Renames the Exchange header *string values* in `JiraConstants` from 
non-Camel-prefixed values (`IssueKey`, `ProjectKey`, `IssueTransitionId`, 
`linkType`, `minutesSpent`, …) to `CamelJira<Name>`, following the convention 
used across the rest of the Camel component catalog.
   
   - Java field names (`ISSUE_KEY`, `ISSUE_PROJECT_KEY`, …) are unchanged → 
routes referencing the constants symbolically keep working.
   - Routes using the literal string values must be updated → documented in the 
**4.18 upgrade guide** as a **potential breaking change**.
   - Generated Endpoint DSL header accessors on `JiraHeaderNameBuilder` renamed 
accordingly (`issueKey()` → `jiraIssueKey()`, …).
   - Producer error messages and component docs updated for consistency.
   
   Follows the rename pattern of CAMEL-23526 (`camel-cxf`), CAMEL-23522 
(`camel-mail`), CAMEL-23461 (`camel-aws-bedrock`). Part of the global sweep 
tracked by CAMEL-23577.
   
   ## Note on the upgrade guide
   
   Per the project backport policy, the matching 
`camel-4x-upgrade-guide-4_18.adoc` entry on `main` is synced in a separate 
doc-sync PR.
   
   ## Test plan
   
   - [x] `mvn -DskipTests install` in `components/camel-jira` on 4.18.x — 
catalog + docs regenerated cleanly; endpoint DSL regenerated.
   - [ ] CI full reactor build.
   
   _Reported by Claude Code on behalf of Andrea Cosentino_


-- 
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]

Reply via email to