shyiko/jabba

(cross-platform) Java Version Manager

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 28 minutes ago
Added to GitGenius on September 20th, 2026
Created on March 24th, 2016
Open Issues & Pull Requests: 149 (+0)
GitHub issues: Enabled
Number of forks: 224
Total Stargazers: 3,414 (+0)
Total Subscribers: 23 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 12
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,377 days
Stale 30+ days: 12
Stale 90+ days: 12

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Jabba is a cross-platform Java version manager that allows developers to install, switch between, and manage multiple Java distributions on a single machine.

The tool solves the problem of managing multiple Java versions when working on projects with different compatibility requirements. It works by downloading and installing specified Java distributions locally, then providing commands to switch the active version. This eliminates the friction of manually managing JAVA_HOME environment variables or maintaining separate Java installations across different projects.

Jabba suits developers and teams working with multiple Java projects simultaneously, particularly those using continuous integration pipelines where different jobs may require different Java versions. It is especially useful in polyglot development environments where Java coexists with other languages and tools. The tool is language-agnostic in its implementation, written in Go, which means it runs as a single compiled binary without requiring a runtime dependency.

The original repository is no longer maintained. The README explicitly directs users to an actively maintained fork that includes continued development, bug fixes, and community support. Anyone considering adoption should be aware of this status and should follow the actively maintained version instead of this repository.