* Run jlink manually (or scripted) to create the bundled runtime.
* Create launcher executables with packr[1].
* Create the installer using whatever tools people normally use for native applications. NSIS[2] and WiX[3] are widely used. (I haven't gotten to this step yet myself.)
[1] https://github.com/libgdx/packr
I believe it also has trouble with reflection involving class names that aren't effectively constant at compile-time. So with that and the other limitations, there's a whole lot you can't do. Hopefully they can resolve that.
Those are better served by a full JVM, optionally boiled down with jlink or with AOT compilation for faster startup, and the JEP that was mentioned upthread.
In .NET Native and Lisp for example, you need to list code that should be kept around and not removed by the linker.
It is not an easy problem to sort out in some kind of automatic way.
Can you give an example?