As a Java programmer, I work on various projects based on different Java versions, especially since the transition to the six-month release cycle. From time to time, I also have a piece of Java code that I want to try out on different Java versions – on the command line without having to click through the menus of my IDE. So it is helpful to be able to quickly and easily change the Java version to be used for compiling code or executing class files.
In this article, I'll show you how to install several Java versions simultaneously in Windows and how to switch between them on the command line with short commands.
Installing several Java versions at the same time is incredibly easy in Windows. You can download and run the installer for each version, which automatically installs the versions in separate directories.
C:\Program Files (x86)\JavaSoft\JRE\1.2\by default – I recommend changing this to
C:\Program Files (x86)\Java\jdk1.2.2\and
C:\Program Files (x86)\Java\jre1.2.2\for the sake of clarity.
C:\jdk1.3.1_28\by default – I recommend changing this to
C:\Program Files (x86)\Java\jdk1.3.1_28\.
C:\j2sdk1.4.2_19\by default – I recommend changing this to
C:\Program Files (x86)\Java\jdk1.4.2_19\.
Starting with the following versions, you don't need to change the default installation directories:
Attention – you may use the following Oracle distributions only for private purposes and development:
The following version is currently an early access build. You should use it only for testing purposes:
In most cases, the following two environment variables decide which Java version an application uses:
JAVA_HOME– many start scripts use this variable.
Path– is used when running a Java binary (such as
javac) from the console.
These variables should always point to the same Java installation to avoid unforeseen problems due to inconsistencies. Some programs, such as Eclipse, define the Java version in a separate configuration file (for Eclipse, for example, this is the entry "-vm" in the
The installers of the Java versions listed above already create various environment variables, which you need to clean up first (see below). The fastest way to change the environment variables is to press the Windows key and type "env" – Windows then offers "Edit the system environment variables" as a search result:
At this point, you can press "Enter," and the system properties appear:
Here you click on "Environment Variables…", after which the following window opens:
As the standard version, I currently use the latest release version, Java 16. Therefore, you should make the following settings:
C:\Program Files (x86)\Common Files\Oracle\Java\javapath
The path list should then look like this:
The last entry ensures that
JAVA_HOME are automatically consistent. Attention: this only works for the default setting configured here. If you change
JAVA_HOME via the command line, you have to adjust
Path accordingly (more about this below).
Now open a command line to check the settings with the following commands:
As a result, you should see this:
Finally, we come to the possibility to change the Java version quickly and easily. Therefore I create a separate command for each Java version, called, for example,
java13. I put these commands in the directory
C:\Program Files\Java\scripts, which I add to the environment variable "Path" as described before:
The files are named, for example,
java13.bat, and change the environment variables as shown in the following example of
@echo off set JAVA_HOME=C:\Program Files\Java\jdk-16 set Path=%JAVA_HOME%\bin;%Path% echo Java 16 activated.
This script, admittedly kept very simple, inserts the
bin directory of the Java version to be activated at the beginning of the
Path variable, so that is where, for example,
java.exe is looked for first. The path variable becomes longer with each switching. However, since this is only the case for the currently opened command prompt, I don't think this is a problem.
The following ZIP file contains all my scripts from Java 1.2 to Java 17 (you might have to adopt one or the other Java directory to your installation): scripts-up-to-jdk17.zip
You can quickly test whether the scripts work in a command line. Attention: after adding the
scripts directory to the
Path variable, you have to open a new command line.
At this point, the setup is complete. I hope this article was helpful for you, and I'd love to hear your comments. If you liked the article, I'd be happy if you shared it via one of the following share icons.