Michael Bayne 4b739cd74f Nix the building of the getdown-tools.jar. We can just include everything in
getdown-pro.jar and it's only 10% larger (109k -> 121k), and it vastly
simplifies life for users.

Just use getdown-pro.jar for all of your Getdown-related needs:

- use it to install your application
- use it in your build scripts for the various Getdown tasks
- link against it in your app to use LaunchUtil or to embed Getdown

We'll even ship this on the website as simply getdown.jar. I'm tempted to ship
this in Maven and modify the main Getdown POM to not export any of its
dependencies. However, that will require a bunch of build file tweaking, which
I'd rather save for another day.
2011-06-22 00:52:56 +00:00
2010-01-04 21:47:35 +00:00

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 an application.

See the Google Code project for documentation and other information:

http://code.google.com/p/getdown

Building
--------

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
S
Description
Download, Install, Update
Readme 3.1 MiB
Languages
Java 90.7%
Shell 8%
JavaScript 1%
Go Template 0.3%