Croway commented on PR #22587: URL: https://github.com/apache/camel/pull/22587#issuecomment-4242193809
> > with jdk 17 the multi jar deployment for virtual threads does not work, use jdk21 instead. > > Do you mean that we must use a JDK 21+ to compile Camel source code to have virtual threads potentially used when running with JDk 21+? If yes, it is a bit weird and even more importantly it means that we also need to ensure that the "release" bits are compiled with JDK21+ to have it usable. Which I'm not sure how to enforce as it is built on the local machine of the releaser. @apupier at the moment we are not enforcing it, but you have a good point, we should, it should be doable via the maven-enforcer-plugin. Gregor, the release manager, always released Camel with JDK 21 (or JDK 25, since there is a profile for it) and this is the correct approach, given that the compatibility is [JDK17](https://github.com/apache/camel/blob/main/pom.xml#L113) anyway (@davsclaus @oscerd may you confirm I didn't write any blasphemy please?). Anyway, the issue with the SNAPSHOT is that the JDK21 (virtual thread) snapshot is not released, and one spring boot test is failing when running the test suite with jdk21 since the jar is not released as expected. I'd merge it, and we can discuss a `maven-enforcer-plugin` configuration, wdyt? -- 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]
