> On Jan 14, 2019, at 11:08 PM, Kustaa Nyholm <kustaa.nyh...@sparetimelabs.com>
> wrote:
>
>
> For reference and posterity in case anyone comes hear searching for a worked
> out sample here is my simplistic test script:
>
> #!/bin/bash
>
> set -e
>
> PACKAGER=/Library/Java/JavaVirtualMachines/jdk-13.jdk/Contents/Home/bin/jpackage
>
FWIW, for OS X I just set this in my .bash_profile
jdkhome=`/usr/libexec/java_home`
alias jpackage=${jdkhome}"/bin/jpackage"
alias jlink=${jdkhome}"/bin/jlink"
That way you aren’t dependent on a hard-coded jdk version name.
I think for some of what this does you need jlink as well and neither of these
commands (jpackage,jlink) appear to point anywhere after a drag and drop
install into JavaVirtualMachines.
jshell does seem correct and I think it was also introduced with jlink in java
9 so I’m not sure why both aren’t pointing correctly.
I think I asked about this before and it was indicated to be Apple who owned
the library holding the symbolic links for these commands and it was up to them
to have them pointing correctly?
