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

   ## Summary
   
   Renames the Exchange header constants in `JGroupsRaftConstants` from the raw 
`JGROUPSRAFT_*` form to the standard `CamelJGroupsRaft*` naming convention used 
across the rest of the Camel component catalog.
   
   The Java field names are unchanged; only the underlying header string values 
are updated, so any route or processor that references the constant 
symbolically (e.g. 
`setHeader(JGroupsRaftConstants.HEADER_JGROUPSRAFT_SET_TIMEOUT, ...)`) 
continues to work without source changes. Routes that hard-code the literal 
string value need to be updated; the upgrade guide entry documents the mapping.
   
   ## Changes
   
   - 
`components/camel-jgroups-raft/src/main/java/org/apache/camel/component/jgroups/raft/JGroupsRaftConstants.java`
 — 12 header constant values renamed to the `CamelJGroupsRaft*` convention. 
`DEFAULT_JGROUPSRAFT_CONFIG` (which is a config file name, not a header) is 
left untouched.
   - `docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_21.adoc` — 
added an entry documenting the rename and the symbolic-vs-literal compatibility 
story.
   - Regenerated metadata: component JSON descriptor, the catalog mirror, and 
the endpoint DSL header builder factory.
   
   ## Jira
   
   https://issues.apache.org/jira/browse/CAMEL-23511
   
   ## Test plan
   
   - [x] `mvn -DskipTests install` in `components/camel-jgroups-raft`
   - [x] `mvn test` in `components/camel-jgroups-raft` (7 tests pass — header 
lookups use the Java constant, so they exercise the new value)
   - [x] Full reactor `mvn clean install -DskipTests` from repo root — 
succeeds, all regenerated artifacts are committed
   
   _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