FXLauncher 1.0.21

• Correctly resolve cacheDir (#131)
• Support for UNC Paths for app uri (#143)

FXLauncher 1.0.20

• Include artifact classifiers when copying dependencies
• What's New now expects fully qualified URL (#125)

FXLauncher 1.0.19

• Renamed --stopOnUpdateErrors to --stop-on-update-errors to bring it in line with the other parameters

FXLauncher 1.0.18

Support for launching non-JavaFX applications (Added for Spring Boot)

FXLauncher 1.0.17

This release sports a single feature: Support for file:// based deployment

It means that you can configure your app uri to be file:// based, which would use file system operations to sync instead of http. This is neat for applications deployed in company wide networks where you have access to a common file share instead of an http server.

FXLauncher 1.0.16

• Library function: Launcher.checkForUpdate(). Call at runtime from your app to check for new version.
• Library function: CreateManifest.create. Used by the build plugins to generate manifest in-process.

FXLauncher 1.0.15

This is probably the most feature packed release ever! Many small improvements and some big new features like the headless mode and whats new screen. Enjoy!

• --lingering-update-screen will keep the update screen active until the primary stage is shown. The default is false, whereas the old behavior was similar to setting it to true.
• Alternative classloader strategy (#55)
• USERLIB Now resolves to user.home/AppData/Local on Windows (#52)
• --ignoressl commandline argument to the fxlauncher.jar will ignore ssl certificate errors. This is especially useful when running in a business environment with for example
  the blue coat proxy that uses a man in the middle attack to sniff on https connections.
• whatsnew option is available, see README.md how to use it.
• App URI can now be any kind of URI, for example file://
• log statements get logged to TEMPDIR/fxlauncher.log. TEMPDIR is OS specific. The Error dialog will show you where it
  expects to find it. Logfile location can be overwritten with the --logfile=filename command line option.
• --offline flag added. when used on the command line the files will not be checked or downloaded from the remote.
• --stopOnUpdateErrors added. This will stop the fxlauncher from trying to start the application when there were errors updating the jars from the remote

FXLauncher 1.0.14

This is a bugfix release to address the following issues.

• include-extensions was consulted too early, leaving the matched files out of the manifest
• Basic Authentication only worked for manifest, not for the artifacts

FXLauncher 1.0.13

• Support for fully customizable update UI, see (https://github.com/edvin/fxlauncher-custom-ui)
• Basic Authentication support for manifest url (via https://user:pass@host/path)
• Added --include-extensions as a comma separated list of filename extensions to include of other resources from the build dir. By default it always includes jar,war.
• Fixed bug: If updating from a manifest with no timestamp (pre 1.0.11), new version was considered older, so no upgrade was performed

FXLauncher 1.0.12

• Added --accept-downgrade=<true|false> parameter to CreateManifest. Default is to not accept downgrades (server version is older than local version)
• Artifacts in subfolders gets correct path delimiter in app manifest for Windows