After some additional effort to figure this out, it turned out to be an easy fix. SDKman stores the JDKs in this folder:
C:\Users\yourUserName\.sdkman\candidates\java
When you issue the command
sdk default java 8.322.06.2-amzn
it copies the JDK from the java 8 folder
C:\Users\yourUserName\.sdkman\candidates\java\8.322.06.2-amzn
and pastes it into the current folder.
C:\Users\yourUserName\.sdkman\candidates\java\current
The idea is that you point your pc to the "current/" directory so that when you change java version with SDKman, the pc environment variable never needs to be updated.
But for the ide, instead of pointing it to the "current/" directory, you can point it directly to the JDK folder
C:\Users\yourUserName\.sdkman\candidates\java\8.322.06.2-amzn
You can specify the JDK for each project, P1 and P2, separately. So even if you change java version with SDKman, that only effects the "current/" directory, which the ides are no longer pointing at.
Since I did this, I dont have to change java version if I want to switch working on my java 8 project to working on my java 11 project. And that means I dont have to close my java 8 project to open my java 11 project. I can have them both open at the same time, and switch between them easily.
Answer from Steve T on Stack OverflowAfter some additional effort to figure this out, it turned out to be an easy fix. SDKman stores the JDKs in this folder:
C:\Users\yourUserName\.sdkman\candidates\java
When you issue the command
sdk default java 8.322.06.2-amzn
it copies the JDK from the java 8 folder
C:\Users\yourUserName\.sdkman\candidates\java\8.322.06.2-amzn
and pastes it into the current folder.
C:\Users\yourUserName\.sdkman\candidates\java\current
The idea is that you point your pc to the "current/" directory so that when you change java version with SDKman, the pc environment variable never needs to be updated.
But for the ide, instead of pointing it to the "current/" directory, you can point it directly to the JDK folder
C:\Users\yourUserName\.sdkman\candidates\java\8.322.06.2-amzn
You can specify the JDK for each project, P1 and P2, separately. So even if you change java version with SDKman, that only effects the "current/" directory, which the ides are no longer pointing at.
Since I did this, I dont have to change java version if I want to switch working on my java 8 project to working on my java 11 project. And that means I dont have to close my java 8 project to open my java 11 project. I can have them both open at the same time, and switch between them easily.
Inside IntelliJ versus outside IntelliJ
- For running a project from within IntelliJ, you specify which JDK to use by configuring within IntelliJ.
- The current default JDK set by SDKMAN! only applies to Java apps being executed on their own, outside IntelliJ.
Unfortunately, configuring which JDK to run your app within IntelliJ is complicated and confusing, requiring you to go spelunking through various buried panels.
These panels include some for the JDK, and some for the language level (which version of Java to target):
- File | Project Structure | Project Settings | Project | SDK … and Language Level.
- File | Project Structure | Project Settings | Project | Modules | Language Level.
- Settings | Build, Execution, Deployment | Compiler | Java Compiler | Per-module bytecode version.
There may be others I don't recall at the moment. Search Stack Overflow to learn more.
If you are building a Web app in IntelliJ Ultimate edition, and running that app from within IntelliJ via an external application server such as Tomcat, Jetty, Glassfish, OpenLiberty, etc., then you need to also specify in another IntelliJ panel which JDK should be used to launch that app server.
If using Maven or Gradle, you need to specify language level there too.
Easily switch between java versions with SDKMAN! and 'j'
Why won't sdkman change my default java version? - Stack Overflow
sdk - Java Version Switch - Stack Overflow
Switching versions of Java on Mac OSX
Videos
https://joerg-pfruender.github.io/software/java/2022/12/30/sdkman_j.html
I just happen to get that error, on Manjaro ..after an update of the S.O., so the error is the /usr/bin/java now points to the default java installed on the update.
So i just removed all Java versions installed on the updates cause I need only to use the sdkman.
Copysdk home java 8.0.232.hs-adpt
With this i can see where are the candidates on my case:
Copy/home/xxxx/.sdkman/candidates/java/8.0.232.hs-adpt
So after removed all java: i run java -version i found there is no java anymore.
So i force update sdkman
Copysdk selfupdate force
Then after install
Copysource "$HOME/.sdkman/bin/sdkman-init.sh"
And to be sure i ran :
Copyls -al /usr/bin/java
lrwxrwxrwx 1 root root 37 may 16 2020 /usr/bin/java -> /usr/lib/jvm/default-runtime/bin/java
and now it points to where sdkman supposed to:
And thats it now i can change versions again with sdkman.
Copysdk use java 11.0.5.hs-adpt
For me, the problem was the ending of .bashrc. I know, it explicitly says there "THIS MUST BE AT THE END OF THE FILE FOR SDKMAN TO WORK!!!", but I still decided to ignore that and wrote a few of my own lines after those ones 🤡. When I made sure the sdkman's lines were indeed at the very end of the file and after running sdk selfupdate force, setting the version started working properly across different terminals.
Yes you can.
You should use the SDK Man software.
curl -s "https://get.sdkman.io" | bash
When doing the sdk list java, you will get a screen like this:
=============================================================================== Available Java Versions for Linux 64bit ================================================================================ Vendor | Use | Version | Dist | Status | Identifier -------------------------------------------------------------------------------- Corretto | | 21.0.2 | amzn | | 21.0.2-amzn
| | 21.0.1 | amzn | | 21.0.1-amzn
| | 17.0.10 | amzn | | 17.0.10-amzn
| | 17.0.9 | amzn | | 17.0.9-amzn
| | 11.0.22 | amzn | | 11.0.22-amzn
| | 11.0.21 | amzn | | 11.0.21-amzn
| | 8.0.402 | amzn | | 8.0.402-amzn
| | 8.0.392 | amzn | | 8.0.392-amzn Dragonwell | | 17.0.9 | albba | | 17.0.9-albba
| | 11.0.21 | albba | | 11.0.21-albba
| | 11.0.20 | albba | | 11.0.20-albba
| | 8.0.402 | albba | | 8.0.402-albba
| | 8.0.392 | albba | | 8.0.392-albba
| | 8.0.382 | albba | | 8.0.382-albba Gluon | | 22.1.0.1.r17 | gln | | 22.1.0.1.r17-gln
| | 22.1.0.1.r11 | gln | | 22.1.0.1.r11-gln GraalVM CE | | 21.0.2 | graalce | | 21.0.2-graalce
| | 21.0.1 | graalce | | 21.0.1-graalce
| | 17.0.9 | graalce | | 17.0.9-graalce GraalVM Oracle| >>> | 21.0.2 | graal | installed | 21.0.2-graal
| | 21.0.1 | graal | | 21.0.1-graal
| | 17.0.10 | graal | | 17.0.10-graal
| | 17.0.9 | graal | | 17.0.9-graal
First of all you should install all the different version by:
sdk install java yourVersion like sdk install java 21.0.1-graalce or sdk install java 17.0.9-graalce or sdk install java 23.ea.12-open.
This allows you to go to a directory and do sdk use java 21.0.1-graalce.
This will activate the JDK 21 version of the GraalVM CommunityEdition (CE). You can do this for different version in different directories.
For support purposes I have multiple versions of Java installed all the time. Namely, I have:
- Oracle Java 6
- Oracle Java 7
- Oracle Java 8
- Oracle Java 11
- OpenJDK 11
- OpenJDK 17
- OpenJDK 21
Yes, I have two Java 11 from different sources.
You can download the packages separately and decompress them. This stategy avoids using the installers since they will try to manage the system properties and set/reset their own versions as the "default one". You probably want to manage the default manually, not automatically.
Now, your folder will look like:
Copyjdk1.6.0_34
jdk1.7.0_40
jdk1.8.0_51
openjdk-11+28
java -> jdk-11+28 (this is a symlink)
...
The PATH variable includes the symlink folder only. This way I decide which java version to use by switching the java symlink -- that is pointing in this example to the OpenJDK 11. If I want to use Java 6, I can repoint the symlink by doing:
Copyrm java
ln -s jdk1.6.0_34 java
Easy, isn't it?
Finally, most IDEs can make this change a lot easier, but I wanted to show you the manual way of doing things, so you can understand there's no magic behind it.