PROVIDER - SDK version management for the JVM

SDKMAN!

SDKMAN! manages more than 10 JVM tool families including JDK, Gradle, Maven and Kotlin from 1 command, with multi-vendor JDK support and .sdkmanrc pinning in a pure shell implementation; it is limited to the JVM, needs WSL on Windows and leaves commercial licences to you.

Developer Tools United States 2026.11.19
4pts

Detailed Notes

Pros 5 items

Manages more than 10 JVM tool families including JDK, Gradle, Maven, Kotlin and Scala from 1 command
Installs JDK distributions from several vendors across versions 8 through 23
Pins a project's SDK combination through 1 .sdkmanrc file
Switches versions with 1 command since PATH and JAVA_HOME are maintained automatically
Pure shell implementation with a roughly 100-line installer that is easy to audit

Cons 4 items

Limited to the JVM ecosystem, so non-JVM tools are out of scope
Depends on Bash, so Windows needs WSL or Git Bash
Community-maintained candidates mean some new releases appear late
Commercial JDK licences must be verified independently

Service Overview

SDKMAN! is the most popular SDK version manager in the JVM ecosystem. Implemented in shell, it installs and switches JDKs, build tools and JVM languages with one command, removing manual JAVA_HOME and PATH editing.

In the development tools category it is the ecosystem-specific version manager: scope is limited to the JVM world, but support for multi-vendor JDKs and build tools is unusually complete.

Key Strengths

  • Broad coverage: 10+ families from JDK to Kotlin
  • Many distributions: versions 8 through 23 across major vendors
  • Project pinning: .sdkmanrc travels with the repository
  • No manual setup: PATH and JAVA_HOME maintained for you
  • Auditable: a short, pure shell installer

Product Ecosystem

Platform capabilities

Candidate listing, version install and switch, default version setting, project version files, automatic environment variable management and update checks.

Integrations

Works with Gradle, Maven, IntelliJ IDEA, VS Code, GitHub Actions and container build flows.

Typical scenarios

Testing across JDK versions, experimenting with JVM languages and pinning Java versions in CI.

Limitations

  • JVM only: non-JVM tools are uncovered
  • Shell dependency: Windows requires WSL or Git Bash
  • Listing delays: community-maintained candidates lag occasionally
  • Licence review: commercial JDK terms remain your responsibility

Use Cases

  • Switching between JDKs (★★★★★): the core scenario, smooth in practice
  • JVM language experiments (★★★★☆): Kotlin and Scala managed together
  • Polyglot repositories (★★★☆☆): pair with asdf or mise
  • Pinned CI environments (★★★★☆): .sdkmanrc makes reproduction easy

Pricing

Item Price Notes
SDKMAN! itself $0 Apache 2.0 open source, commercial use allowed
Open source JDKs $0 Temurin, Zulu community and similar
Commercial JDKs Vendor licensing Verify terms independently

FAQ

How does SDKMAN! differ from setting JAVA_HOME manually?

SDKMAN! maintains PATH and JAVA_HOME automatically, so switching takes one command and environment mistakes disappear.

Is Windows supported?

Not natively; use WSL or Git Bash.

How do I lock versions per project?

Create and commit .sdkmanrc in the repository root, and teammates run sdk env.

Does it affect JDKs already installed on the system?

No, SDKMAN! installs under the user directory and injects variables through scripts.

Code Examples

# Install SDKMAN!
curl -s "https://get.sdkman.io" | bash

# List and install a Java version
sdk list java
sdk install java 21.0.2-tem
sdk default java 21.0.2-tem

# Pin SDK versions for a project
cat > .sdkmanrc <<'EOF'
java=21.0.2-tem
gradle=8.6
EOF
sdk env

Community & Resources

Visit SDKMAN! Website → https://sdkman.io/
Visit Website ↗