Jabba
github.com
- Free plan
- Windows
- macOS
- Linux
What Jabba is
Jabba is a free, open-source Java version manager written in Go for installing and switching between JDK versions on macOS, Linux, and Windows. Its JDK index uses DiscoAPI to list options for the user's operating system and architecture. The repository lists distributions including Oracle, Adopt OpenJDK, Zulu, IBM SDK, GraalVM, OpenJDK, Liberica, and Amazon Corretto. Users can browse remote versions, filter with semantic version ranges, install JDKs, and switch among installed versions. A `.jabbarc` file can set a project's JDK, and a default alias can choose the version for new terminals. Jabba can link an existing system JDK and coexist with another Java installation. The README documents shell integration for bash, zsh, and fish, plus installation through Homebrew, shell scripts, PowerShell, Scoop, and Docker. Custom JDK downloads can use formats including zip, tgz, dmg, bin, and exe. Jabba does not switch Java globally by itself; the README provides manual platform-specific snippets. The project describes itself as a community fork in progress and warns that some instructions may be outdated.
Who it suits
Jabba suits developers who need to install and select different JDK versions across macOS, Linux, or Windows. Its project configuration and shell integration can help teams keep a chosen JDK associated with a project.
Good to know, and what to watch
- Supports macOS, Linux, and Windows.
- Lists JDKs from multiple distributions.
- Project JDK selection uses `.jabbarc`.
- Shell integration covers bash, zsh, and fish.
- Apache License 2.0.
- Does not switch Java globally by itself.
- The project is a work in progress.
- Some README instructions may be outdated.
- The repository says use is at the user's own risk.
Plans
Every plan and priceJabba
Open source
Getting started
- Visit https://github.com/Jabba-Team/jabba.
- Choose an installation method documented in the README, such as Homebrew, shell scripts, PowerShell, Scoop, or Docker.
- Set up shell integration for bash, zsh, or fish if needed.
- List remote JDKs, filter for a version, and install it.
- Select a project version with `.jabbarc` or set a default alias for new terminals.
The Club's review
Jabba is a free, command-line manager for installing JDKs and choosing which version a project or terminal uses. It is best suited to developers working across Java projects on Linux, macOS, or Windows. Its broad distribution support and project-level selection are useful, while the work-in-progress status and manual global setup call for caution.
Overview
Inspired by nvm and written in Go, Jabba aims to give developers one way to manage JDK versions across three desktop operating systems. It can install JDKs or link one already on the system, making it practical for projects that need different releases or vendors without removing an existing Java installation.
Jabba is a community fork described as a work in progress, and its README warns that some 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 and no published security advisories, considerations for teams with formal security review requirements.
Key features
JDK catalog and custom sources
The DiscoAPI-powered index lists JDKs suited to 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 including zip, tgz, tgx, dmg, bin, and exe. This breadth is helpful when a team relies on a particular vendor, though it also puts the user in charge of choosing and maintaining the appropriate source.
Version selection
Users can browse remote JDKs, filter versions with semantic version ranges, install releases, and switch among those installed. A default alias chooses the version for new terminals. This gives command-line users a direct way to match their shell environment to a project's Java requirement, but it is not automatic switching.
Project configuration and wrappers
A project's .jabbarc file can specify its JDK version. The jabba-wrapper scripts let a project use Jabba without a global installation and select the configured version. This is a useful fit for repositories where contributors need a consistent Java release; teams still need to arrange for users to invoke the wrapper.
Shell and container use
The README documents integration with bash, zsh, and fish, plus installation through Homebrew, shell scripts, PowerShell, Scoop, and Docker-based use. Its Docker example installs a JDK during a build and then removes the Jabba binary, a focused option for image builds where the manager itself need not remain. Jabba stores its files under ~/.jabba on Linux and macOS, and %USERPROFILE%/.jabba on Windows.
Jabba does not provide built-in global Java switching. The README supplies manual platform-specific snippets, so users who expect the system-wide Java setting to follow their selected Jabba version will need extra configuration.
Pricing
Jabba is free: its plan costs nothing and the software is open source under Apache License 2.0. There are no paid tiers, seat charges, quotas, or trial terms to weigh. The free plan includes the version-management tool; its practical trade-off is that setup, shell integration, and any global Java configuration are left to the user.
Platforms
Jabba supports Linux, macOS, and Windows. Shell integration is documented for bash, zsh, and fish, with PowerShell also among the documented installation methods. That makes it relevant to individual developers and cross-platform teams, although each user must follow the appropriate setup for their operating system and shell.
Who it's for
Jabba suits developers who maintain several Java projects with different JDK requirements and are comfortable managing tools from a shell. Its vendor range, system-JDK linking, and per-project configuration are especially useful where projects need distinct Java distributions or releases. It is a weaker fit for users who want automatic project switching, built-in global Java changes, or a project presented as fully mature and maintained.
Pros and cons
Pros
- Runs across Linux, macOS, and Windows, so teams can use one JDK manager across those systems.
- Supports a wide selection of JDK distributions and custom download URLs, allowing projects to use vendor-specific builds.
- Project version pinning through .jabbarc and the wrapper scripts helps align a project's Java choice across contributors.
- Can link an existing system JDK, preserving an installation already in use.
- Free and Apache-2.0 licensed, with no paid plan to budget for.
Cons
- No automatic switching means users must select versions through Jabba or the project wrapper.
- Global Java switching requires manual, platform-specific configuration.
- The work-in-progress designation and warning about potentially outdated instructions make long-term maintenance less certain.
- No SECURITY.md policy or published advisories are reported, which may complicate adoption in organizations that require a formal security process.
Alternatives
For a different language or toolchain, these free version managers offer comparable cross-platform or focused options:
- nvm is a free, open-source Node.js version manager for Linux, macOS, self-hosted environments, and Windows; choose it for Node.js rather than JDK management.
- rustup is free and supports Linux, macOS, and Windows; it is the relevant alternative for Rust.
- GVM is a free Go version manager for Linux and macOS; choose it when Go is the toolchain to manage.
- plenv is a free Perl binary manager for Linux and macOS; it is aimed at Perl environments.
- chruby is free, MIT licensed, and supports Linux and macOS with bash or zsh; consider it for Ruby version management.
- GHCup is free and installs and manages the Haskell toolchain across Linux, macOS, self-hosted environments, web, and Windows; pick it for Haskell.
- elan is a free Lean version manager for Linux, macOS, and Windows; it serves Lean projects rather than Java.
- axe-playwright is free and supports Linux and web; its package metadata names Abhinaba Ghosh as author.
For broader comparisons, see Runtime Version Managers and Development Environment Managers.
Verdict
Choose Jabba if you need a free, cross-platform way to manage several JDK distributions and pin Java versions to projects. Its strongest case is the combination of vendor choice, existing-JDK support, and .jabbarc project selection. Look elsewhere if you need automatic switching, built-in global Java control, or a more settled maintenance posture.
The verdict
Jabba provides a cross-platform way to install and select JDK versions, including per-project selection through `.jabbarc`. Users should account for its work-in-progress status and the lack of built-in global Java switching.
Questions people ask
Is Jabba free and open source?
Yes. Jabba is free and licensed under Apache License 2.0.
Which operating systems does it support?
Jabba is intended for macOS, Linux, and Windows.
Can I choose a JDK version for a project?
Yes. A `.jabbarc` file can specify the version Jabba should use for a project.
Does Jabba switch Java globally?
No built-in global switching is included. The README provides manual platform-specific snippets.
Which JDK distributions does it support?
The README lists Oracle, Adopt OpenJDK, Zulu, IBM SDK, GraalVM, OpenJDK, Liberica, and Amazon Corretto, among others.
How can I install Jabba?
The README documents Homebrew, shell scripts, PowerShell, Scoop, and Docker-based installation or use.
What the maker publishes
- Custom downloads
- Jabba can install JDK distributions from custom URLs using formats including zip, tgz, tgx, dmg, bin, and exe. source
- Data location
- Jabba stores its files under ~/.jabba on Linux and macOS and %USERPROFILE%/.jabba on Windows. source
- Docker
- The README shows using Jabba in a Docker build to install a JDK and then remove the Jabba binary. source
- Existing JDKs
- Jabba can link a system JDK, and the README says it can coexist with an already installed Java version. source
- Global Java setting
- Jabba does not include built-in functionality to switch Java globally; the README gives manual platform-specific snippets instead. source
- Goal
- The project aims to provide a unified way to install and switch JDK versions across macOS, Linux, and Windows. source
- Index integration
- The JDK index is powered by DiscoAPI. source
- Install and switch JDKs
- Jabba is intended to install and switch between JDK versions across macOS, Linux, and Windows. source
- Install methods
- The README documents Homebrew, shell scripts, PowerShell, Scoop, and Docker-based installation or use. source
- JDK catalog
- Its JDK index is powered by DiscoAPI and lists JDKs for the user's OS and architecture. source
- JDK sources
- The README lists Oracle JDK, Adopt OpenJDK, Zulu OpenJDK, IBM SDK, GraalVM CE, OpenJDK, Liberica JDK, and Amazon Corretto among supported distributions. source
- License
- The repository is licensed under Apache License 2.0. source
- License and disclaimer
- The repository identifies the software as Apache-2.0 licensed and says it is for educational purposes and used at the user's own risk. source
- Platforms
- The README documents installation for macOS, Linux, and Windows 10, with OS and architecture support described as macOS, Linux x86/x86_64/ARMv7+, and Windows x86_64. source
- Project configuration
- A `.jabbarc` file can specify a JDK version for Jabba to use, and a default alias can select the version used in new terminals. source
- Project status
- The repository describes Jabba as a community fork that is a work in progress and warns that some README instructions may be outdated. source
- Project wrapper
- The jabba-wrapper scripts let a project use Jabba without installing it globally and select a JDK version through .jabbarc. source
- Purpose
- Jabba is a Java version manager inspired by nvm and written in Go. source
- Security
- GitHub reports that the project has no SECURITY.md policy and no published security advisories. source
- Shells and installation
- The README documents shell integration for bash, zsh, and fish, with installation instructions for macOS, Linux, and Windows. source
- Shell support
- The README gives shell integration instructions for bash, zsh, and fish. source
- Supported distributions
- The README lists Oracle, Adopt OpenJDK, Zulu, IBM SDK, GraalVM, OpenJDK, Liberica, and Amazon Corretto among supported JDKs. source
- Version selection
- Users can list remote JDKs, filter versions with semantic version ranges, install versions, and switch among installed versions. source
- Version switching
- Users can install JDKs, switch among installed versions, set a default version, and select a project version through a .jabbarc file. source
Checked against the maker's pages on 9 Oct 2026.