Comparison with SDKMAN!
Overview • Installation • Usage • Architecture • Enterprise • Locking • Networking • Shells • Threat Matrix • FAQ • SDKMAN! Comparison • Changelog • Security • Contributing • Support
SDKMAN! is the industry standard for managing Java versions and ecosystem tools. However, for native Windows users, it presents strict architectural challenges.
The Problem with SDKMAN! on Windows
SDKMAN! is a collection of POSIX-compliant Bash scripts. To run it on Windows, developers must install heavy compatibility layers like Windows Subsystem for Linux (WSL), MSYS2, or Git Bash. While this works well for Linux-first workflows, it causes severe friction for native Windows developers:
- IDE Disconnect: JDKs installed inside WSL are not easily accessible by native Windows IDEs (like IntelliJ or VS Code) without setting up complex remote-bridge configurations.
- I/O Performance: Crossing the OS boundary between WSL and the native Windows filesystem (
/mnt/c/) causes notoriously slow read/write speeds, increasing build times for Maven and Gradle. - Environment Variables: SDKMAN! updates
.bashrc, which Windowscmd.exeand background services completely ignore.
The Native Windows Alternative
This Java Version Manager (jvm.bat) solves this by operating directly on the Windows Registry, native NTFS Directory Junctions, and pure CMD/PowerShell environments.
| Feature | SDKMAN! (on Windows) | Java Version Manager (Native) |
|---|---|---|
| Runtime | Bash / curl / zip |
Native Batch / PowerShell / .NET |
| Dependencies | WSL, Cygwin, or Git Bash | None (Works out-of-the-box) |
| Supported Shells | Bash / Zsh only (inside compatibility layer) | CMD, Windows PowerShell, PS Core, Windows Terminal |
| I/O Speed | Slower (Virtualization boundary) | Maximum (Native NTFS) |
| Integration | .bash_profile / .zshrc |
Windows Registry (JAVA_HOME, PATH) |
| Switching Engine | POSIX Symlinks (requires Developer Mode) | Dual Engine: UAC-Free NTFS Junctions & Registry Mode |
| Switching Syntax | Verbose candidate slugs (sdk use java 21.0.2-tem) |
1-Word Shorthand (jvm 21, jvm lts, jvm latest) |
| Live Broadcasting | Shell-only (requires source or restart) |
Win32 WM_SETTINGCHANGE + Live In-Memory Hot Patch |
| IDE Support | Requires WSL bridges | 100% Native (IntelliJ, Eclipse, VS Code) |
| Windows Services & GUI | Inaccessible to Windows services | Full System Visibility (Jenkins, SonarQube, Task Scheduler, Start Menu) |
| Project File Support | .sdkmanrc only |
Dual Support: .java-version & Auto .sdkmanrc Translation |
| Local JDK Discovery | Cannot scan Windows folders | Automatic Local Discovery (scans Program Files for existing JDKs & JREs, tags [JRE]) |
| Standalone JRE Support | None (forces full JDK install) | Native JRE-Only Mode (--jre / --jdk) (standalone runtime lifecycle for Adoptium, Zulu, Liberica, Semeru) |
| Offline Operation & CAS Cache | Basic cache directory | Content-Addressed Storage (cache\sha256\), Portable Bundling (.jvmcache), & Zero-Ping Local Switching |
| Pre-Change Safety | None (overwrites shell files) | Automated Registry Backups (exports .reg to %LOCALAPPDATA%\DiamTek\JVM\backups\) |
| User Interface | CLI Only (Manual typing) | Interactive TUI & Headless CLI |
| Archive Extraction | Requires external zip / tar binaries |
Native .NET System.IO.Compression |
| Security & Error Hardening | Basic (curl downloads, silent script failures) |
329-Test Adversarial Suite (41 MITRE CWEs across 16 Suites), 10.0/10.0 Audit Scorecard, Atomic Rollback (PREV_JUNCTION_TARGET), & Deterministic Handle Lifecycle |
| Multi-Tool Environment Profiles | None (manual tool-by-tool switching) | jvm profile (Atomic multi-candidate switching, rollback on error CWE-460, and reparse point protection CWE-59) |
| State Snapshots & Rollback | None | jvm snapshot (Point-in-time state capture into JSON manifests, validated restore, and --dry-run simulation) |
| Portable Toolchain Bundles | None | jvm bundle (Standalone .jvmbundle archives with 0x50 0x4B magic bytes & ZipSlip CWE-22 containment) |
| Air-Gapped Toolchain Distros | Incompatible without internet | jvm distro & install.ps1 -Offline (Cryptographic standalone distributions with zero network calls CWE-319) |
| Provenance & Authenticity | None | jvm verify [ver|all] (6-tier cryptographic & signature audit) |
| Installation Atomicity | Basic unzips | jvm transaction (Atomic journaling & rollback engine) |
| CPU Architecture | Manual configuration | Native x64 / ARM64 Auto-Detection |
| Bulk Maintenance | Manual, tool-by-tool | 1-Click Bulk Updater (jvm update --all) |
| Self-Updater & Channels | Single-channel script pull (sdk selfupdate) |
Dual Channels ([Stable] / [Nightly]) with SHA-256 integrity, ahead-of-remote block & rate-limit fallback |
| Engine History & Rollback | None (manual re-install) | jvm self-update --history & --rollback (integrity-verified rollback engine) |
| OS Conflict Handling | Passive | Active Phantom-Path Scrubbing |
| Status & Binary Inspection | sdk current (POSIX shell string) |
jvm current & jvm which (Full status card + binary resolver) |
| Script-Friendly Single Values | None (verbose strings) | jvm current --short|--numeric|--bin & jvm vendor (zero-regex widgets for Starship, prompt statuslines, & CI) |
| Environment Resolution Explainer | None (guesswork) | jvm why (7-tier precedence decision tree tracing active runtime) |
| Candidate Deep Inspection | None | jvm explain <candidate> (7-layer identity, storage, junction, DACL, lock & CAS audit) |
| Contextual Build Runner | None (manual toggling) | jvm run <task> (automatic mvnw/gradlew detection & execution) |
| Toolchain Conflict Detection | None (silent build failures) | Proactive conflict scanner in jvm run (flags Gradle wrapper & Maven compiler target mismatches) |
| Sanitized Diagnostic Bundles | None (manual copy-paste) | jvm report, jvm doctor --report & jvm support (automated secret redaction & .zip bundles) |
| CAS Telemetry & Deduplication | sdk flush (basic temp deletion) |
jvm cache stats & jvm cache dedupe (SHA-256 CAS metrics & disk reclamation) |
| Cache & Slate Cleaning | sdk flush (basic temp deletion) |
jvm clean & jvm clear (Deep cache purge & registry slate wipe) |
| Ephemeral Subshell Runner | None (must switch shell and restore) | jvm exec <ver> [--] <cmd> / jvm run (zero global changes, accurate exit codes) |
| Diagnostic Health Audit | None | jvm doctor (7-point deep conflict, junction, & shadowing analysis with automated --fix self-healing) |
| Project Pinning CLI | Manual .sdkmanrc editing |
jvm pin [ver] / jvm local (instant lock writing & display) |
| Migration Muscle Memory | sdk use / sdk default |
jvm use / jvm default (1:1 transparent compatible aliases) |
| File Explorer Jump | Manual path navigation | jvm open [candidate] / jvm home (Instant GUI explorer jump) |
| Shell Wrapper Hook | Manual source line in .bashrc/.zshrc |
jvm hook (Automated install, status, and removal for PS 5.1 & PS 7+) |
| Enterprise Proxies | Manual http_proxy env exports |
Native Windows WinINet & Corporate Certificate Store |
| Windows Packaging | Unofficial / None | Winget, Scoop, Chocolatey, & Native MSI |
| Enterprise Privileges | Requires WSL/Bash setup | Zero-Admin / 0 UAC (Runs on locked-down corporate laptops) |
| Corporate Fleet Rollout | None (Manual shell curl) | Silent Intune, MECM & GPO MSI (msiexec /qn) |
| Uninstallation | Manual script deletion | Deep UAC Uninstaller & Windows Settings Integration |
Ecosystem Parity
You don’t need SDKMAN! just to get build tools and runtimes on Windows. DiamTek JVM features a built-in Universal Candidate Engine providing complete native ecosystem parity with SDKMAN!, downloading, verifying, and routing tools directly without Cygwin or WSL.
| Candidate | Display Name | Upstream Provider | Executable | Environment Variable |
|---|---|---|---|---|
java |
Java Development Kit | Multi-Vendor (12 Distributions) | java.exe |
JAVA_HOME |
maven |
Apache Maven | Apache Software Foundation | mvn.cmd |
MAVEN_HOME |
gradle |
Gradle | Gradle Inc. | gradle.bat |
GRADLE_HOME |
kotlin |
Kotlin Compiler | JetBrains | kotlinc.bat |
KOTLIN_HOME |
scala |
Scala | Scala Lang / EPFL | scala.bat |
SCALA_HOME |
groovy |
Apache Groovy | Apache Software Foundation | groovy.bat |
GROOVY_HOME |
ant |
Apache Ant | Apache Software Foundation | ant.bat |
ANT_HOME |
sbt |
Scala Build Tool | sbt / Lightbend | sbt.bat |
SBT_HOME |
jbang |
JBang | JBang Dev | jbang.cmd |
JBANG_HOME |
quarkus |
Quarkus CLI | Red Hat / Quarkus | quarkus.bat |
QUARKUS_HOME |
spring |
Spring Boot CLI | VMware Tanzu / Broadcom | spring.bat |
SPRING_HOME |
micronaut / mn |
Micronaut CLI | Micronaut Foundation | mn.bat |
MICRONAUT_HOME |
Cross-Platform Harmony (.sdkmanrc Hijacking)
The biggest hurdle for Windows developers is collaborating on repositories maintained by Mac/Linux developers who commit a .sdkmanrc file to the root of the project.
This tool completely eliminates that friction. It features a native .sdkmanrc parser that dynamically “hijacks” SDKMAN! workflows:
- When you run
jvmin a folder with a.sdkmanrcfile, it reads the exact versions requested by the Linux team. - It translates SDKMAN! vendor strings (e.g.,
17-tem,21-amzn,21-librca,21-sem,21-sapm,21-mandrel,21-dragonwell,21-kona) into their native Windows equivalents (Adoptium, Corretto, Liberica, Semeru, SapMachine, Mandrel, Dragonwell, Kona). - It instantly isolates the exact requested JDK, Maven, Gradle, Ant, sbt, JBang, Quarkus, Spring Boot, or Micronaut versions into your current terminal session.
You get 100% perfect environment synchronization with your Linux teammates, without ever installing a Linux subsystem on your Windows machine.
Ergonomic Switching (Shorthand vs Slugs)
In SDKMAN!, switching versions requires knowing and typing the exact candidate slug:
# SDKMAN! (POSIX syntax)
sdk use java 21.0.2-tem
sdk default java 17.0.10-amzn
If you forget the vendor suffix or patch release, you are forced to run sdk list java, search through hundreds of lines, and copy-paste the exact string.
DiamTek JVM provides 1-Word Shorthand Ergonomics alongside transparent SDKMAN! aliases:
# DiamTek JVM (Native Windows shorthand)
jvm 21
jvm lts
jvm latest
# SDKMAN! / NVM Migration Aliases (supported 1:1)
jvm use 21
jvm default 21
# Session-isolated switch (matching SDKMAN 'sdk use' semantics)
jvm use 21 --session
Note on
jvm usevsjvm default: In SDKMAN!,sdk useapplies strictly to the current shell whilesdk defaultchanges the global symlink. In DiamTek JVM, standard switches (jvm 21,jvm use 21,jvm default 21) switch the active JDK globally via the Directory Junction to match the Windowsnvm-windowsconvention. To get SDKMAN’s session-isolated behavior, simply pass--session(jvm use 21 --session).
JVM automatically inspects your installed versions and routes to the best installed candidate. If you have multiple distributions installed for the same major version (e.g., both Oracle JDK 21 and Eclipse Temurin 21), JVM pauses and displays an interactive prompt asking you to pick your preferred vendor—or you can override it directly via --vendor (e.g., jvm 21 --vendor adoptium).
Ephemeral Subshell Runner vs Manual SDK Toggling (jvm exec)
In SDKMAN!, running a one-off build or test against a different JDK requires switching your current shell (sdk use java 17...), executing the build, and then manually switching back (sdk use java 21...). If the build crashes or you forget to revert, your shell remains stuck on the wrong Java version.
DiamTek JVM provides native, one-line ephemeral execution:
# Runs in an ephemeral child subshell with zero global changes
jvm exec 17 -- mvn clean test
# Alias: jvm run 17 mvn clean test
- Zero Global Side Effects: Leaves your active Directory Junction (
current), global Windows Registry, and other terminal windows completely untouched. - Strict Exit Code Fidelity: Captures and propagates the child process’s exact exit code (
0or non-zero) back to the calling shell, ensuring CI/CD and automation runners fail accurately when builds break.
Proactive Health Audits vs Silent Breakages (jvm doctor)
Windows developers frequently face silent environment breaks caused by rogue MSI installers, broken directory junctions, or mismatched User/Machine registries. SDKMAN! has no diagnostic command to analyze underlying OS health or identify why a tool is malfunctioning.
DiamTek JVM includes jvm doctor—an automated 7-point health auditor:
jvm doctor
- Audits AppData local storage permissions.
- Verifies Directory Junction integrity and
bin\java.exetarget reachability. - Synchronizes User (
HKCU) and Machine (HKLM) registry states. - Scans
where.exe javafor legacy OraclejavapathandSystem32shadowing. - Verifies PowerShell
$PROFILEhook status. - Returns standard exit code
0on clean health or1on warnings, making it an ideal pre-flight check for enterprise deployment scripts.
Instant Project Pinning (jvm pin / jvm local)
In SDKMAN!, locking a project to a specific runtime requires manually writing or updating a .sdkmanrc file by hand.
DiamTek JVM provides dedicated CLI commands for project pinning:
# Lock project to JDK 21 (.java-version)
jvm pin 21
# Lock with vendor flags
jvm pin 21 --vendor adoptium
# Inspect active project pin
jvm pin
# Alias: jvm local
Whenever a developer runs jvm inside that directory, JVM automatically reads the .java-version file and locks the terminal session to that version without touching the global registry.
Direct Windows File Explorer Navigation (jvm open / jvm home)
Finding where a JDK or build tool is physically stored on disk in Windows usually requires traversing hidden AppData directories or system folders.
With DiamTek JVM, you can jump directly to any installed runtime or candidate folder in Windows File Explorer:
# Open active JDK directory in File Explorer
jvm open
# Open specific tool candidate folder
jvm open maven
jvm open gradle
# Open the JVM storage root
jvm open root
# Alias: jvm home
Automated Shell Hook Management (jvm hook vs POSIX source)
In SDKMAN!, integrating with developer shells requires manually maintaining a source "$HOME/.sdkman/bin/sdkman-init.sh" block inside .bashrc or .zshrc. If that initialization script becomes corrupted, debugging it requires manual text editing.
DiamTek JVM provides dedicated, one-command shell hook lifecycle management:
# Install or update the auto-sync wrapper hook in PowerShell profiles
jvm hook install
# Check hook status across Windows PowerShell 5.1 and PowerShell 7+
jvm hook status
# Cleanly remove the wrapper hook without touching other profile settings
jvm hook remove
- Automated Multi-Shell Discovery: Automatically detects and manages both Windows PowerShell (5.1) and modern PowerShell Core (7+) profiles across standard and OneDrive-redirected Documents folders.
- In-Memory Session Sync: Whenever you switch JDKs (
jvm 21), the hook dynamically updates$env:JAVA_HOMEand$env:Pathin-memory across the active shell session without restarting your terminal window.
Native Inspection & Binary Resolution (jvm current & jvm which)
When configuring Windows IDEs (IntelliJ IDEA, Eclipse, VS Code), native scripts, or CI/CD pipelines, you need to know where the actual Windows executable is located. Under WSL or Git Bash, which java returns a virtualized Linux path (/home/user/.sdkman/candidates/java/current/bin/java) that Windows applications cannot resolve without conversion bridges like wslpath -w.
DiamTek JVM provides native Windows inspection tools:
jvm current(orjvm status): Displays a comprehensive overview card detailing the active JDK version, vendor,JAVA_HOME, resolved executable, switching mode ([Symlink Mode]vs[Registry Mode]), junction link, and active ecosystem tools (Maven, Gradle, Kotlin, Scala, Groovy, Ant, sbt, JBang, Quarkus, Spring Boot, Micronaut).jvm which [candidate](orjvm path): Prints the absolute Windows filesystem path to the active binary directly tostdout. Works for Java (jvm which) and ecosystem build tools (jvm which maven,jvm which gradle). Ideal for automation scripts and IDE path configurations:# PowerShell automation $javaExe = (jvm which) & $javaExe -version
Dual Maintenance: Cache Pruning (jvm clean) vs Slate Reset (jvm clear)
Managing development environments requires both disk space hygiene and environment sanitization. In SDKMAN!, cache cleanup is limited to sdk flush, while de-activating an environment requires manually editing .bashrc and deleting symlinks.
DiamTek JVM cleanly decouples these two maintenance workflows:
jvm clean(Disk Cache Pruner): Safely sweeps%TEMP%and%LOCALAPPDATA%\DiamTek\JVMto purge orphaned.zipand.tar.gzdownloads, temporary extraction trees, and obsolete updater scripts. It calculates and reports the exact number of files deleted and megabytes reclaimed without touching active JDKs or settings.jvm clear(Environment Slate Wipe): Performs a deep system reset. It removesJAVA_HOME, scrubs rogue Oraclejavapathentries and broken junctions from both User and MachinePATH, and restores a clean baseline. To ensure complete safety,jvm clearautomatically exports a timestamped.regregistry backup to%LOCALAPPDATA%\DiamTek\JVM\backups\before executing.
Zero-Risk Backups & 100% Offline Execution
- Pre-Change Safety: Unlike POSIX shell scripts that directly overwrite
.bashrcor.zshrc, DiamTek JVM automatically creates a timestamped.regbackup in%LOCALAPPDATA%\DiamTek\JVM\backups\before making destructive registry modifications or clearing paths. If you ever need to roll back, simply double-click the.regfile to restore your previous environment state. - Zero-Ping Local Switching: SDKMAN! can occasionally lag or stall on poor network connections when running version queries against remote servers. DiamTek JVM executes local version switches 100% offline with zero network latency, making it completely reliable in air-gapped corporate environments, remote locations, and on planes.
Observability, Toolchain Automation & Diagnostic Telemetry vs SDKMAN!
Beyond candidate installation, DiamTek JVM provides systems engineering, observability, and toolchain automation capabilities with zero SDKMAN! equivalent:
- Deterministic Resolution Graph (
jvm why): In SDKMAN!, when an unexpected Java version runs, developers must guess whether.sdkmanrc, an active shell session, or a global default is responsible.jvm whytraverses a 7-tier precedence tree and prints the authoritative reason and location in plain text or--json. - Deep Candidate Auditing (
jvm explain <candidate>): While SDKMAN! only shows candidate paths,jvm explaininspects 7 operational layers: candidate identity, filesystem layout, NTFS junction status, environment variables, Windows DACL permissions (CWE-276), lockfile status, and Content-Addressed Storage (CAS) SHA-256 digests. - Proactive Toolchain Conflict Detection (
jvm run <task>): SDKMAN! leaves build tool execution to the developer, leading to cryptic build errors when a modern JDK runs against an obsolete Gradle wrapper.jvm runautomatically detects project build descriptors (mvnw,gradlew,pom.xml,build.gradle) and proactively warns developers if a Gradle wrapper (< 8.5on Java 21+,< 9.0on Java 25+) or Maven compiler target is mismatched with the active JDK. - Secret-Redacted Diagnostic Incident Bundles (
jvm report&jvm doctor --report): Troubleshooting on SDKMAN! requires manually copying terminal logs. DiamTek JVM generates sanitized diagnostic text reports (jvm report->jvm-report.txt) and comprehensive ZIP incident bundles (jvm doctor --report->jvm-issue-bundle.zip) with automatic redaction of usernames, tokens, and credentials (CWE-209/CWE-532). - Content-Addressed Storage Telemetry & Deduplication (
jvm cache stats&jvm cache dedupe): SDKMAN! only providessdk flushfor temporary folder clearing. DiamTek JVM indexes all downloads into a cryptographic CAS structure (cache\sha256\), tracks inventory footprint withjvm cache stats, and dedupes redundant candidate binaries viajvm cache dedupe. - Executable Version History & Integrity Rollback (
jvm self-update --history&--rollback): SDKMAN! only supports forward updates (sdk selfupdate). DiamTek JVM tracks an immutable history of previous engine builds and enables instant one-command rollback with fail-closed EOF marker verification (rem END OF SCRIPT).
Multi-Tool Profiles, Portable Bundles & Air-Gapped Distros vs SDKMAN!
While SDKMAN! requires switching candidates one-by-one or relying solely on directory-level .sdkmanrc files, DiamTek JVM introduces enterprise portability primitives:
- Named Environment Profiles (
jvm profile): SDKMAN! offers no concept of multi-tool named profiles. With DiamTek JVM, teams can define named environments (e.g.,jvm profile create legacy-fintech) that atomically switchJAVA_HOME,MAVEN_HOME,GRADLE_HOME, andKOTLIN_HOMEin a single command, with automatic rollback on error (CWE-460). - Toolchain Snapshots (
jvm snapshot): Point-in-time state capture allows developers to record their complete multi-tool environment configuration into portable JSON manifests and restore or preview them via--dry-run. - Portable Environment Bundles (
jvm bundle): SDKMAN! cannot export installed runtimes to another machine. DiamTek JVM bundles active tools and project lockfiles into.jvmbundlepackages hardened with0x50 0x4Bmagic byte checks and ZipSlip traversal prevention (CWE-22). - Zero-Network Air-Gapped Distros (
jvm distro&install.ps1 -Offline): In secure financial, defense, or air-gapped environments where developer workstations cannot query the public internet, DiamTek JVM builds complete offline distributions with SHA-256 manifests (distro-manifest.json) and pre-seeded CAS caches, allowing 100% offline installation without network requests (CWE-319).