Jabba

Jabba is a free, cross-platform Java version manager for developers who need different JDKs across projects. Its wide distribution support and project-level version selection are useful; its work-in-progress status and manual global setup call for care.

Overview

Inspired by nvm and written in Go, Jabba brings JDK installation and version selection to Linux, macOS, and Windows. It can manage downloaded JDKs, switch among installed versions, or link a system JDK, so projects can use a chosen Java release without displacing an existing installation.

The project is a community fork that describes itself as a work in progress and cautions that some README instructions may be outdated. It is licensed under Apache-2.0 and carries an educational-purpose, use-at-your-own-risk disclaimer. GitHub reports no security policy file and no published security advisories, a consideration for teams that require formal security guidance.

Key features

JDK catalog and custom downloads

Jabba's DiscoAPI-powered index lists JDKs for the user's operating system and architecture. Named 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 breadth helps when a project depends on a particular vendor or packaging source, though it leaves users responsible for choosing the right build.

Version selection by terminal or project

Users can browse remote JDKs, filter versions with semantic version ranges, install them, and switch among installed versions. A default alias sets the version for new terminals, while a .jabbarc file selects a project version. The project wrapper scripts can let a project use Jabba without a global installation. These options make project-specific Java requirements manageable, but automatic switching is not supported: users need the documented shell integration and project setup.

Shells, existing JDKs, and containers

The README documents integration with bash, zsh, and fish, and installation through Homebrew, shell scripts, PowerShell, or Scoop. Jabba can link a system JDK and coexist with an existing Java installation. Docker instructions show installing a JDK during a build and then removing the Jabba binary, which suits image-building workflows where the manager need not remain in the finished image.

Jabba does not provide built-in global Java switching. Setting Java globally instead means following manual, platform-specific snippets, adding setup work for anyone who expects one command to change the system-wide version. Its files live under ~/.jabba on Linux and macOS, and %USERPROFILE%/.jabba on Windows.

Pricing

Jabba is open source and free: the Jabba plan costs nothing and is licensed under Apache License 2.0. There are no paid tiers, seat limits, quotas, or trial terms to weigh.

Platforms

Jabba supports Linux, macOS, and Windows. Its JDK catalog is tailored to the user's operating system and architecture, and installation guidance covers all three platforms. Shell integration is documented for bash, zsh, and fish; Windows users also have PowerShell and Scoop installation methods.

Who it's for

Jabba fits developers who work on Java projects with different JDK requirements, want to choose among several distributions, or need a shell-based manager across Linux, macOS, and Windows. It is also a practical candidate for Docker builds and for users who want to keep an existing system JDK while managing project versions separately.

Look elsewhere if you need automatic project switching, a built-in global Java switch, or a project whose documentation and maintenance status provide stronger assurances. Jabba's manual global setup and work-in-progress warning are material trade-offs, especially for teams with formal security requirements.

Pros and cons

• Broad JDK choice: The DiscoAPI index and custom URL support cover multiple named distributions and package formats.
• Project-specific versions: A .jabbarc file and wrapper scripts can tie a project to its intended JDK.
• Cross-platform workflow: Linux, macOS, and Windows support helps teams use one manager across operating systems.
• No automatic switching: Project selection depends on shell integration and setup rather than switching automatically.
• Global changes take manual work: Platform-specific snippets are required to change Java globally.
• Maintenance caveat: The community fork is a work in progress, and some README instructions may be outdated.

Alternatives

For toolchains beyond Java, Runtime Version Managers is a broader category to explore; for managing development environments, see Development Environment Managers.

GHCup is a free option for Haskell toolchain installation and management, while rustup is free and available across Linux, macOS, and Windows. fnm is another free, cross-platform version manager, and nvm is a free, open-source Node.js version manager. elan offers free Lean version management, and GVM provides free Go version management for Linux and macOS. mise is a free, MIT-licensed option for Linux, macOS, and Windows. axe-playwright is also free and supports Linux and web.

Verdict

Choose Jabba if you need a free, cross-platform way to manage multiple JDK distributions and assign versions to projects. Its catalog, existing-JDK support, and project configuration make it a useful fit for shell-oriented Java development. Look elsewhere if automatic switching, built-in global control, or a more assured maintenance posture is essential.