-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Update to graalvm and mandrel 22.3.0 - 2.13 #29028
Update to graalvm and mandrel 22.3.0 - 2.13 #29028
Conversation
cescoffier
commented
Nov 3, 2022
•
edited
Loading
edited
- Update to GraalVM and Mandrel 22.3.0 images
- Use the GraalVM 22.3 AlwaysInline annotation
Thanks for your pull request! The title of your pull request does not follow our editorial rules. Could you have a look?
|
This comment has been minimized.
This comment has been minimized.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, other than the documentation issue.
Thanks @cescoffier
8a6fa2b
to
181ecc3
Compare
@ppalaga here is your 2.13 branch with GraalVM 22.3 ^ |
Don't worry about the quickstarts compilation, that's normal. |
Cherry-Pick of 4eecb96
This annotation has moved to a new package and we need to use the 22.3 version to make sure our code compiles. As for using 22.2, it still works but the annotation is ignored, which looks OK as the annotation is not used in places where it is strictly necessary. If people use the recommended GraalVM version, everything will be fine. If not, things will mostly work anyway. (cherry picked from commit 6c5700f)
181ecc3
to
c087f36
Compare
Failing Jobs - Building c087f36
Full information is available in the Build summary check run. Failures⚙️ JVM Tests - JDK 11 #- Failing: extensions/smallrye-reactive-messaging-amqp/deployment
! Skipped: integration-tests/reactive-messaging-amqp 📦 extensions/smallrye-reactive-messaging-amqp/deployment✖
|
The reasoning behind this short-circuiting is to clean up the code-path used when obtaining a Validator object programmatically. This ultimately makes it possible for code that obtains the Validator object programmatically to work in native mode. Fixes: quarkusio#29028
The reasoning behind this short-circuiting is to clean up the code-path used when obtaining a Validator object programmatically. This ultimately makes it possible for code that obtains the Validator object programmatically to work in native mode. Fixes: quarkusio#29028 (cherry picked from commit d41f300)