Skip to content
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

Closed
essobedo opened this issue Jan 30, 2023 · 12 comments
Closed

Bump Mandrel from 22.2.0 to 22.3.1 #4017

essobedo opened this issue Jan 30, 2023 · 12 comments

Comments

@essobedo
Copy link
Contributor

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.

@essobedo
Copy link
Contributor Author

essobedo commented Jan 30, 2023

However starting from Mandrel 22.3 only Java 17 is supported, can I still propose a PR to upgrade?

@oscerd
Copy link
Contributor

oscerd commented Jan 30, 2023

Not until everything is in place to support jdk 17

@essobedo
Copy link
Contributor Author

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?

@oscerd
Copy link
Contributor

oscerd commented Jan 30, 2023

There was a discussion a while ago about this: #3817

@oscerd
Copy link
Contributor

oscerd commented Jan 30, 2023

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.

@essobedo
Copy link
Contributor Author

I see, it's clear now, thx for the input.

@oscerd
Copy link
Contributor

oscerd commented Jan 30, 2023

So at some point we should switch and probably this will be with Camel 4.

@squakez
Copy link
Contributor

squakez commented Jan 31, 2023

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

@essobedo
Copy link
Contributor Author

essobedo commented Feb 6, 2023

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?
I'm asking that because, with Mandrel as the root image, there is no way to support the native mode for the JS DSL or once done, predicates and expressions expressed in Python.

@squakez
Copy link
Contributor

squakez commented Feb 6, 2023

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.

@github-actions
Copy link
Contributor

github-actions bot commented May 8, 2023

This issue has been automatically marked as stale due to 90 days of inactivity.
It will be closed if no further activity occurs within 15 days.
If you think that’s incorrect or the issue should never stale, please simply write any comment.
Thanks for your contributions!

@squakez
Copy link
Contributor

squakez commented May 8, 2023

Since Camel K 2 onward, this should not be any longer a concern of the operator but of the runtime.

@squakez squakez closed this as not planned Won't fix, can't repro, duplicate, stale May 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants