Skip to content

Latest commit

 

History

History
101 lines (63 loc) · 4.16 KB

CHANGELOG.md

File metadata and controls

101 lines (63 loc) · 4.16 KB
Raw

Change Log

All notable changes to this project will be documented in this file.

[1.0.22-SNAPSHOT]

[1.0.21 - 2018-12-28]

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

[1.0.20]

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

[1.0.19]

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

[1.0.18]

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

[10.0.17]

  • Support for file:// based deployment

[10.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.

[1.0.15]

  • --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 especially usefull 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

[1.0.14] - 2016-10-26

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

[1.0.13] - 2016-09-12

  • 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

[1.0.12]

Changed

  • Added include-extensions parameter to CreateManifest. By default only jar and war files are included, add more extensions via this comma separated list.
  • 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

[1.0.11]

Changed

  • Progress window is now closed after primaryStage is shown instead of right before app.start() is called

[1.0.10] - 2016-05-07

Changed

  • Add optional --cache-dir program parameter cacheDir and manifest entry (#9)
  • Add / if missing from base url (#6)

[1.0.9] - 2016-03-14

Added

  • App manifest location can be given as command line parameter (#3)

[1.0.8] - 2016-03-02

Added

  • Support for manifest configurable parameters (#2)

[1.0.7] - 2016-02-20

Added

  • Support for platform specific resources

Changed

  • Parameters are now passed to the Application instance (#1)

[1.0.6] - 2016-02-10

  • First feature complete release