Debian/Ubuntu installer packages for Eclipse Adoptium

This uses the Eclipse Adoptium API to produce Ubuntu/Debian packages which download and install Eclipse Adoptium from their official releases.

• Ubuntu: ppa:rpardini/adoptium-installers or see instructions below.
• Debian: there's an APT repo hosted at GitHub Pages, see below for instructions.
• The Debian instructions also work for Ubuntu if you'd rather avoid PPA's.

Use these packages at your own risk. These are NOT official packages.

For Ubuntu:

[[ ! -f /usr/bin/add-apt-repository ]] && sudo apt-get -y install software-properties-common # Make sure 'add-apt-repository' is available
sudo add-apt-repository --yes ppa:rpardini/adoptium-installers
sudo apt-get install adoptium-17-installer # or 8, 11, etc; also adoptium-17-jdk-hotspot-installer-set-default

For Debian:

sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys A1EAC8B7 # add the builder key
echo 'deb https://rpardini.github.io/adoptium-deb-installer stable main' > /etc/apt/sources.list.d/rpardini-adoptium.list # add the package repo to sources 
sudo apt-get update # update from sources
sudo apt-get install adoptium-17-installer # or 8, 11, etc; also adoptium-17-jdk-hotspot-installer-set-default

For developers/builders

This repo produces source packages which are then uploaded to Launchpad, where they're built and hosted. The final packages produced are essentially just downloader scripts, and try to handle proxy usage, SHA256 verification, update-alternatives and update-java-alternatives as per java-common standards.

A huge amount of the actual installer scripting was stolen from Alin Andrei's webupd8 oracle-java8-installer -- all the update-alternatives, manpages, etc stuff is clearly in need of work. The proxy handling also needs to be confirmed; a few of his provisions like using a custom wgetrc was kept, but a lot of cosmetic stuff like icons were removed.

Due to the way Launchpad works, a big part of this is calculating a single set/version from many possible JDK builds for different architectures. It seems common that aarch64 and/or s390x archs have different Eclipse Adoptium builds than other architectures, at least for Java 8 and Java 11. Update: Adoptium does not suffer so much from those.

For this reason (and also cause I'm a bit of a codegen freak) I implemented a Node.js script that consumes Eclipse Adoptium's releases API and process sets of templates to produce final source packages.

Also due to Launchpad's requirements, I build a lot of (otherwise identical) source packages for different distributions/series (trusty, xenial, bionic, etc); please instruct me how to avoid this if you know.

Credits

• Of course, Eclipse Adoptium for all of the actual amazing work, and for the API.
• Alin Andrei/webupd8 for the original oracle-jdk8-installer from which I started this work
• Launchpad for actually building on many architectures and hosting the whole thing for Ubuntu
• GitHub for repo, Github Actions, and hosting the Debian repo with GitHub Pages. Please don't ban me.