Docs menu

Runtime versions

How Primcloud selects an OpenJDK version for your Java app, how to pin one via system.properties, and how to upgrade.

On this page

Primcloud installs OpenJDK, as Azul Zulu builds. The versions you can install are part of the Primcloud Runtime, including the recent LTS releases 17, 21, and 25. You choose one with a system.properties file, and each deployment's build log shows the exact version it installed.

Pinning a version#

Add a system.properties file at the repo root and set the java.runtime.version key:

system.properties
java.runtime.version=21

The value accepts several shapes:

  • Major only: 21 installs the latest patch of that major.
  • Full version: 21.0.4 for OpenJDK 9 and up, or the legacy 1.8.0_x scheme for OpenJDK 8.
  • Distribution-qualified: a zulu- prefix (for example zulu-21) is accepted, though not required.

Give the major alone unless you need an exact release, so every build gets the newest patch.

No system.properties: you get the latest LTS, which moves forward when a new LTS arrives.

Upgrading#

Change the version, commit, and push:

  • Major upgrade: edit java.runtime.version in system.properties (say 17 to 21), commit, and push.
  • Patch upgrade: drop any exact-patch pin (or bump it), commit, and push. Primcloud picks up the newest patch of the requested major on the next build.

The first build on a new major takes a little longer while it's downloaded.

Before jumping majors, review Oracle's migration guide for the version you're moving to. A JDK bump can break your build or your runtime code, and nothing stops you from installing one that does.

End-of-life versions#

When an OpenJDK major reaches end-of-life, it's eventually removed from the Primcloud Runtime. Until then, builds on it keep working. Once it's removed, builds that pin it fail with "unsupported OpenJDK version". Move to a supported LTS before then to avoid an upgrade under pressure.