-
-
Notifications
You must be signed in to change notification settings - Fork 71
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
Don't specify jar or classpath #322
Comments
To be honest I don't know how to help you. I could ask directly on the Launch4j page |
Thanks, but I suspect it's just not possible. Looking through the |
Yet it's still worth mentioning such requirement, maybe it will be addressed in the future |
Entirely up to you if you want to ask. I can't stop you 😄 |
Could you write and link a minimum hello world app with the same structure as you need? I'd like to check something |
Hello!
I'm trying to package up a modular (in the Java 9 modules sense) command-line application. The application is run like this:
That is, the
lib
directory is set as the application's module path (not class path), and the-m
option specifies the main class within a module. Thelib
directory contains all of the jar files that make up the application, and those go onto the module path (and the class path is entirely empty).Unfortunately, if I put together a configuration like this:
I get the error:
It obviously expects me to be using a single executable jar, which I'm not. Is there some way I can trick
launch4j
into doing the right thing?The text was updated successfully, but these errors were encountered: