jpackage custom resources not found

Rachel Greenham rachel at
Tue Jan 15 15:18:41 UTC 2019

surely simpler just unpack the jpackage jdk into, say, /opt/jdk-13, ie: 
emphatically *not* installed as a JVM in 
/Library/Java/JavaVirtualMachines, and then it doesn't get in the way of 
anything else. When you want to use jpackage invoke, directly, 
/opt/jdk-13/bin/jpackage, which is a path you can put in a convenient 
system variable perhaps, or symlink it into your path somewhere.


On 15/01/2019 12:09, Kustaa Nyholm wrote:
>> On 15 Jan 2019, at 12.57, Michael Hall <mik3hall at> wrote:
>> Usually the latest jdk with the command would be the one you’d want?
> Funnily enough, I wanted to quickly test something (jdeps) from the command line,
> and sure enough it evoked jdk-13 ea which is NOT what I want cause my main goal
> is to move all my stuff to jdk-11 and stay with that for next 5 years or so.
> For those who are not aware here is tip how to disable a jdk on MacOs:
> cd /Library/Java/JavaVirtualMachines/jdk-13.jdk/Contents/
> sudo mv Info.plist Info.plist-disabled
> i.e. just rename the Info.plist so that it cannot be found by the tools,
> after that command line tools reverted to jdk-11.0.1
> wrb Kusti

More information about the core-libs-dev mailing list