What is it?
Getdown (yes, it's the funky stuff) aims to provide a system for downloading and installing a collection of files on a user's machine and upgrading those files as needed. Though just any collection of files would do, Getdown is mainly intended for the distribution and maintenance of the collection of files that make up a Java application.
How do I use it?
How does it work?
Where can I see it in action?
Getdown was originally written by developers at OOO for the deployment of their Java-based massively multiplayer games. Try out any of the following games to see it in action:
Getdown is implemented in Java, but certainly can be used to deploy non-Java-based applications. Doing so would be a little crazy since you may have to install a JVM on the user's machine (if they don't already have one installed), which is a ~7MB download. This isn't so bad if you're already installing a Java application and must have a JVM, but it's a little crazy if the JVM is only used for your installer. It is probably possible to compile Getdown with GCJ, which would make Getdown a viable choice for non-Java applications.
See CHANGELOG.md for release notes.
The latest version of Getdown can be obtained thusly:
- Download the pre-built jar file from Maven Central: getdown-1.7.1.jar
- Obtain the jar artifact via Maven with the following identifier:
- Check out the code and build it yourself.
You can also:
JVM Version Requirements
- Getdown version 1.7.x requires Java 7 VM or newer.
- Getdown version 1.6.x requires Java 6 VM or newer.
- Getdown version 1.5 and earlier requires Java 5 VM or newer.
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 repository
Feel free to pop over to the OOO Libs Google Group to ask questions and get (and give) answers.