jpackage custom resources not found

Andy Herrick andy.herrick at
Mon Jan 14 13:35:42 UTC 2019

I can see from the verbose message that you are not using the jpackage 
from the latest EA2 at

(run jpackage --version to see what version you are running)

Did you download the earlier EA and copy it over installed jdk-11.0.1 ?

In any case the behavior you are trying to use has changed twice (once 
from javafxpackager in JDK8 to jpackage in EA1 and again from EA1 to EA2).

With the current EA2, you need to add option "--resource-dir 

( or use a patch relative to the current directory) to say where to load 
custom resources from.

With the first EA you needed to put resources in "./package/macosx".  It 
was looking for custom resources in "package/<platform>" relative to the 
current working directory, not the input directory (as in javafxpackager)


On 1/14/2019 5:27 AM, Kustaa Nyholm wrote:
> Hi,
> over the weekend I tried to use the EA jpackage from here:
> I invoke it like this:
> PACKAGER=/Library/Java/JavaVirtualMachines/jdk-11.0.1.jdk/Contents/Home/bin/jpackager
> create-image \
> --build-root build-jpackager \
> --verbose \
> --echo-mode \
> --add-modules java.base,java.desktop \
> --input /Users/nyholku/EazyCNC-Project/javapackager-resources \
> --output . \
> --name EazyCNC \
> --main-jar EazyCNC.jar \
> --class eazycnc.Main \
> But I keep getting these messages:
> Using default package resource [icon]  (add package/macosx/EazyCNC.icns to the class path to customize)
> Preparing Info.plist: /Users/nyholku/EazyCNC-Project/./
> Using default package resource [Application Info.plist]  (add package/macosx/Info.plist to the class path to customize)
> Using default package resource [Java Runtime Info.plist]  (add package/macosx/Runtime-Info.plist to the class path to customize)
> even though the resources exist (and worked with JDK8 javapackager):
> ls /Users/nyholku/EazyCNC-Project/javapackager-resources/package/macosx/Info.plist
> /Users/nyholku/EazyCNC-Project/javapackager-resources/package/macosx/Info.plist
> wbr Kusti

More information about the core-libs-dev mailing list