jiriOndrusek-agent opened a new pull request, #9201: URL: https://github.com/apache/camel-quarkus/pull/9201
Fixes #9200 **Failed run:** https://github.com/apache/camel-quarkus/actions/runs/35573093554 (`camel-main`, Native Tests - group-03) ### Problem `SedaVirtualThreadsIT` fails on `camel-main` because the CI builds Camel from source on JDK 17. Camel compiles its Java 21/25 multi-release sources (e.g. the virtual thread aware `CamelThreadFactory`) only when built on JDK 21+ (`java-21-sources` / `java-25-sources` profiles in `core/camel-util/pom.xml`), so the CI-built jars lack those classes, unlike the released Camel jars used on `main`. ### Change Set up JDK 25 only for the "Build Camel" step and switch back to JDK 17 right after it, in both `ci-build.yaml` (guarded by the existing camel-main condition, so inert on `main` and PR builds) and `camel-master-cron.yaml`. The JDK 17 baseline of camel-quarkus is unchanged. ### Verification Locally the native `SedaVirtualThreadsIT` passes with camel-util built on JDK 25 and fails with the CI message when the Java 21/25 profiles are disabled (equivalent to a JDK 17 build). actionlint reports nothing new for either workflow. 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- 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]
