Java jdk download linux

6 JDK Installation for Linux Platforms

This page describes JDK for Linux system requirements and gives installation instructions for several JDK-Linux combinations.

This page contains these topics:

See «JDK 8 and JRE 8 Installation Start Here» for general information about installing JDK 8 and JRE 8.

For information on enhancements to JDK 8 that relate to the installer, see «Installer Enhancements in JDK 8».

System Requirements

See http://www.oracle.com/technetwork/java/javase/certconfig-2095354.html for information about supported platforms, operating systems, and browsers.

On a 64-bit system, you can download either the 64-bit or the 32-bit version of the Java platform. However, if you are using a 32-bit browser and you want to use the plugin, then you need to install the 32-bit version of the Java platform. To determine which version of Firefox you are running, launch the application, and select the menu item Help -> About Mozilla Firefox. At the bottom of the window is a version string line that contains either «Linux i686» (32-bit) or «Linux x86_64» (64-bit). To setup the Java plugin, see «Manual Installation and Registration of Java Plugin for Linux».

JDK 8 Installation Instructions

This topic describes:

Installation Instructions Notation and Files

For instructions containing the notation version , substitute the appropriate JDK update version number. For example, if you are installing update JDK 8 update release 2, the following string representing the name of the bundle:

Note that, as in the preceding example, the version number is sometimes preceded with the letter u , for example, 8u2 , and sometimes it is preceded with an underbar, for example, jdk1.8.0_02 .

The following table lists the options and instructions for downloading the JDK 8 release on a Linux platform.

Download File and Instructions	Architecture (CPU Type)	Who Can Install
For Linux x64 systems: jdk-8u version -linux-x64.tar.gz «Installation of the 64-bit JDK on Linux Platforms»	Intel — 64-bit	anyone
For Linux aarch64 (64-bit ARM) systems: jdk-8u version -linux-aarch64.tar.gz (version 8u271 and later) «Installation of the 64-bit JDK on Linux Platforms	ARM — 64-bit	anyone
For Linux x86 systems: jdk-8u version -linux-i586.tar.gz «Installation of the 32-bit JDK on Linux Platforms»	Intel — 32-bit	anyone
For Linux x64 systems: jdk-8u version -linux-x64.rpm «Installation of the 64-bit JDK on RPM-based Linux Platforms»	Intel — 64-bit RPM-based Linux	root
For Linux aarch64 (64-bit ARM) systems: jdk-8u version -linux-aarch64.rpm (version 8u271 and later) «Installation of the 64-bit JDK on RPM-based Linux Platforms»	ARM — 64-bit RPM-based Linux	root
For Linux x86 systems: jdk-8u version -linux-i586.rpm «Installation of the 32-bit JDK on RPM-based Linux Platforms»	Intel — 32-bit RPM-based Linux	root

Installation can be performed using either of the following:

Installation of JDK using archive files ( .tar.gz ) allows you to install a private version of the JDK for the current user into any location, without affecting other JDK installations. However, it may involve manual steps to get some of the features to work (for example, the -version: release option of the java command, which allows you to specify the release to be used to run the specified class, requires the correct path to the JDK release under /usr/jdk ).

Installation of JDK using RPM packages allows you to perform a system-wide installation of the JDK for all users, and requires root access.

When you download and install the Java Development Kit (JDK), the associated Java Runtime Environment (JRE) is also installed.

JDK 7u6 and later releases include JavaFX SDK (version 2.2 or later). The JavaFX SDK and Runtime are installed and integrated into the standard JDK directory structure.

Installation of the 64-bit JDK on Linux Platforms

This procedure installs the Java Development Kit (JDK) for 64-bit Linux, using an archive file ( .tar.gz ).

These instructions use the following files:

jdk-8uversion-linux-x64.tar.gz and jdk-8uversion-linux-aarch64.tar.gz (version 8u271 and later) for 64-bit ARM systems.

Download the required file.

Before the file can be downloaded, you must accept the license agreement. The archive file can be installed by anyone (not only root users), in any location that you can write to. However, only the root user can install the JDK into the system location.

Change directory to the location where you would like the JDK to be installed, then move the .tar.gz archive file to the current directory.

Unpack the archive file and install the JDK.

• For x64 — % tar zxvf jdk-8uversion-linux-x64.tar.gz
• For 64-bit ARM system — % tar zxvf jdk-8uversion-linux-aarch64.tar.gz

The Java Development Kit files are installed in a directory called jdk1.8.0_ version in the current directory.

Delete the .tar.gz file if you want to save disk space.

Installation of the 64-bit JDK on RPM-based Linux Platforms

This procedure installs the Java Development Kit (JDK) for 64-bit RPM-based Linux platforms, such as Oracle, Red Hat and SuSE, using an RPM binary file ( .rpm ) in the system location. You must be root to perform this installation.

These instructions use the following files:

jdk-8uversion-linux-x64.rpm and jdk-8uversion-linux-aarch64.rpm (version 8u271 and later) for 64-bit ARM systems.

Download the required file.

Before the file can be downloaded, you must accept the license agreement.

Become root by running su and entering the super-user password.

Uninstall any earlier installations of the JDK packages.

Install the package:

• For x64 — # rpm -ivh jdk-8uversion-linux-x64.rpm
• For 64-bit ARM system — # rpm -ivh jdk-8uversion-linux-aarch64.rpm

To upgrade a package:

• For x64 — # rpm -Uvh jdk-8uversion-linux-x64.rpm
• For 64-bit ARM system — # rpm -Uvh jdk-8uversion-linux-aarch64.rpm

Delete the .rpm file if you want to save disk space.

Exit the root shell. No need to reboot.

Starting with version 8u40, the JDK installation is integrated with the alternatives framework and after installation, the alternatives framework is updated to reflect the binaries from the recently installed JDK. Java commands such as java , javac , javadoc , and javap can be invoked from the command line.

Using the java -version command, users can confirm the default (recently installed) JDK version.

In addition, users can now check which specific RPM package provides the java files:

Change in Communication With the Alternatives Framework of JDK RPM Installer Starting With JDK 8u261

Prior to JDK 8u261, the JDK RPM installers registered two groups of symbolic links with the alternatives framework, java and javac . In some versions of the alternatives framework, certain link names in these groups were duplicated, which resulted in installation failures.

Starting with JDK 8u261, the JDK RPM doesn’t register the javac group with the alternatives framework. All links unique to the javac group are moved into the java group, but the set of symbolic links registered by the installer are not changed; only the duplicated links have been dropped.

The implication of this change is that if you install JDK 8u261 and JDK 8u251 (or older versions) and uninstall JDK 8u261, the symbolic links from the java group that are managed by the alternatives framework will be deleted. To restore the deleted links, run the following command:

Installation of the 32-bit JDK on Linux Platforms

This procedure installs the Java Development Kit (JDK) for 32-bit Linux, using an archive file ( .tar.gz ).

These instructions use the following file:

Download the file.

Before the file can be downloaded, you must accept the license agreement. The archive file can be installed by anyone (not only root users), in any location that you can write to. However, only the root user can install the JDK into the system location.

Change directory to the location where you would like the JDK to be installed, then move the .tar.gz archive file to the current directory.

Unpack the archive file and install the JDK.

The Java Development Kit files are installed in a directory called jdk1.8.0_ version in the current directory.

Delete the .tar.gz file if you want to save disk space.

Installation of the 32-bit JDK on RPM-based Linux Platforms

This procedure installs the Java Development Kit (JDK) for 32-bit RPM-based Linux platforms, such as Red Hat and SuSE, using an RPM binary file ( .rpm ) in the system location. You must be root to perform this installation.

These instructions use the following file:

Download the file.

Before the file can be downloaded, you must accept the license agreement.

Become root by running su and entering the super-user password.

Uninstall any earlier installations of the JDK packages.

Install the package.

To upgrade a package:

Exit the root shell. No need to reboot.

Delete the .rpm file if you want to save disk space.

Starting with version 8u40, the JDK installation is integrated with the alternatives framework and after installation, the alternatives framework is updated to reflect the binaries from the recently installed JDK. Java commands such as java , javac , javadoc , and javap can be invoked from the command line.

Using the java -version command, users can confirm the default (recently installed) JDK version.

In addition, users can now check which specific RPM package provides the java files:

Installation of Public Key on RPM-based Linux Platforms

Since JDK version 8, the JDK RPMs are signed with OL keys. Installation of these RPMs on Linux distributions other than OL gives a warning message indicating that security validation of the package fails. This indicates that the public key used to sign this RPM needs to be installed in the system. A sample warning message and the public key installation steps are as follows:

Sample Warning Message

Installation Steps

Download the key file from https://yum.oracle.com/RPM-GPG-KEY-oracle-ol7 using the following command:

Install the key using the following command:

sudo rpm —import RPM-GPG-KEY-oracle-ol7

Public key installation needs to be done only once. The key installation is persistent across reboots.

General Installation Notes

This topic describes general installation topics.

Root Access

Installing the software automatically creates a directory called jdk1.8.0_ version . Note that if you choose to install the JDK into system-wide location, such as /usr/jdk , you must first become root to gain the necessary permissions. If you do not have root access, simply install the JDK into your home directory, or a subdirectory that you have permission to write to.

Overwriting Files

If you install the software in a directory that contains a subdirectory named jdk1.8.0_ version , the new software overwrites files of the same name in that jdk1.8.0_ version directory. Please be careful to rename the old directory if it contains files you would like to keep.

System Preferences

By default, the installation script configures the system such that the backing store for system preferences is created inside the JDK’s installation directory. If the JDK is installed on a network-mounted drive, it and the system preferences can be exported for sharing with Java runtime environments on other machines.

Источник

Java SE JDK and JRE 8.301

Java allows you to play online games, chat with people around the world, calculate your mortgage interest, and view images in 3D, just to name a few. This new version is considered a Critical Patch Update.

Download

What’s New

Certified

Similar to 5

It’s also integral to the intranet applications and other e-business solutions that are the foundation of corporate computing. Installing this update will ensure that your Java applications continue to run as safely and efficiently as always.

The JRE is the Java Runtime Environment, it covers most end-users needs. Contains everything required to run Java applications on your system. It is a package of everything necessary to run a compiled Java program, including the Java Virtual Machine (JVM), the Java Class Library, the java command, and other infrastructure. However, it cannot be used to create new programs.

The JDK is the Java Development Kit, the full-featured SDK for Java. It has everything the JRE has, but also the compiler (javac) and tools (like javadoc and jdb). It is capable of creating and compiling programs.

Usually, if you only care about running Java programs on computer you will only install the JRE. It’s all you need. On the other hand, if you are planning to do some Java programming, you need to install the JDK instead.

Sometimes, even if you are not planning to do any Java development on a computer, you still need the JDK installed. For example, if you are deploying a web application with JSP, you are technically just running Java programs inside the application server. Why would you need the JDK then? Because the application server will convert JSP into Java servlets and needs to use the JDK to compile the servlets.

Allow SASL Mechanisms to Be Restricted

• A security property named jdk.sasl.disabledMechanisms has been added that can be used to disable SASL mechanisms. Any disabled mechanism will be ignored if it is specified in the mechanisms argument of Sasl.createSaslClient or the mechanism argument of Sasl.createSaslServer. The default value for this security property is empty, which means that no mechanisms are disabled out-of-the-box.

SunPKCS11 Provider Upgraded with Support for PKCS#11 v2.40

• The SunPKCS11 provider has been updated with support for PKCS#11 v2.40. This version adds support for more algorithms such as the AES/GCM/NoPadding cipher, DSA signatures using SHA-2 family of message digests, and RSASSA-PSS signatures when the corresponding PKCS11 mechanisms are supported by the underlying PKCS11 library.

New Checks on Trust Anchor Certificates

• New checks have been added to ensure that trust anchors are CA certificates and contain proper extensions. Trust anchors are used to validate certificate chains used in TLS and signed code. Trust anchor certificates must include a Basic Constraints extension with the cA field set to true. Also, if they include a Key Usage extension, the keyCertSign bit must be set.
• A new system property named jdk.security.allowNonCaAnchor has been introduced to restore the previous behavior, if necessary. If the property is set to the empty String or «true» (case-insensitive), trust anchor certificates can be used if they do not have proper CA extensions.
• The default value of this property, if not set, is «false».
• Note that the property does not apply to X.509 v1 certificates (since they don’t support extensions).
• This property is currently used by the JDK implementation. It is not guaranteed to be supported by other Java SE implementations.

Exact Match Required for Trusted TLS Server Certificate

• A TLS server certificate must be an exact match of a trusted certificate on the client in order for it to be trusted when establishing a TLS connection.

Added LuxTrust Global Root 2 Certificate

The following root certificate has been added to the cacerts truststore:

+ LuxTrust
+ luxtrustglobalroot2ca
DN: CN=LuxTrust Global Root 2, O=LuxTrust S.A., C=LU

Bug Fixes:

Support for OpenType CFF Fonts

• Previously, Oracle JDK 8 did not include OpenType CFF fonts (.otf fonts) into the standard logical fonts (such as «Dialog» and «SansSerif»). This resulted in missing glyphs when rendering text. In the most extreme cases where only CFF fonts were installed on the system, a Java exception could be thrown.
• Several Linux distributions were affected by this issue because they rely on CFF fonts to support some languages, which is common for CJK (Chinese, Japanese, and Korean) languages.
• Oracle JDK 8 now uses these CFF fonts, and this issue has been resolved.

Better Serial Filter Handling

• The jdk.serialFilter system property can only be set on the command line. If the filter has not been set on the command line, it can be set can be set with java.io.ObjectInputFilter.Config.setSerialFilter. Setting the jdk.serialFilter with java.lang.System.setProperty has no effect.

Legacy:

If you are looking for previous Java versions here are the links to download:

Источник