Getdown (yes, it's the funky stuff) is a system for deploying Java applications to end-user computers, as well as keeping those applications up to date.
It was designed as a replacement for Java Web Start due to limitations in Java Web Start's architecture which are outlined in the rationale section.
Note: Getdown was designed in 2004 as an alternative to Java Web Start, because of design choices made by JWS that were problematic to the use cases its authors had. It is not a drop-in replacement for JWS, aimed to help the developers left in the lurch by the deprecation of JWS in Java 9. It may still be a viable alternative for developers looking to replace JWS, but don't expect to find feature parity with JWS.
A tutorial and more detailed specification are available from the Documentation page.
Note that because one can not rely on users having a JRE installed, you must create a custom installer for each platform that you plan to support (Windows, macOS, Linux) that installs a JRE, the Getdown launcher jar file, a stub configuration file that identifies the URL at which your real app manifest is hosted, and whatever the appropiate "desktop integration" is that provides an icon the user can click on. We have some details on the installers documentation page, though it is unfortunately not very detailed.
The main design and operation of Getdown is detailed on the design page. You can also browse the javadoc documentation and source code if you're interested in implementation details.
Getdown was originally written by developers at OOO for the deployment of their Java-based massively multiplayer games.
Getdown is implemented in Java, and is designed to deploy and update JVM-based applications. While it would be technically feasible to use Getdown to deploy non-JVM-based applications, it is not currently supported and it is unlikely that the overhead of bundling a JVM just to run Getdown would be worth it if the JVM were not also being used to run the target application.
See CHANGELOG.md for release notes.
Getdown will likely need to be integrated into your build. We have separate instructions for build integration. You can also download the individual jar files from Maven Central if needed. Getdown is comprised of three Maven artifacts (jar files), though you probably only need the first one:
getdown-launcher contains code that you actually run to update and launch your app. It also contains the tools
needed to build a Getdown app distribution.
getdown-core contains the core logic for downloading, verifying, patching and launching an app as well as the core logic for creating an app distribution. It does not contain any user interface code. You would only use this artifact if you were planning to integrate Getdown directly into your app.
getdown-ant contains an Ant task for building a Getdown app distribution. See the build integration instructions for details.
You can also:
See this document on the changes needed to migrate from Getdown 1.8 to 2.0.
Getdown is built with Maven in the standard ways. Invoke the following commands, for fun and profit:
% mvn compile # builds the classes
% mvn test # builds and runs the unit tests
% mvn package # builds and creates jar file
% mvn install # builds, jars and installs in your local Maven repositoryFeel free to pop over in the GitHub project discussions to ask questions and get (and give) answers.