This allows users to create a "Fat Jar" without loosing module information.
- Use the structure supported by: https://github.com/raphw/jenesis-launcher
- Configure
build.jenesis:build.jenesis.launcher as default launcher, but allow users to provide their own launcher code if it can work with the same structure
- Parallel to the
jpackage task, there should be one task per-target - libraries like JavaFX or LWJGL would require different native modules for different target platforms.
This allows users to create a "Fat Jar" without loosing module information.
build.jenesis:build.jenesis.launcheras default launcher, but allow users to provide their own launcher code if it can work with the same structurejpackagetask, there should be one task per-target - libraries like JavaFX or LWJGL would require different native modules for different target platforms.