You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#1962 was implemented for 21.3. Basic support for building images from modules is available. But more work is needed.
While all of the images coming from the substratevm suite (native-image-launcher, native-image-agent-library, ...) are already built on module-path our other GraalVM images from other suites are still built in the classpath. This needs to be fixed.
Currently the image builder only runs on the module-path if an image should be built from the module-path. This needs to changes so that the image-builder always runs on the module-path.
Module-info at image runtime is generated at image-buildtime. This is still incomplete. Hosted module access setup needs to be translated to runtime module-info access state so that module-related checks pass at image runtime as expected. One instance of this problem is explained in detail in [GR-34444] Ensure java.lang.Module#isReflectivelyExportedOrOpen works as expected #3911
#1962 was implemented for 21.3. Basic support for building images from modules is available. But more work is needed.
native-image-launcher
,native-image-agent-library
, ...) are already built on module-path our other GraalVM images from other suites are still built in the classpath. This needs to be fixed.StackTraceElement.getModuleName()
does not return module names. (see Show module name in stacktrace #4008)The text was updated successfully, but these errors were encountered: