Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Main module of secondary launched not added #290

Open
HGuillemet opened this issue Jan 20, 2025 · 2 comments
Open

Main module of secondary launched not added #290

HGuillemet opened this issue Jan 20, 2025 · 2 comments
Assignees
@xzel23

Comments

@HGuillemet
Copy link

When configuring a secondary launcher, its moduleName is not listed in the --add-modules option of jlink, and jpackage fails with an exception like:

java.lang.RuntimeException: jdk.jpackage.internal.ConfigException: "Failed to find XXXX module in module path"

(unless the module of the secondary launcher is a module dependency of main launcher module).

Could you consider fixing that ?

Current workaround is to configure a customImage with an explicit list of appModules.
@xzel23
Copy link
Collaborator

xzel23 commented Jan 21, 2025

Hello @HGuillemet, I will look into this when I find the time. Need to create a simple reproducer first to add to the plugin tests.

@xzel23 xzel23 self-assigned this Jan 21, 2025
@HGuillemet
Copy link
Author

Here is a reproducer.

secondary-launcher-module.tgz

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@xzel23 xzel23

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@xzel23 @HGuillemet