You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by "oscerd (via GitHub)" <gi...@apache.org> on 2026/05/27 13:17:06 UTC
[PR] [backport camel-4.14.x] CAMEL-23591: camel-mail - align consumer-side dispatch header constant names with Camel naming convention [camel]
oscerd opened a new pull request, #23564:
URL: https://github.com/apache/camel/pull/23564
Backports #23478 to `camel-4.14.x`. Standard 4_21 → 4_14 guide-file adaptation. Three consumer-side dispatch headers renamed (`copyTo` / `moveTo` / `delete` → `CamelMailCopyTo` / `CamelMailMoveTo` / `CamelMailDelete`); RFC 5322 message headers unchanged. mvn test passes on 4.14.x.
Tracker: CAMEL-23577
_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: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] [backport camel-4.14.x] CAMEL-23591: camel-mail - align consumer-side dispatch header constant names with Camel naming convention [camel]
Posted by "oscerd (via GitHub)" <gi...@apache.org>.
oscerd merged PR #23564:
URL: https://github.com/apache/camel/pull/23564
--
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: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] [backport camel-4.14.x] CAMEL-23591: camel-mail - align consumer-side dispatch header constant names with Camel naming convention [camel]
Posted by "oscerd (via GitHub)" <gi...@apache.org>.
oscerd commented on PR #23564:
URL: https://github.com/apache/camel/pull/23564#issuecomment-4556499263
Local `mvn test` reported 2 failures in `MimeMultipartAlternativeWithLongerFilenameTest.testMultipartEmailWithRegularAttachments` (`Received message count. Expected: <1> but was: <0>`). Re-running that test in isolation (`mvn test -Dtest=MimeMultipartAlternativeWithLongerFilenameTest`) passes consistently. The test exercises multipart mail attachment rendering and does not touch `MAIL_COPY_TO` / `MAIL_MOVE_TO` / `MAIL_DELETE` (the three constants this backport renames), so the failure is a pre-existing timing/ordering flake unrelated to this PR.
_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: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org