javafx-gradle-plugin 8.8.0

release of version 8.8.0

javafx-gradle-plugin 8.7.0

This is the 10th release !!!

I'm currently in a very good flow to push new features and bugfixes.

Not even two weeks after the last release some nice features and of course bugfixes are inside this new one. Thanks to all who reported bugs and who are asking me directly via e-mail. Keep on your good work ;) and use my gradle-plugin.

New:

• added checkForAbsolutePaths-property to enable absolute paths for all path-properties (it defaults to false to behave like before)
• added additionalBundlerResources for being able to have additional files available to the used bundler
• added feature for copying additionalAppResources to build/jfx/app when calling jfxJar and jfxRun, making it possible to have all that files available (like native files being required to not reside in the jar-files) by setting copyAdditionalAppResourcesToJar = true (issue #39)

Bugfixes:

• made it possible to specify absolute paths for all path-properties, fixes issue #36
• reverted the idea of registering the real tasks after project-evaluation, only add ant-javafx.jar after project-evaluation (fixes issue #31)
• adjusted CI-files for AppVeyor and TravisCI to handle functional tests
• fixed possible file-handler leak (unreported)

Changes:

• removed the skipDaemonModeCheck-property, please remove this from your configuration/buildscript

Enhancements:

• implemented some functional tests, mostly using the example-projects as test-projects (running against Gradle 2.10 and Gradle 3.0)
• added example project: windows installer with license
• added example project: debian installer with license
• added example project: adjusted launcher-icon
• added example project: additional bundler-files
• extracted plugin-version into separated file to have example-projects working at their place without having the need to adjust these version-numbers on every release
• refactored a bit to have cleaner code

javafx-gradle-plugin 8.6.0

This is a very special release, because it contains a workaround for a very nasty bug inside the JDK on Windows-systems when using DAEMON-mode. It was the very first time I had to do some JVM-bytecode analysis and using ASM for the first time for "hacking" something existing before using it. As Gradle 3 now uses daemon mode per default, it became mandatory to finally find some working fix for it ... but the real fix should come from Oracle, it even got reported by me, but as the javapackager is built with short-living JVMs, this will take its time to get fixed.

For further information about how this works, please take a look into the MonkeyPatcher-class.

Another thing to mention: this time an enhancement was implemented/integrated and released before the javafx-maven-plugin got it, namely the adjustments for the jfxRun-task, this does not mean that the javafx-maven-plugin gets less attention from me.

If something does NOT work with the new fixes, please report these as seperated issues.

Happy coding! eats-cake 🍰

New:

• added alternativePathToJarFile-property to specify the jar-file which gets used for javafx-jar-transformation
• added usePatchedJFXAntLib-property to disable gradle daemon workaround of the JDK-bug (which might be required when patching does result in crashing the JVM)
• added useEnvironmentRelativeExecutables-property to change the executables being used from the JDK instead of environment-relative (which could differ due to multiple local java-installations)
• added possibility to adjust java-command used for jfxRun-task: it is now possible to pass parameters to your jfx-application
• added possibility to adjust java-command used for jfxRun-task: it is now possible to pass parameters to the java-executable, e.g. to specify some javassist-module or other JVM-related stuff (like Xmx or other funny things)

Bugfixes:

• fixed issue #29 and #30 regarding stdout/stderr not printed when Gradle is in daemon mode (which is default for Gradle 3 now)
• fixed issue #12 regarding gradle daemon mode: IT IS NOW SUPPORTED

Changes:

• removed the usage of skipDaemonModeCheck-property, please remove this from your configuration/buildscript (will be removed in the next minor-release)
• the javafx-gradle-plugin now requires ASM being present on classpath of the buildscript for being able to work around the JDK-bug (https://bugs.openjdk.java.net/browse/JDK-8148717)

Enhancements:

• fixed issue #26 by providing a way to specify jar-file used for javapackager
• updated proguard example using new alternativePathToJarFile-property
• updated README.md to show minimal setup and other stuff

javafx-gradle-plugin 8.5.2

This is a quick fix for some stupid NullPointerException inside the nasty workaround I hat do introduce into the plugin.

Bugfixes:

• fixed issue #24 regarding NullPointerException inside workaround (I'm very sorry about that, thanks to @AustinShalit for finding this)

When ever you encouter problems while building on you system, please drop a line, if you are unsure about not being related, just drop me some lines via email.

javafx-gradle-plugin 8.5.1

This release took a bit too long, but it is finally here. Available via maven-central, might take some while that it is available (as always).

New:

• added new property to skip workaround for gradle daemon mode (which causes problems with the runtime-folder, see issue #12 for more information), this makes it now possible to create native builds within the IDE (at least once)

Bugfixes:

• fixed some classloader-problem when using javafx-gradle-plugin in combination with Netbeans IDE having netbeans-gradle-plugin installed (I'm very sorry about this, don't know why this wasn't detected by me before)
• updated workaround-detection for creating native bundles without JRE, because it got fixed by latest Oracle JDK 1.8.0u92

Enhancements:

• made it possible to specify file-association icon as String, File or Path
• changed the way for adding ant-javafx.jar to the classloaders (by using more stuff provided by the gradle-api)

Migrated from javafx-maven-plugin:

• (bugfix) added workaround for native linux launcher inside native linux installer bundle (DEB and RPM) not working, see issue #205 for more details on this (it's a come-back of the issue 124)
• (new) added ability to write and use custom bundlers! This makes it possible to customize the work which is required for your bundling-process.
• (new) added new property to disable "native linux launcher inside native linux installer"-fix skipNativeLauncherWorkaround205 = true
• (improvement) moved workarounds and workaround-detection into its own class (makes it a bit easier to concentrate on the main work inside JfxNativeTask)

Note:
There won't be any GString-support, please use toString() inside your buildscript

Another note: I know, dependency-filtering is not yet implemented, but as this is a rather unused feature, I will take the time ;)

javafx-gradle-plugin 8.4.1

This release contains only one bugfix, but it is important to make the whole thing work properly.

Bugfixes:

• copy dependencies with runtime-scope (fixes #15)

Thanks for using my javafx-gradle-plugin, only when used by more people we can find and fix all bugs.

Don't hesitate to report bugs, as this is the only way to discuss and find new ways for improvement. And of course to improve the experience with javaFX itself 😸

javafx-gradle-plugin 8.4.0

New version, new features, and something else is new too 😄

New:

• introduced jfxRun task
• introduced jfxGenerateKeyStore task
• 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

Improvement:

• added appveyor for building javafx-gradle-plugin on windows

Starting with this release I will keep the javafx-gradle-plugin and the javafx-maven-plugin in sync. This means, that you can compare the features of each plugin by comparing its major- and minor-version-number, I'm using semantic versioning v2.

Next thing will be to create some tests and example-projects.

javafx-gradle-plugin 1.3

After publishing a new version of the javafx-maven-plugin, I quickly integrated the new features and bugfixes into my gradle-plugin.

Bugfixes:

• replace backslash with normal slash within JNLP-files
• add signing-feature for bundler with ID "jnlp" (by setting "jnlp.allPermisions": true inside bundleArguments)
• fixed size-attributes within JNLP-files when using bundler with ID "jnlp" and requesting to sign the jars

Next versions will be in sync with the javafx-maven-plugin, mostly to have a better visual sign what feature-set exists. This means to me, that I still have to do some work ;)

javafx-gradle-plugin 1.2

New:

• added workaround for issue #12 regarding file descriptor leak inside the JDK starting from 1.8.0_60

As there seems to be no good way for having something like maven-invoker-plugin (which is used for the javafx-maven-plugin), I still need to find a nice way having buildable example-projects.

If there are some cool ways to have something similar like maven-invoker-plugin but for gradle, please contact me with working examples.

1.1

Short update

• support gradle daemon-mode (which is the default on most IDEs)
• support for multi-project projects

Known bugs

• on windows: when calling task jfxNative you can't call task clean, because there is a possible file descriptor leak (see issue #12 )