SDKMAN! is a tool for managing parallel versions of multiple Software Development Kits on most Unix based systems. It provides a convenient Command Line Interface (CLI) and API for installing, switching, removing and listing Candidates. Formerly known as GVM the Groovy enVironment Manager, it was inspired by the very useful RVM and rbenv tools, used at large by the Ruby community.
@sdkmanager you will be glad to know sdkman works on Bash on Ubuntu on Windows.
Is it possible to install jre6 using brew or sdkman? I tried: $ brew install jre6 Updating Homebrew. Error: No available formula with the name 'jre6' $ brew install java6 Searching taps. Searching taps on GitHub. Error: No formulae found in taps.
— Corneil (@corneil) July 23, 2016
New blog post: SDKMAN! The Software Development Kit Manager https://t.co/7VQBofse3l#blog@sdkman_
- Is it possible to install jre6 using brew or sdkman? I tried: $ brew install jre6 Updating Homebrew. Error: No available formula with the name 'jre6' $ brew install java6 Searching taps. Searching taps on GitHub. Error: No formulae found in taps.
- SDKMAN is an amazing project that makes it easy to manage multiple versions of Java and Scala on a single computer. It also provides support for other Java ecosystem projects like Maven, SBT, and Spark. SDKMAN stands for Software Development Kit MANager.
- For a quick and effortless start on Mac OSX, Linux or Cygwin, you can use SDKMAN! (The Software Development Kit Manager) to download and configure any Groovy version of your choice. Basic instructions can be found below.
This is amazing! Finally a usable way to manage JDKs. https://t.co/t0qex0tmmJ
— Mark Vieira (@mark_vieira) 19 December 2016There I did it! I ripped out all my old JDKs (including Java 7), and installed latest Java 8 via @sdkman_. So awesome!
— Greg L. Turnquist (@gregturn) 19 January 2017I always struggled with installing and managing my @java tools.
Now I found @sdkman_. Sooooo simple! I love it!
Kudos @sdkman_ team!
SDKMAN is an amazing project that makes it easy to manage multiple versions of Java and Scala on a single computer.
It also provides support for other Java ecosystem projects like Maven, SBT, and Spark.
SDKMAN stands for Software Development Kit MANager.
SDKMAN is the best Java version management solution because it works out of the box for a variety of different programs.
Install SDKMAN
Install SDKMAN with curl -s 'https://get.sdkman.io' | bash.
Run source '$HOME/.sdkman/bin/sdkman-init.sh' to load SDKMAN (this step is optional – you can also just close your Terminal and reopen it).
Run sdk version and make sure SDKMAN 5.9.1+575 is output to verify the installation was successful.
The installation script will append these lines to your ~/.zshrc file (you don’t need to add these lines – the installer will add them for you):
Run echo $PATH and see that .sdkman is prepended to the PATH as follows: /Users/powers/.sdkman/candidates/java/current/bin:/Users/powers/.pyenv/shims:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin.
SDKMAN uses the shim design pattern to intercept Java relevant commands and route them to the correct software versions. This design pattern is also used in other version management tools like rbenv (Ruby) and pyenv (Python).
Install Java
List the available Java versions with sdk list java:
Install Java 8 with sdk install java 8.0.272.hs-adpt. Here’s the terminal output when the installation is complete:
SDKMAN stores files it downloads in the /Users/powers/.sdkman directory.
Now install Java 11 with sdk install java 11.0.9.hs-adpt. Type sdk list java to show the Java versions that have been installed and the Java version that’s currently being used.
You can also see the Java version that’s being used by running sdk current:
Switch to Java 11 with sdk use java 11.0.9.hs-adpt. Run sdk current and confirm that Java 11 is being used.
The sdk use java command will only switch the Java version for the current shell. You’ll lose those settings when the shell is closed.
You can set a default Java version for whenever shells are started. Set SDKMAN to default to Java 8 with sdk default java 8.0.272.hs-adpt.
Close the shell, reopen it, and run sdk current java to confirm SDKMAN is using Java version 8.0.272.hs-adpt by default now.
You can also check the version by running java -version. You should see output like this:
JAVA_HOME
Lots of programs require the JAVA_HOME environment variable to be set.
Lucky for you, SDKMAN automatically sets the JAVA_HOME environment variable.
When you run echo $JAVA_HOME, you should see something like /Users/powers/.sdkman/candidates/java/current.
Install SBT
View the available SBT versions with sdk list sbt:
Install SBT 1.3.13 with sdk install sbt 1.3.13. After installing, respond with a “Y” to set 1.3.13 as your default SBT.
You can clone a SBT project and run the test suite if you’d like to verify that your SBT version was installed correctly. Here are the optional verification steps.
- Clone spark-daria with
git clone git@github.com:MrPowers/spark-daria.git cdinto the spark-daria directory- Run
sbt testand make sure the test suite finishes successfully
Install Scala
List the available Scala versions with sdk list scala:
Install Scala 2.11.12 with sdk install scala 2.11.12.
Type sdk use scala 2.11.12 to switch to the Scala version you just downloaded. Type scala in the Terminal and it’ll open up an interactive Scala REPL with Scala 2.11.12. Type :quit in the REPL to exit.
As you might have guessed, you can set a default Scala version with sdk default scala 2.11.12.
SDKMAN’s command line interface is consistent for all the SDKs. The commands to list, install, change, and set default versions follow the same syntax for each SDK. It’s easy to memorize the commands.
Install Spark
Run sdk list spark to see the versions of Spark you can download:
Run sdk install spark 2.4.7 to install the latest version of Spark 2.
Spark is a great example of a project that needs specific Java, Scala, and SBT versions to work properly. Spark 2 projects should be run with Java 8, Scala 2.11, and SBT 1.3 for example. Run sdk current to show all the current versions that SDKMAN is currently using.
This machine currently has the right dependencies setup for a Spark 2 project.
Run spark-shell to start a Spark REPL. You can see that it’s using the right versions:
Other supported SDKs
SDKMAN also supports a bunch of other SDKs.
It supports projects such as Maven, Groovy, Kotlin, Spring Boot, and more.
You can use the same syntax patterns we’ve seen in this blog post to install the SDKs, change versions, and set defaults.
SDKMAN has an elegant, consistent public interface and the commands are easy to remember.
Where SDKMAN stores packages
SDKMAN stores file in $HOME/.sdkman/candidates/.
To find where SBT 1.3.13 is installed, type sdk home sbt 1.3.13. It’ll return something like /Users/powers/.sdkman/candidates/sbt/1.3.13.
The arguments to the sdk install command align with where the files are stored in $HOME/.sdkman/candidates.
sdk install java 8.0.272.hs-adptstores files in$HOME/.sdkman/candidates/java/8.0.272.hs-adpt.sdk install sbt 1.3.13stores files in$HOME/.sdkman/candidates/sbt/1.3.13.
When you run sdk install, the downloaded binaries get saved in $HOME/.sdkman/archives. For example, $HOME/.sdkman/archives/java-8.0.272.hs-adpt.zip and $HOME/.sdkman/archives/sbt-1.3.13.zip.
Brew Android Sdkmanager
Some of the binaries are pretty big and can end up taking a lot of space on your computer. You should periodically delete them with the sdk flush archives command. Once you install the software, you don’t need the binaries anymore.
Other alternatives for managing Java / SDK versions
Brew Vs Sdkman
There are other ways to download and switch Java versions.
You can download Java versions with Homebrew and switch versions with jenv. This approach is a little harder because jenv is not as user friendly and the Homebrew commands to download Java tend to change. It’s easier to just use SDKMAN.
Jabba helps you download different version of Java and lets you switch between them, but it doesn’t provide access to any of the SDK versioning. You’ll rarely use Java in isolation and will often want to switch between versions for core libraries like SBT and Scala. SDKMAN saves you from reinventing the wheel by providing a single, consistent interface that works for a variety of different projects.
Jabba’s main advantage is that’s it’s cross platform (because it’s written in Go). Jabba provides a unified interface on Mac, Windows, and Linux. If you need a cross platform solution, go with Jabba.
Conclusion
Managing Java versions was painful for me until I started using SDKMAN.
I struggled with manual installations. The Homebrew downloads / jenv switching workflow helped, but didn’t solve versioning for SBT, Scala, or Spark. jenv is a great project, but it has some quirks that make it slightly more difficult to work with. Downloading Java versions via Homebrew is annoying because the commands change frequently so the Stackoverflow answers are often stale.
SDKMAN will let you manage multiple versions of Java and other core libraries on your machine with minimal hassle. Try it out and you’ll be sure to love it.