-
Notifications
You must be signed in to change notification settings - Fork 350
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump Mandrel from 22.2.0 to 22.3.1 #4017
Comments
However starting from Mandrel 22.3 only Java 17 is supported, can I still propose a PR to upgrade? |
Not until everything is in place to support jdk 17 |
So it cannot be upgraded until Camel-K supports Camel 4 and Camel-Quarkus 3, is it what you mean? Because as you can see from the CI of Camel and Camel-Quarkus, they are both already tested against Java 17, isn't it good enough? |
There was a discussion a while ago about this: #3817 |
I know well that both Camel and CQ could be build with JDK 17 and run correctly with it, but we don't release them using Java 17, we built with Java 11. |
I see, it's clear now, thx for the input. |
So at some point we should switch and probably this will be with Camel 4. |
With the work I'm doing to address #3831 this is not going be any longer necessary. Everything related to the build and runtime (including Mandrel distro) will be only configured in the runtime, hence will be part of the configuration required to run Camel Quarkus/Camel (with JDK 17 most presumably). |
BTW, is there any technical lock with Mandrel, or in theory, Camel-K should also work with GraalVM as the root image for the operator? |
That's exactly the scope of #4025. Right now we need to keep it as it is (with Mandrel) as the build time requires the very same bits of the runtime to build natively. If this is limiting some DSL in native mode, we can mark them as not yet available. |
This issue has been automatically marked as stale due to 90 days of inactivity. |
Since Camel K 2 onward, this should not be any longer a concern of the operator but of the runtime. |
There is a bug that has been fixed between Mandrel 22.2.0 and 22.3.1, upgrading the version of Mandrel will fix the bug.
The text was updated successfully, but these errors were encountered: