-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Introduce new JPMS exports to allow running native-image on module-path #25986
Conversation
@zakkak Could we move this out of draft now, please? It looks like our nightly mandrel builds are failing miserably because of oracle/graal#4468 See for example: |
@jerboaa this is not ready to be merged though. In the meantime for Mandrel's CI we can set |
Fair enough. As long as we keep a tracker with remaining issues and flip that once everything is fixed. |
Once oracle/graal#4468 gets merged, native-image will run on module-path requiring some additional exports to be passed to it in order to access internal APIs.
acd19ea
to
2e3fcf7
Compare
2e3fcf7
to
2e80961
Compare
Both issues are now tackled and this is now ready for review. |
This comment has been minimized.
This comment has been minimized.
quarkusio/quarkus#25986 allows Quarkus native to work with the image-builder running on module path. Reverts: oracle#388, oracle#390, oracle#391 Closes: oracle#389
quarkusio/quarkus#25986 allows Quarkus native to work with the image-builder running on module path. Reverts: #388, #390, #391 Closes: #389
PR quarkusio#25986 was mistakenly tested only with GraalVM set as `JAVA_HOME`. This resulted in Quarkus being able to properly figure the GraalVM version using `org.graalvm.home.Version#getCurrent`. This is not the case though when `JAVA_HOME` is set to point to a non-GraalVM JDK, since `org.graalvm.home.Version#getCurrent` always returns `snapshot` in that case which results in the JPMS exports being always passed to the `native-image` command. This results in warnings like the following when building with GraalVM 22.1 or earlier: ``` WARNING: Unknown module: org.graalvm.nativeimage.builder specified to --add-exports WARNING: Unknown module: org.graalvm.nativeimage.base specified to --add-exports WARNING: Unknown module: org.graalvm.nativeimage.builder specified to --add-exports ```
Once oracle/graal#4468 gets merged, native-image will run on module-path requiring some additional exports to be passed to it in order to access internal APIs.
Marking as Draft till I finish testing it with oracle/graal#4468