JEnv: A Next‑Gen Java Environment Manager that Simplifies Multi‑Version Management

Problem

Managing multiple JDK versions on a single machine is error‑prone and requires manual editing of environment variables.

Solution – JEnv

JEnv provides fast discovery, registration and switching of JDKs. A full five‑level scan of the C: drive completes in 400 ms , a 90 % speedup over typical 3‑second scans.

Technical core

Concurrent scanning engine : Implements a Dispatcher‑Worker model using Go goroutine s; concurrency scales with CPU core count.

Smart pre‑filtering : Skips system directories (Windows, System32), development artefacts ( node_modules, .git), cache/temp folders, and applies pattern‑based directory name recognition.

Depth control : Default scan depth is 5 levels, balancing coverage and performance.

Cache mechanism : Stores scan results for 5 minutes to avoid rescanning identical paths.

Cross‑platform support

Windows : Direct registry manipulation for system‑wide variables, minimal UAC prompts, symlink handling tuned for NTFS, and path verification for typical JDK install locations.

Linux : Works with bash, zsh, fish, etc.; supports user‑level configuration without root, optional system‑level configuration, and automatic privilege detection.

macOS : Under development to align with macOS directory layout and environment‑variable handling.

Terminal UI

Theme system : Default, dark and light themes with colour‑coded messages and status highlights.

Real‑time statistics : During a scan the tool displays scanned directories, skipped directories, discovered JDKs and an estimated remaining time.

Typical workflow

# Initialise JEnv
jenv init

# Add JEnv to PATH
jenv add-to-path

# Scan for JDKs
jenv scan /path/to/java

Common commands:

# List all registered JDKs
jenv list

# Switch to a specific version
jenv use java8

# Register a new JDK
jenv add java17 /opt/jdk-17

# Remove a JDK
jenv remove java8

Advanced features

Alias management for memorable JDK names.

Automatic detection of JDK installation directories.

Backup of environment‑variable state before modification.

Persistent configuration across restarts.

Architecture

Configuration management : JSON‑based config files.

Environment handling : Cross‑platform variable management.

Java management : Discovery, validation and lifecycle handling of JDKs.

System tools : Symlink creation, permission handling, etc.

Extensibility : Plugin interface and custom theme support.

User scenarios

Full‑stack developer adds three JDKs and switches per project directory:

jenv add legacy8 /usr/lib/jvm/java-8-openjdk
jenv add service11 /usr/lib/jvm/java-11-openjdk
jenv add modern17 /usr/lib/jvm/java-17-openjdk

# In each project directory
jenv use legacy8   # Java 8 project
jenv use service11 # Java 11 microservice
jenv use modern17 # Java 17 Spring Boot app

DevOps engineer configures CI/CD pipelines:

# Dockerfile
RUN jenv add ci-jdk /opt/jdk && jenv use ci-jdk

# Deployment script
jenv use production-jdk

Performance benchmarks

i7‑12700H + SSD, C: drive, depth 5 → 380 ms

i5‑10400 + HDD, C: drive, depth 5 → 420 ms

Ryzen 7 5800X + NVMe, C: drive, depth 5 → 350 ms

Old laptop i5‑8250U, C: drive, depth 5 → 450 ms

Installation

Option 1 – Download a pre‑built binary from GitHub Releases.

Option 2 – Build from source:

git clone https://github.com/WhyWhatHow/jenv.git
cd jenv/src
go build -o jenv

Quick start

Download and install the binary.

Run jenv init to initialise.

Execute jenv scan /path/to/java to discover JDKs.

Use jenv use <version> to switch.

Open‑source community

Contribute code via Pull Requests.

Report issues.

Suggest features or improve documentation.

Links

GitHub repository: https://github.com/WhyWhatHow/jenv.git