Gradle tasks for downloading JREs, customizing them and publishing to the Terasology Artifactory. These customized JREs can be bundled along with the Terasology Launcher to distribute it as a self-contained package that can run the launcher and the game without requiring the user to manually install Java.
There are downloading and publishing tasks for each of the supported platforms. The platform names contain both the OS and its bitness:
For each of them we have the download task
downloadJreZZZ and publishing
ZZZ is the
target platform. To download or publish all the supported JREs, you can
publish tasks respectively.
Note that for publishing to our Artifactory,
you need to be authorized. You can create a
gradle.properties file in
the project root and store your credentials in this format:
# Terasology Artifactory credentials artifactoryUser = username artifactoryPass = password
Note: Git is configured to ignore this file.
Downloading 64-bit Linux JRE
- The downloaded
linux64.zipcan be found inside
Downloading all JREs
- All the JREs will be found inside
Note: No download task will overwrite the existing zip files.
Publishing Mac JRE to Artifactory
- The current version of JRE will be available here
Note: You need to set up
gradle.properties as described previously.
Publishing 64-bit Windows JRE to Maven local repository
- The current version of JRE will be available inside
The value of
m2_path depends on your OS:
A JRE cannot be published to the Artifactory if the same version of that
JRE already exists there. So the version needs to be incremented if this
repo gets updated. This can be done by updating the global
We are using BellSoft Liberica JRE
(version 8u212) as the source of the original JRE packages. To use a
different vendor, change the respective links in
build.gradle. Remember to update the global
group variable as it contains the vendor name at the end.