JavaFX Maven Plugin Files

This was a fast one! Not even a week has passed before a new version was able to be released!

This plugin was depending on some maven-plugins to call keytool and executing the generated jfx-jar, but that all got reworked by directly using ProcessBuilder. Removing the mojo-executor revealed some misconfiguration of our pom.xml, because we were dependent of transitive dependencies of that maven-plugin (which never is a good idea). There are some other improvements and changes which are listed below:

New: - when creating JNLP-files, your can now choose between Blob Signing (which was introduced since JavaFX but seems has never worked, and will be removed from Java 9) or normal signing done by jarsigner by providing the new property <noBlobSigning>true</noBlobSigning> - the run goal got its deprecation removed, you can call mvn jfx:run now again to start your application like you would start a normal executable-jar (no more calling java -jar yourProject-jfx.jar)

Improved: - removed org.twdata.maven:mojo-executor-dependency - fixed maven-plugin dependencies - generating keystore now directly uses keytool - changed appveyor to build/test using x86 and x64

All in all I get the feeling that some users don't report their found bugs, or JNLP isn't used very often when using the javafx-maven-plugin.

Using Gradle? Using Maven isn't what you need? You can start using the javafx-gradle-plugin which brings the same power from maven to gradle.