Open msgilligan opened 4 years ago
I went ahead and merged in the logging... I've needed it as well. Long term, the jlink approach is desirable. I think that with now having access to Gradle actions, it will make jlink possible without having full access to all OS's
I went ahead and merged in the logging... I've needed it as well.
Yeah the silent failures in start()
are a PITA. There must be a more generic solution for that issue (maybe in some of the JavaFX frameworks?)
Long term, the jlink approach is desirable. I think that with now having access to Gradle actions, it will make jlink possible without having full access to all OS's
I think that is true for jlink
, but not for jpackage
. I've been using both mostly on the macOS platform and am just starting to branch out to Linux and Windows for my Bitcoin wallet application. I'll let you know as I learn more.
This uses the Badass JLink Gradle Plugin
What works:
To build the packaged app: ./gradlew build jgnash-fx:jpackage -x test
The packaged app will crash on start, needs more debugging
To run the modular app via Gradle:
./gradlew jgnash-fx:run
The app will start and display a window, but will crash on New or Open
Note: You’ll need the jpackage build from JDK 14 installed in the directory pointed to by the env variable
BADASS_JLINK_JPACKAGE_HOME