-
Notifications
You must be signed in to change notification settings - Fork 3
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
JDK 24+13 based Mandrel 24.2 builds produce warnings #278
Comments
Discussion about this here: |
This should be fixed once oracle/graal#9654 merges. |
oracle/graal#9654 is now merged but there are still related warnings showing up in some cases, e.g.:
See https://github.com/graalvm/mandrel/actions/runs/10985696189/job/30498692042 |
Hmm, this seems to be the intended warnings that need to happen after https://openjdk.org/jeps/472. I.e. the brotli library needs to have enabled native access configured or the coarse grain https://github.com/graalvm/mandrel/actions/runs/10985696189/job/30498692042#step:10:8773 |
The warning shows up in Quarkus integration tests as well so I believe this is something to be handled in Quarkus. |
It would be great if Quarkus could move to automatic modules. |
I'm closing this as it was originally about svm modules that produced warnings, which is gone. The brotli issue is tracked in: #284 |
After oracle/graal#9621, mandrel builds produce warnings due to some GraalVM enterprise modules which aren't there for mandrel. Example warning:
Seen in CI here:
https://github.com/graalvm/mandrel/actions/runs/10747037745/job/29809505730#step:11:12828
We'd need a patch in upstream GraalVM so as to not add those modules for Mandrel. Example patch:
jerboaa/graal@74a2e81
The text was updated successfully, but these errors were encountered: