Bump javafx-maven-plugin from 8.1.4 to 8.8.3

[dependabot-preview[bot]]

Bumps javafx-maven-plugin from 8.1.4 to 8.8.3.

Release notes

Sourced from javafx-maven-plugin's releases.

javafx-maven-plugin-8.8.0

This is kind of a big release, because it contains so much new stuff :) all just for you !!!

There are some changes, maybe you used the features, mostly one important is about the used properties. Please note that using maven-properties is not recommended, please use the tags inside the configuration-blocks as much as possible.

New:

• added detection of missing main class, wrong configuration now gets detected a bit earlier, to disable scanning, just set <skipMainClassScanning>true</skipMainClassScanning> (might cause the build-time to increase when enabled)
• nativeReleaseVersion will now get sanitized, anything than numbers and dots are removed, this ensures compatibility with the used bundler toolsets
• signing jars using jarsigner was introduced some time ago, but it was lacking some custom parameters, this is now fixed by having the new additionalJarsignerParameters-list while using native MOJO (fixes issue #260)
• generating a keystore has some hardcoded parameters (like keysize or used algorithm), but was missing support for additional parameters, this is now fixed by having the new additionalKeytoolParameters-list while using generate-key-store MOJO
• added ability to fail the build on errors while bundling, just set <failOnError>true</failOnError>
• when having not specified any bundler, it now is possible to remove that JNLP-warning regarding "No OutFile Specificed", which makes that bundler being skipped, just set <skipJNLP>true</skipJNLP> inside the <configuration>-block
• added property to skip nativeReleaseVersion rewriting, just set <skipNativeVersionNumberSanitizing>true</skipNativeVersionNumberSanitizing> inside the <configuration>-block
• added skipCopyingDependencies to make it possible to NOT copying dependencies, but they are added to the classpath inside the manifest like normal
• added <fixedManifestClasspath> for setting the classpath-entry inside the generated manifest-file in the main jfx-jar, this is already possible for secondary launchers by setting <classpath> within the configuration-block of the secondary launcher
• added <useLibFolderContentForManifestClasspath> for creating the manifest-entriy for the classpath, depending on the content of the lib-folder, makes it possible to have files not being inside dependencies being present there (which got copied beforehand)

Improvements:

• added warning when no classes were generated for -jfx.jar-generation, fixes issue #233 (no real FIX, as this is no real BUG ... IMHO)
• added warning about slow performance (even on SSD) when having ext4/btrfs filesystems using "deb"-bundler (fixes issue #41)
• added warning about missing "jnlp.outfile"-property inside bundleArguments when using JNLP-bundler (from issue #42)
• added ability to change name of the lib-folder by setting libFolderName

Changes:

• reimplemented <additionalBundlerResources>, now searching for folders with the name of the used bundler, makes it possible to adjust nearly all bundlers now
• all parameters are now accessible via jfx.-prefixed properties, please adjust your properties accordingly (I hope this does not break much for you)

javafx-maven-plugin-8.7.0

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 this maven-plugin.

New:

• added additionalBundlerResources for being able to have additional files available to the used bundler
• added feature for copying additionalAppResources to target/jfx/app when calling jfx:jar and jfx:run, 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</copyAdditionalAppResourcesToJar>

Bugfixes:

• fixed possible file-handler leak (unreported)

Improvements:

• refactored a bit to have cleaner code

javafx-maven-plugin-8.6.0

After three months without a new release, it feels refreshing to have some minor tweaks for you folks. Now all my "open" issues are down to non-critical bugs, it is time to take care of the website, which is heavily outdated ... the polymer-project got some nice mayor upgrade, so this in mind the next goal is to make you happy again.

New:

• added new property useEnvironmentRelativeExecutables to make sure having the correct executables used, required when having multiple installations of java, just set this to false for using the JDK used for executing maven (this got migrated from the javafx-gradle-plugin)
• added new property runAppParameter for specifying application parameters passed to the execution call java -jar while developing your application (this fixes #176, because that issue got valid as the mvn jfx:run goal is valid again after the removal of the exec-maven-plugin)
• added new property runJavaParameter for having additional settings passed to the execution call used for running your javafx-application, makes it possible to specify javassist-parameters now (and much more)

... (truncated)

Changelog

Sourced from javafx-maven-plugin's changelog.

Release Notes

Version 8.8.3 (09-feb-2017)

Bugfixes:

• fixed <launcherArguments> of secondary launchers not being set correctly (reported at the javafx-gradle-plugin)

Version 8.8.2 (09-feb-2017)

Bugfixes:

• fixed <nativeReleaseVersion> missing it's default-value (issue #275)

Version 8.8.1 (06-feb-2017)

Bugfixes:

• the new option <useLibFolderContentForManifestClasspath> did not calculate the paths correctly (issue #271)

Version 8.8.0 (05-feb-2017)

New:

• added detection of missing main class, wrong configuration now gets detected a bit earlier, to disable scanning, just set <skipMainClassScanning>true</skipMainClassScanning> (might cause the build-time to increase when enabled)
• nativeReleaseVersion will now get sanitized, anything than numbers and dots are removed, this ensures compatibility with the used bundler toolsets
• signing jars using jarsigner was introduced some time ago, but it was lacking some custom parameters, this is now fixed by having the new additionalJarsignerParameters-list while using native MOJO (fixes issue #260)
• generating a keystore has some hardcoded parameters (like keysize or used algorithm), but was missing support for additional parameters, this is now fixed by having the new additionalKeytoolParameters-list while using generate-key-store MOJO
• added ability to fail the build on errors while bundling, just set <failOnError>true</failOnError>
• when having not specified any bundler, it now is possible to remove that JNLP-warning regarding "No OutFile Specificed", which makes that bundler being skipped, just set <skipJNLP>true</skipJNLP> inside the <configuration>-block
• added property to skip nativeReleaseVersion rewriting, just set <skipNativeVersionNumberSanitizing>true</skipNativeVersionNumberSanitizing> inside the <configuration>-block
• added skipCopyingDependencies to make it possible to NOT copying dependencies, but they are added to the classpath inside the manifest like normal
• added <fixedManifestClasspath> for setting the classpath-entry inside the generated manifest-file in the main jfx-jar, this is already possible for secondary launchers by setting <classpath> within the configuration-block of the secondary launcher
• added <useLibFolderContentForManifestClasspath> for creating the manifest-entriy for the classpath, depending on the content of the lib-folder, makes it possible to have files not being inside dependencies being present there (which got copied beforehand)

Improvements:

• added warning when no classes were generated for -jfx.jar-generation, fixes issue #233 (no real FIX, as this is no real BUG ... IMHO)
• added warning about slow performance (even on SSD) when having ext4/btrfs filesystems using "deb"-bundler (fixes issue #41)
• added warning about missing "jnlp.outfile"-property inside bundleArguments when using JNLP-bundler (from issue #42)
• added ability to change name of the lib-folder by setting libFolderName

Changes:

• reimplemented <additionalBundlerResources>, now searching for folders with the name of the used bundler, makes it possible to adjust nearly all bundlers now
• all parameters are now accessible via jfx.-prefixed properties, please adjust your properties accordingly (I hope this does not break much for you)

Version 8.7.0 (09-Sept-2016)

New:

• added additionalBundlerResources for being able to have additional files available to the used bundler

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Note: This repo was added to Dependabot recently, so you'll receive a maximum of 5 PRs for your first few update runs. Once an update run creates fewer than 5 PRs we'll remove that limit.

You can always request more updates by clicking Bump now in your Dependabot dashboard.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot ignore this [patch|minor|major] version will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

Finally, you can contact us by mentioning @dependabot.