davsclaus commented on PR #28329:
URL: https://github.com/apache/camel/pull/28329#issuecomment-6358897582

   I pushed a follow-up commit (250252c) so this backport builds on 
camel-4.18.x.
   
   The cherry-pick brought the two new tests (`PQCBinaryBodySignatureTest`, 
`PQCFileBodySignatureTest`) over from `main` unchanged, where they use:
   
   - the hybrid signature API (`hybridSign`/`hybridVerify`, `HybridSignature`, 
`PQCClassicalSignatureAlgorithms`) — but camel-4.18.x has only the `sign` and 
`verify` operations; and
   - `camel-test-junit6` — but camel-4.18.x uses `camel-test-junit5`.
   
   Both would fail to compile here. The tests now cover the single-algorithm 
`sign`/`verify` over `byte[]`, `ByteBuffer`, `ByteArrayOutputStream`, `File`, 
`Path`, `GenericFile` and `String` bodies, plus `Map`/POJO rejection, and 
import `camel-test-junit5`.
   
   I also added the `camel-pqc` entry to the 4.18.6 upgrade guide — the 
cherry-pick's note targeted the 4.24 guide, which doesn't exist on this branch. 
(The catalog `.adoc` hunk was correctly dropped, since that generated file 
isn't present on 4.18.x.)
   
   Local `mvn -pl components/camel-pqc test` is green (131 tests, 0 failures). 
The 4.22/4.18 upgrade-guide notes are synced to `main` in #28332.
   


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