-
Notifications
You must be signed in to change notification settings - Fork 19
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
JPMS related VM configurations cannot be set #56
Comments
The following is the one of the exceptions that appears during the launch if the aforementioned options ain't set while starting the VM
|
Your args are added, but perhaps it's adding them in the wrong order. Can you share the command-line |
The following is an example of running the gradle daemon -
|
I just tried to publish a new version of the application with the following runtime arguments -
It still behaves the same. I also think the ordering is wrong. |
This is how I run the application from the executable jar without any problem:
|
I've just pushed out a new version that fixes this issue. I've tested it on your app. You don't need to republish, but you do need to download the installer again from the download page to get the change. |
@shannah Thanks a lot for your continuous support. I have tested it and it works like a charm 👍 |
With the introduction of jpms, new java options are introduced:
--add-exports
the package is exported, meaning all public types and members therein are accessible at compile and run time.--add-opens
the package is opened, meaning all types and members (not only public ones!) therein are accessible at run time.In https://www.jdeploy.com/~osgifx application, I need the following java options to be set as well to make it work:
These options are still not set while running the application by either double clicking on it or by running the executable directly from the command line.
The text was updated successfully, but these errors were encountered: