Replacing a Java environment with running Java applications can lead to side effects and uncontrolled behavior.
Yum install openjdk 1.8 centos 7 update#
Running yum update on CentOS or respectively apt update & apt upgrade on Ubuntu replaces your OpenJDK 11.0.2.7 with the new version 11.0.3.7. Let’s say you have the package java-11-openjdk-devel installed which comes in version 11.0.2.7 and there is a new version of OpenJDK 11.0.3.7 available and you want to update your system. Over time there will be updates on Java packages.
Yum install openjdk 1.8 centos 7 manual#
It will change the mechanism from auto to manual and gives you more control which default Java environment is used on your system. To prevent changes affecting your running Java applications, run the update-alternative -config java tool and set it manually, even you have just one JDK installed. The first output line of the update-alternatives -display java shows you the default setting which is java - status is auto and the Java version with the highest priority defines which Java is set by default. OpenJDK 64-Bit Server VM (build 11.0.2+9-Ubuntu-3ubuntu118.04.3, mixed mode, sharing) OpenJDK Runtime Environment (build 11.0.2+9-Ubuntu-3ubuntu118.04.3)
Set the java-11-openjdk-amd64 as your manual selected version by type 1. The + tells you what is selected, in auto mode the version with the highest priority is selected. Press to keep the current choice, or type selection number:
* 0 /usr/lib/jvm/java-11-openjdk-amd64/bin/java 1111 auto modeġ /usr/lib/jvm/java-11-openjdk-amd64/bin/java 1111 manual modeĢ /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java 1081 manual mode There are 2 choices for the alternative java (providing /usr/bin/java). You can verify this here: update-alternatives -display javaĬheck which Java versions are already installed on my system with yum: apt list -installed | grep openjdk To prevent this behavior, run the update-alternative -config java tool and set it manually, even you have just one JDK installed. This can cause weird behavior when you restart running Java applications and can get you in some unnecessary trouble. As soon as you install OpenJDK 1.8.0 it will change your system to use this as your new default because it is set as auto selection by default. This means if you just install OpenJDK 11 it will be your default JDK. For CentOS 7 by default tells you OpenJDK 1.8.0 is the best-suited version for your system. By default you will see java - status is auto. The first output line of the update-alternatives -display java shows you the default setting and how it is selected. Test if the Java compiler is set to the same version you’ve selected: javac -version OpenJDK 64-Bit Server VM 18.9 (build 11.0.3+7-LTS, mixed mode, sharing) OpenJDK Runtime Environment 18.9 (build 11.0.3+7-LTS) Test if the Java Runtime Environment is the version you’ve selected: java -version There are 3 programs which provide 'java'. Set the java-11-openjdk.x86_64 as your selected by type 3.
The * is what the distribution to prefer as the “best version” and the + tells you what is selected. Set a default version update-alternatives -config java The update-alternatives tool shows which version is currently used as default: update-alternatives -display java For OpenNMS Horizon it is required to have OpenJDK Development Kit installed which is named java-11-openjdk-devel on CentOS and on Ubuntu openjdk-11-jdk.Ĭheck which Java versions are already installed on my system with yum: yum list installed | grep java
0 kommentar(er)
