Vendor | Use | Version | Dist | Status | IdentifierĪdoptOpenJDK | | 16.0.0.j9 | adpt | | 16.0.0.j9-adpt If you list the Java versions, you see this output: $ sdk list java I opted to focus my efforts on Java only. SDKMAN! uses different tools under the covers to do things like list versions, so my first attempt to make a universal sdk use function was going to get verbose, and I only ever switch among Java versions now. That’s OK - I have fzf! (That bang is my own.) Local-path : optional path to an existing local installationĮg: $ sdk install groovy 2.4.13-local /opt/groovy-2.4.13 Version : where optional, defaults to latest stable if not provided Use list command for comprehensive list of candidates When I run just the plain sdk command, I see it offers a completion command: $ sdkĬandidate : the SDK to install: groovy, scala, grails, gradle, kotlin, etc. I used SDKMAN! to install Coretto, both 8 and 16, but the syntax for switching is laborious: $ sdk use java 16.0.0.36.1-amzn I’ve been sleeping on Java, but it hasn’t conceded to JavaScript, Rust, or Go yet.

Our current NiFi installation runs on Java 8, so I’ve been swapping between Java 8 and the new hotness in Java 16, which I’m actually not saying ironically. I’ve been back in Java world lately for work, using Apache NiFi to create RDF Triples and push to Ontotext GraphDB.

Think nvm for Java, Maven, Groovy, et al. It’s a tool for managing versions of various Java-world tools. The bang in the subject belongs to SDKMAN!, not me.

Sdkman