When there is a --files arg this works as expected, all jars are added
to the classpath in the config file.
When there is no --files arg, only the jar files at the top level of the
input dir are added to the classpath in the config file.
I filed bug JDK-8215900
<https://bugs.openjdk.java.net/browse/JDK-8215900> and will be fixing soon.
/Andy
On 12/19/2018 4:57 PM, Scott Palmer wrote:
If the main jar is in a subfolder the .cfg file is written incorrectly leading
to:
Error: Could not find or load main class <fully-qualified class name>
Caused by: java.lang.ClassNotFoundException: <fully-qualified class name>
Which I only found by manually running:
./MyApp.app/Contents/MacOS/MyApp
as double clicking doesn’t seem to show that output anywhere (I tried to find
it in the Console.app output, but didn’t).
In my case the main jar is in a ‘libs’ subfolder. The image is built
correctly, with the subfolder under the ‘Java’ folder in the Mac application
bundle. However, the cfg file had:
app.mainjar=MyMainJar-1.0.0.jar
instead of:
app.mainjar=libs/MyMainJar-1.0.0.jar
When I manually made that edit, it started to work.
Scott
On Dec 14, 2018, at 7:46 AM, Andy Herrick <andy.herr...@oracle.com> wrote:
I am pleased to announce that the first EA build of jpackage is now available
at : https://jdk.java.net/jpackage/
This is an early access build of JEP 343: Packaging Tool
<https://openjdk.java.net/jeps/343>, aimed at testing a prototype
implementation of jpackage,
This build is intended for developers interested in jpackage, and is provided as a convenience
so that they don't need to build from the source code
<https://hg.openjdk.java.net/jdk/sandbox> (branch="JDK-8200758-branch").
Warning: This build is based on an incomplete version of JDK 12
<https://openjdk.java.net/projects/jdk/12/>.
Please send feedback via e-mail to core-libs-dev@openjdk.java.net
/Andy
