javafx-gradle-plugin | Gradle plugin that makes it easy to work with JavaFX | Plugin library

I created a java 10 project with intelliJ, using gradle. I copied some stuff into it (some "AppFx" class using the library guava and javaFx, and a personal build.gradle file). I also added a module-info.java file in src/main/java with this content:

I made an app with JavaFX and it worked correctly when I build the project with the build button on IntelliJ IDE. However it doesn't work when I run from jar file generated from gradle JavaFX project and the following error is shown on console.

I am making a skeletton of a java project; the gradle build file has an annoying problem : tests are ran twice, one time by the task 'JUnitPlatformTest' and a second time by the task 'test'.

The first one seems to trigger the second, so I can't disable it, and I would like to keep the second one as there is a little difference between them : the first one is in the console (of intelliJ) and the second uses the integrated intelliJ window.

here is gradle.build

I'm building a JavaFX application and I seem to be having trouble adding and using libraries like Gson or Apache Commons Lang. The libraries seem to add fine when referenced in my build.gradle and Intellij also shows they're in my project.. Gradle also seems to run clean and build with no problems. The problem occurs when I actually run the app and click the button that triggers the event sub-routine where the problem begins. I also get errors like this, no matter the library I try to reference:

I am packaging my app into exe with javafx-maven-plugin. x64 version works well. But then I package x86 version on 32-bit Windows 7 (running in VirtualBox if that's important) with 32-bit JDK 1.8.0_161 and 32-bit Maven. The resulting application installs, but fails to run, claiming that MSVCR100.dll is missing even though it is in the runtime\bin folder. I googled around and found out that this is a JDK bug that was supposedly fixed way back in u40. So why does this still happen? If I copy that dll manually next to the .exe it starts on one machine (again, in VirtualBox), but for some reason silently crashed on another (real one this time, fresh installation). Found an identical problem in javafx-gradle-plugin issues, though it got resolved when building on newest Win10 version, whereas I'm building on newest Win7.

If I just install Microsoft Visual C++ 2010 Redistributable Package then everything works, obviously, but I don't want user having to do that. So how do I copy .dll with Inno Setup script and how do I figure out the reason behind silent crashing?

I'm actually using javafxpackager through the JavaFX-Gradle-Plugin, but I can't figure out the solution in plain javafxpackager, so, that would help as well.

How do I sign an MSI using javafxpackager? How do I specify the cert/key/whatever is needed?

In its documentation:

• https://docs.oracle.com/javase/8/docs/technotes/tools/unix/javafxpackager.html
• https://docs.oracle.com/javase/9/tools/javapackager.htm

I can see the options for Mac OS, such as: mac.signing-key-developer-id-app=key but I don't see anything about signing the Windows MSI installer.

In this doc:

• https://docs.oracle.com/javafx/2/deployment/self-contained-packaging.htm

it acknowledges the need for signing it by saying:

If you plan to distribute your MSI package on the network, then consider signing it for the best user experience.

but there's no explanation on how to achieve this (compared to the Mac OS equivalent section).

I'm using the JavaFX packager through the JavaFX-Gradle-Plugin and I need to add a couple of Wix extension libraries to be able to run my app after install.

How do I achieve that?

According to the Wix documentation, by adding -ext WixUIExtension -ext WixUtilExtension to the command line, but I don't see how to do it from the JavaFX packager nor JavaFX-Gradle-Plugin.

AWT's TrayIcon class has a method called displayMessage that shows a native OS message that in Windows 10 looks like this:

when called like this:

I'm building a JavaFX application and using the JavaFX packaging tools by means of the JavaFX-Gradle-plugin. I'm generating various launchers with this configuration: