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.
4pts
Detailed Notes
Pros 5 items
Cons 4 items
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
- Website: https://sdkman.io/
- Source repository: https://github.com/sdkman/sdkman-cli
- Usage guide: https://sdkman.io/usage
Articles
- 01 GitLab CI/CD Best Practices: From Beginner to Production-Grade Pipelines 07-18
- 02 Prometheus Monitoring System Setup: From Metric Collection to Alert Notifications 07-18
- 03 Ansible Automation Ops Guide: From Configuration Management to Application Deployment 07-18
- 04 Docker Beginner Tutorial: From Installation to Containerized Web Deployment 07-18
- 05 API Integration Guide: REST vs GraphQL Comparison and Selection 07-18
- 06 GitHub Actions CI/CD Tutorial: Automated Build, Test, and Deployment 07-18
- 07 Docker Compose Multi-Container Deployment: Building Complete Application Orchestration 07-18
- 08 Kubernetes Deployment Guide for Beginners: Building a K8s Cluster from Scratch 07-18
- 09 Best VS Code Extensions 2026: Boost Your Development Productivity 07-18
- 10 Frontend Toolchain 2026: Vite / Next.js / Tailwind CSS Ecosystem 07-18