jpackage current status
mik3hall at gmail.com
Mon Feb 24 22:24:10 UTC 2020
> now you can build runtime that has the tools like I do here:
>> $JDK_HOME/bin/jlink --bind-services --output mods.runtime --add-modules me.mymodule --module-path '../input-mods/mods'
> (../input-mods/mods has my app in me.mymodule)
> then in app you can find any of the tools by using System.getProperty("java.home") and looking in "bin" subdir.
> So in the app you can refer to any of the tools by their full path.
> My proposed addition of --jlink-options jpackage option would only make the first step unnecessary.
Seems like this would work if users were aware they needed to build the path. I could of sworn though that there were occasions where I successfully just created and copied in commands. I was wondering if there were some way in the native launcher to have the bin directory included in the paths searched by the launched java task. Maybe not. I just thought this used to work.
More information about the core-libs-dev