#Install4j not bundling jre download

It should not be taken down except for maintenance.

The host should be available as much as possible.

It would be great if we could get some metrics from GitHub to see how often the bundled JREs are downloaded so we can predict how much traffic we'll see.

Increased bandwidth possibly leading to an increased Linode bill.

The purpose of this issue is to discuss possibly moving the bundled JREs to one of our Linode servers and serve them from there using Nginx (or something equivalent). Even when we can remove an older bundled JRE from HEAD, it stays in the repo history unless we rewrite history.Ī static file server is probably a better place to host these resources rather than using a Git repo.

Adding additional JREs increases the size of the triplea-game/assets repo significantly.

#Install4j not bundling jre download

Adding additional JREs increases the time to run the Gradle build on Travis due to the additional download requirements.As long as those older builds are considered compatible, we have to keep multiple JRE versions on HEAD in the repo (we currently have two versions for three platforms). We can't just provide the 'latest' JRE because older installers are built with a hard-coded link to a specific path in the repo.There are a few problems hosting these files on GitHub:

We currently host these bundled JREs in the triplea-game/assets repo, and the installer downloads them, if needed, directly from GitHub. We bundle JREs with our installer for users that do not have a Java 8 JRE installed on their machine.