davsclaus commented on PR #27433: URL: https://github.com/apache/camel/pull/27433#issuecomment-6336087220
I rebased this PR onto `main` (the conflict came from CAMEL-22996, which replaced the `getSignatureSchemes(...)` reflection helper with direct `SSLParameters.getSignatureSchemes()` calls) and added a commit, dc63de5d73ac, that disables `testSignatureSchemesFilter_postJDK26`. The test only runs on JDK 26 onwards (`@EnabledForJreRange(min = JAVA_26)`). Camel supports JDK 21 and 25, which CI builds with, so this test never runs in CI. It now has `@Disabled` and a code comment saying why. `@EnabledForJreRange` stays, so the test can be turned back on when a JDK 26+ release is supported. One thing to look at when it is turned back on: the comment this PR removes said an empty signature-scheme list "would fail every handshake", and the test now asserts that an empty filter produces an empty array. Neither expectation has been run on JDK 26 or 27 here. _Claude Code on behalf of davsclaus_ -- 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]
