> On Feb 21, 2020, at 11:12 AM, Kevin Rushforth <kevin.rushfo...@oracle.com>
> wrote:
>
> I doubt this has anything to do with jpackage being in incubator or not.
> Fundamentally, just copying binary launchers into another JDK image like you
> are doing is only going to work by accident, if it works at all. If you need
> jpackage (or javac or jar or ...) to be in a JDK image, then you should jlink
> it yourself, include all of the modules you need, and don't strip the
> executables.
>
> -- Kevin
>
I was doing that for applications going back to before jlink - application
build tools have not handled this real consistently and often just strip.
Possibly now you are correct. jpackage does use jlink though? So why would my
own be better than what the tool does? I believe I showed the module is present
in the runtime in use.
But again doing jlink separately might in this instance be the best practice. I
will try it.
