Why use SDKMAN and jenv? The whole idea of both is to simplify management, and SDKMAN's functionality is (mostly?) a superset of jenv's, so... why complicate things by using both?
I too had this quandary of loving the ease of use with jenv, but wanted sdkman for ease of installing multiple different jdk's, in addition to all the other supported tools, gradle, groovy, scala, etc.. I finally looked into the issue of switching environments easily and noticed the command 'sdk env'. From there I found this excellent write up on using it on blog.mrhaki.com
Why use SDKMAN and jenv? The whole idea of both is to simplify management, and SDKMAN's functionality is (mostly?) a superset of jenv's, so... why complicate things by using both?
Maybe one exists, but I haven't yet found a way to quickly and easily switch between Java versions with SDKMAN. With jenv, it's as easy as:
I too had this quandary of loving the ease of use with jenv, but wanted sdkman for ease of installing multiple different jdk's, in addition to all the other supported tools, gradle, groovy, scala, etc.. I finally looked into the issue of switching environments easily and noticed the command 'sdk env'. From there I found this excellent write up on using it on blog.mrhaki.com
Automatic Switching Of Java Versions With SDKMAN!