Jabba

Jabba is a free, open-source Java version manager for developers who install JDKs and work across projects with different Java requirements. Its command-line approach combines a broad range of JDK sources with project-level version selection, though global Java switching takes manual setup.

Overview

Inspired by nvm and written in Go, Jabba aims to provide one way to install and switch JDK versions on Linux, macOS, and Windows. It supports both managed downloads and links to an existing system JDK, which is useful when a project needs a particular vendor or release without replacing the Java installation already on the machine.

There is a meaningful maintenance caveat: Jabba is a community fork described as a work in progress, and some README instructions may be outdated. The project is Apache-2.0 licensed and carries an educational-purpose, use-at-your-own-risk disclaimer. GitHub reports no SECURITY.md policy and no published security advisories; organizations that require a formal security policy should account for that before adopting it.

Key features

JDK catalog and custom downloads

Jabba’s JDK index is powered by DiscoAPI and filters its catalog for the user’s operating system and architecture. Supported distributions include Oracle, Adopt OpenJDK, Zulu, IBM SDK, GraalVM, OpenJDK, Liberica, and Amazon Corretto. Users can also install from custom URLs in formats such as zip, tgz, tgx, dmg, bin, and exe. This range suits developers who need to match a project’s vendor or use a distribution outside the standard index, though the work-in-progress status makes the README’s instructions worth checking carefully.

Version selection and project configuration

Users can browse remote JDKs, filter versions with semantic version ranges, install releases, and switch among installed versions. A default alias sets the version for new terminals, while a .jabbarc file lets a project specify its JDK. That project pinning is useful for keeping a project’s Java choice explicit across a team; Jabba does not provide automatic switching, so selecting the project version is not a hands-off transition.

Shell integration and deployment

The README documents integration with bash, zsh, and fish, alongside installation instructions for macOS, Linux, and Windows using Homebrew, shell scripts, PowerShell, Scoop, or Docker. The jabba-wrapper scripts let a project invoke Jabba without a global installation and select a version through .jabbarc. Docker examples install a JDK during a build and then remove the Jabba binary, a practical option for image construction.

Jabba does not include built-in global Java switching. The README instead provides manual, platform-specific snippets, which makes it a weaker fit for people who want a single tool to change the system-wide Java setting. Its files are stored under ~/.jabba on Linux and macOS and %USERPROFILE%/.jabba on Windows.

Pricing

Jabba is free: the Jabba plan costs nothing and is Apache License 2.0 software. There are no paid tiers to compare; the trade-off is that users take on the project’s work-in-progress status and the need for manual global switching.

Platforms

Jabba supports Linux, macOS, and Windows. Shell integration is documented for bash, zsh, and fish, with installation paths that include command-line scripts and platform package managers.

Who it's for

Jabba is best suited to developers who manage JDK versions from a shell, need to pin Java per project, or work with multiple JDK vendors. It is less suitable for users who require automatic project switching, built-in global Java changes, or the reassurance of a project with a formal security policy.

Pros and cons

• Pros: A DiscoAPI-backed catalog and custom URL support cover a broad range of JDK distributions and formats.
• Pros: Project-level version selection, a default alias, and wrapper scripts support separate Java requirements without requiring a global Jabba installation.
• Pros: Linux, macOS, and Windows support makes it usable across common desktop development environments.
• Cons: Global Java switching requires manual platform-specific setup rather than a built-in command.
• Cons: The project warns that it is a work in progress and that some README instructions may be outdated.
• Cons: No SECURITY.md policy or published security advisories are reported, a concern for teams with formal security requirements.

Alternatives

For a tool focused on a different language or toolchain, consider GHCup for Haskell, rustup for Rust, or elan for Lean. fnm and nvm are free Node.js version-manager options. mise is a free, MIT-licensed option for macOS, Linux, and Windows; asdf is a free, open-source tool version manager for Linux and macOS. axe-playwright is a free option for Linux and web, with Playwright as a peer dependency.

Browse more options in Runtime Version Managers or Development Environment Managers.

Verdict

Choose Jabba if you want a free, cross-platform way to manage JDK installations and select Java per project, especially across multiple distributions. Look elsewhere if you need automatic switching, built-in global Java changes, or a project with a more established maintenance and security posture.