Module support for native-image building

[olpaw]

The native-image source base needs to be modularized similar to what already happened for other parts of our GraalVM stack. This will help to get rid of all the --add-exports that we currently need when we run the image builder on Java 11+.

Additionally we need support for specifying the application that we want to build an image from on the module path. I.e. we need to support native-image --module-path. Specifically we need

• -p <module path>
• --module-path <module path>...
• -m or --module <module>
• --add-opens & --add-exports

Adding support for 'native-image ' would also be nice to have.

[olpaw]

Being able to build Java 11 javac to a native-image is a good test-case for this issue.

[olpaw]

#2372 addresses the modularization of the image builder itself.

[joerg-wille]

In version 19.3 of GraalVM Native Image Java 11 support was added but without support for the Java Platform Module System (JPMS) and also no module introspection at image run time.

• Is this issue the correct one to track native-image JPMS support and especially module introspection at run time?
• Has anything changed on this topic in later releases of native-image?
• Is there work in progress on this topic or any estimation for full module introspection in native-image?

Thanks

[olpaw]

Hello @joerg-wille

adding module support to native-image is actively being worked on. This will allow to build images on the module path (e.g. native-image --module-path=module-foo.jar:module-bar.jar -m mymods.foo/qualified.name.MainClassInFoo and use --add-exports and --add-opens. Additionally we are working on making sure the moduleinfo seen at image runtime makes sense. E.g. if someone calls MainClassInFoo.class.getModule().getName(), "mymods.foo" would be returned as expected.

Currently the changes that enable this are only available when building GraalVM with a special environment variable USE_NATIVE_IMAGE_JAVA_PLATFORM_MODULE_SYSTEM=true. We also have some testing that gives an idea what already works (can be run with mx hellomodule from graal/substratevm).

While this will not be part of 21.2 we are working on getting this released as soon as possible.

[alina-yur]

@olpaw I guess we have an update here, right?:)

[olpaw]

@olpaw I guess we have an update here, right?:)

Correct.

While the feature is still experimental, as of GraalVM 21.3, images can be built from Java modules. I.e. now native-image also understands --module-path (-p), --module (-m), --add-exports and --add-opens.
We added a simple example for users to try out:
https://github.com/graalvm/graalvm-demos/tree/master/native-hello-module

As said, this is still experimental and we a look forward for feedback from early adopters.
Our main-branch is already a few steps further:

• Improved support for --add-exports and --add-opens
• Added support for --add-reads and --add-modules (WIP on [GR-31710] Support building js-launcher with image-builder on module-path. WIP #3748)
• More accurate module-info at image runtime (WIP on [GR-34108] Extend boot module layer to include required modules #3821)
  So if you run into problems with what we have in the release it would be a good idea to check if the problem might be already fixed on our main-branch.

[olpaw]

The follow up PR for future improvements is #3935