These tarballs are automatically generated from the OpenJDK repositories at Seeding the local copy with these tarballs is usually much faster than Mercurial transfer from US West coast, especially if you are in Europe, especially if you are checking out the large monorepo JDK 10+. Archive names are derived from the names of the tracked repositories.

Tarballs are updated at least weekly. Don't forget to "hg pull" to get the latest changesets after unpacking the tarball. By default, the archive contains only the Mercurial metadata, use "hg update" to materialize the working copy.

Example to checkout and build JDK 8u or derivatives:

$ curl | tar xJf -; \
  cd jdk8u-jdk8u; \
  hg pull; hg up; \
  sh common/bin/ pull; sh common/bin/ up; \
  sh ./configure --with-cacerts-file=/etc/ssl/certs/java/cacerts; \
  make images; \
  build/linux-x86_64-normal-server-release/images/j2sdk-image/bin/java -version

Example to checkout and build JDK 10+ or derivatives:

$ curl | tar xJf -; \
  cd jdk-jdk; \
  hg pull; hg up; \
  sh ./configure --with-cacerts-file=/etc/ssl/certs/java/cacerts; \
  make images; \
  build/linux-x86_64-normal-server-release/images/jdk/image/bin/java -version


File Name  ↓ File Size  ↓ Date  ↓ 
Parent directory/--
README.txt 10682018-Jan-19 11:52
aarch64-port-jdk8u-shenandoah.tar.xz 244M2018-May-25 10:50
aarch64-port-jdk8u.tar.xz 243M2018-May-25 10:45
amber-amber.tar.xz 745M2018-May-25 12:42
jdk-client.tar.xz 738M2018-May-25 12:13
jdk-jdk.tar.xz 743M2018-May-25 11:59
jdk-sandbox.tar.xz 748M2018-May-25 11:43
jdk-submit.tar.xz 745M2018-May-25 12:28
jdk-updates-jdk10u.tar.xz 714M2018-May-25 10:41
jdk-updates-jdk9u.tar.xz 399M2018-May-25 10:27
jdk8u-jdk8u-dev.tar.xz 232M2018-May-25 10:17
jdk8u-jdk8u.tar.xz 232M2018-May-25 10:21
shenandoah-jdk.tar.xz 727M2018-May-25 11:27
shenandoah-jdk10.tar.xz 715M2018-May-25 11:13
shenandoah-jdk8u.tar.xz 245M2018-May-25 10:54
shenandoah-jdk9.tar.xz 402M2018-May-25 11:01
valhalla-valhalla.tar.xz 739M2018-May-25 10:13
zgc-zgc.tar.xz 740M2018-May-25 12:57