Downloads

Latest release

The ready-to-run bundle (JUICE, JAMS Launcher, model libraries and all dependencies included) is published on GitHub:

Unpack the archive and run juice.sh / juice.bat — no installation required.

Additional model libraries

The JAMS bundle above already includes the standard model components (J2K_base, J2K_ext, J2K_iso, J2Kg, Thornthwaite). The full set — including regional J2000 variants, isotope transport, DRYvER and more — is published separately from the jamsmodels repository:

Download latest jamsmodels release All releases

Unzip and copy the contents into the components folder of your JAMS installation (or the libs path configured in default.jap / the JUICE settings dialog).

System requirements

Building JAMS from source requires a JDK 17 or newer (Maven and all third-party dependencies are included via the Maven wrapper).
Running the pre-built bundle only requires a Java runtime, version 17 or newer. On macOS, use Java 24 or newer if you hit a rare accessibility-related crash (a JDK bug fixed in Java 24).

Building from source

Clone and build the JAMS framework:

git clone https://github.com/jamsframework/jams.git
cd jams
./mvnw install -pl jams-starter -am
cd jams-bin && ./juice.sh

This builds and starts the JAMS framework itself, without any model components. To build the model libraries (e.g. the J2K family), also clone and build jamsmodels:

git clone https://github.com/jamsframework/jamsmodels.git
cd jamsmodels
# drop jams-api-*.jar / jams-main-*.jar (from the JAMS build above, or
# from a release bundle's lib/ folder) into jams-libs/, then:
./install-jams-libs.sh            # or install-jams-libs.bat on Windows
./mvnw package                    # build all models
./mvnw package -pl J2K_base -am   # build a single model, e.g. J2K_base

The built model jars are collected in the components/ directory of the jamsmodels checkout. Add that directory to the libs property of JAMS (settings dialog in JUICE) and the models are ready to use.

Version history

Release notes for past versions are collected on the Changelog page. Notes for new releases are published directly on GitHub Releases.