Skip to content
Branch: master
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
89 lines (56 sloc) 4.47 KB


Build Status Apache License Java-9+ Maven Release Gitter

Read the documentation, explore the JavaDoc, or see it in action

Auto-updater and launcher for your distributed applications. Built with Java 9's module system in mind.



Downloads 4 files then launches hello-world.jar. You can see that subsequent runs won't download again. headless


Downloads 4 files then launches hello-world.jar javafx


The update4j framework is the first auto-update and launcher framework completely compatible with Java 9 and up. Easily host your application files anywhere (even Google Drive, Dropbox, Amazon S3, or Maven Central) and you can synchronize them with all your distributed applications. You can use any protocol you wish to retrieve those files and may be protected under authenticated API.

In update4j you have ultimate control of every process, from startup - update - launch - shutdown; unlike other auto-update frameworks that yields over the control only once the business application was launched. In addition, every single piece of code is completely updatable; even the framework itself, once a new version is released!

Installation & Usage

You can download or install using Maven:


You can use it as a regular dependency, or you may run it as a runnable JAR file.

To run it in the modulepath, use either of:

$ java -p update4j-1.4.1.jar -m org.update4j
$ java -p . -m org.update4j

To run it in the classpath, use either of:

$ java -jar update4j-1.4.1.jar
$ java -cp * org.update4j.Bootstrap

For more information refer to Starting the Application in the wiki.

What's New in 1.4.x — Migration Guide

  • Added UpdateHandler.shouldCheckForUpdate(). Returning false will skip that file from being updated.
  • Pass arguments and system properties from the config when using the DefaultLauncher.
  • DefaultLauncher is now aware of JavaFX and will start javafx.application.Application even if missing a main method in class defined in default.launcher.main.class.
  • Reduced system dependencies to java.xml and added warnings if system module is not properly resolved. (breaking change in some cases).
  • Added dependency injection framework to communicate between the bootstrap and service provider.
  • Consequently, removed provider consumers at update and launch, and passing args at launch.
  • Removed many confusing getXxxProperty() methods in Configuration class.
  • You can now add properties to a config dynamically at runtime.
  • Locate explicit service providers even if not properly registered as required by ServiceLoader.
  • Made many service methods default.
  • Added osFromFilename() method in FileMetadata builder.
  • Changed how --delegate argument in Bootstrap works.


This project was highly influenced by edvin/fxlauncher. Thanks for the insights that made this possible.


This project is licensed under the Apache Software License 2.0

You can’t perform that action at this time.