why javm
project jdk
javm exec ./gradlew build reads .java-version and runs the build with that JDK. No shell setup, so it works the same in CI, scripts, and IDE launchers.
native windows
Works in PowerShell and Command Prompt as well as Bash, Zsh, Fish, and Nushell. No WSL or Git Bash.
any distribution
Temurin, Zulu, Corretto, GraalVM, and every other distribution in the Foojay Disco API, selected by version or range such as ~21.0.2.
existing jdks
Finds JDKs installed by your system, IntelliJ IDEA, Gradle, or jabba, and javm link registers any other.
updates
javm update installs the newest build of each installed line and removes the old one unless something still selects it.
one binary
A single static binary with no JVM required. The installers check SHA-256 checksums, and build provenance can be verified. Apache-2.0 licensed.
questions
Does javm change my system Java?
No. javm use changes PATH and JAVA_HOME only in the current shell, and javm exec only for the command it runs. javm never edits system alternatives, the Windows registry, or shell profiles.
Does it switch automatically when I enter a project?
No. Run javm use or javm exec in the project; both read .java-version. See Switch Java versions.
Can I use it in CI?
Yes. Install a pinned release, run javm install, and run builds with javm exec. Exit codes are stable. See Use javm in CI.
I use jabba. Can I switch?
javm is a maintained fork of jabba and finds the JDKs jabba installed. See Migrate from jabba.
Is it stable?
javm is before 1.0: commands and configuration may still change between minor versions. Pin a release tag for reproducible setups; see Releases & Verification.
Is piping the installer into a shell safe?
The installers verify the SHA-256 checksum of the release archive before extracting it, and can also verify its build provenance. You can read them first or download a release archive yourself; see Installation verification.