-
Notifications
You must be signed in to change notification settings - Fork 37
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
Explicitly required module ALL-MODULE-PATH is not available #64
Comments
Hi, Thank you for reporting this, we'll take a look into it and get back to you |
Is it possible to provide a reproducer for this issue? |
Yes I will provide a reproducer that I can share. Just need some time to cleanup and push to my GitHub account. |
Instead of preparing the GitHub repo (need some time to get everything ready) I have attached the sample in the archive file. Without the option I also noticed that the classpath option is not working as expected.
=>
=>
The only option that works is to list every jar explicitly in the |
In the shared zip, I see 2 folders, one with generated config and the other with multiple jars. Could you please specify the steps to reproduce this issue? |
|
This should be fixed in the new 22.3.0 release, could you please test it and confirm? |
The error is gone, but the result is not the same as with running the native-image build using the classpath. Starting the application shows an exception. It doesn't seem to be really relevant, but it is different. See apache/felix-atomos#68
The classpath command that is working without issues is:
The application is a small Gogo Shell commandline application. You can for example enter BTW, I am running the build on Windows 10 for the verification. Just in case this makes a difference. I updated the commands to Linux style to make it easier for you to reproduce it. I also tried the following executions with the classpath option, that actually still don't work:
Shows the following error:
Shows the following error:
|
As this seems to be a different problem, can you please create a new issue for it? this is not directly related to container so the appropriate place should be https://github.com/oracle/graal/issues |
When trying to build a native image with graalvm-ce-java17-22.2.0 and the following options:
I get the following error:
Is the add-modules option not supported in native-image? Or is the option ALL_MODULE_PATH not supported?
The native-image help shows that the option as well as the value should be working.
The text was updated successfully, but these errors were encountered: