Here's a list of OpenJDK distributions still offered as JRE build. One could consider Temurin the most official one, while Zulu is offered for the longest and together with Liberica offers JavaFX included runtimes.
| Name | Vendor | Download |
|---|---|---|
| Temurin | Adoptium | https://adoptium.net/temurin/releases |
| Zulu | Azul | https://www.azul.com/downloads/?package=jre#zulu |
| Liberica | Bellsoft | https://bell-sw.com/pages/downloads/?package=jre |
| SapMachine | SAP | https://sap.github.io/SapMachine/ |
| Semeru | IBM | https://developer.ibm.com/languages/java/semeru-runtimes/downloads/ |
Java Runtime Environment (JRE) 17 Not Installed (when it is...)... Installing Catia v5
eclipse - Can I run a java program built using Java 8 (.192) using JRE 17, or does everything (JRE, JVM, JDK) have to be on the correct Java 8 version first? - Stack Overflow
maven - Both Java 8 and 17 installed, does java -version always output 17? - Stack Overflow
jython - How to get JRE root path for java 17 using "java -verbose -version" - Stack Overflow
What is Java JDK?
What is Java?
Is Java free to use?
Videos
In the past, there were JDK and JRE. End-users only needed to install JRE which was smaller than JDK. I know the latest JDK is 17.0.2, but where is JRE 17? All I could find was JRE 8. Has JRE been deprecated and now even end-users need to install JDK 17, if they want to run Java applications written in Java 17?
I just bought the 3DExperience Engineer Student Edition and am trying to download the Catia v5 tool within 3DExperience, however, every time I run the launcher, I get the error from Java Runtime Environment regarding it not being installed, and to use the two links it provides to install JRE 17. I think I have installed at least 15 different versions and each time it says that it does not detect it being installed. I've perused through countless subreddits and youtube videos, only to still not get an answer.
Looking for any insight to solve this. Thanks.
Error SnippetJava 8 is still available, as the first Long-Term Support (LTS) version. I would suggest starting with the latest update of Java 8. The current release is Update 402 (as seen on Adoptium).
Be aware that Java 8 is not receiving regular updates for the public except for critical security patches. You may want to consider paying for a support contract from any number of vendors such as Azul Systems or Oracle to get support including possible additional updates releases through the rest of this decade.
Generally Java apps will run on later versions of Java without any modifications needed. The Java team at Oracle and the OpenJDK community place a very high priority on preserving that compatibility.
However, there are exceptions to the compatibility policy. In particular: Java 9 introduced the Java Platform Module System which caused some problems in some apps. And in later versions of Java some libraries that were previously bundled are now removed. Some of those removed libraries were transferred to the Jakarta EE project at the Eclipse Foundation. Some were abandoned for lack of interest such as CORBA.
Some few parts of Java that were for years marked as “deprecated for eventual removal” have now been removed.
If you consider moving beyond Java 8, I suggest your first step be sitting down to read through the Release Notes for every release of Java. They are quite well-written. They should alert you to any issues that may affect your app.
FYI, Java 21 is the latest LTS version. Java 23 is current, as of 2024-11. Java 24 arrives in the Spring. A major new version arrives every six months. Java 25 in Fall of 2025 is likely to be the next LTS version. Keep track of Java versions on Wikipedia.
I have a program for work that I'm told will only use Java version 8 update 192 to run correctly.
I would doubt the accuracy of that statement. I would say that someone is making a statement without evidence ... if that is what they actually said.
Maybe a more accurate statement is that the program is only known to run on that particular version ...
Anyway, it will probably run on a later version of Java 8, or Java 11. Java 17 is less certain because of the issue of package sealing / blocking of access to internal packages that occurred in Java 16. (Some of the sealing / blocking started in Java 9 ... but there are easy workarounds ...)
Q: Do you need a JRE?
A: No. A JDK will work just as well. (A JDK distro includes a JRE.) But unless there are strong counter-indications, you need the latest version of Java 8, 11 or 17. Java 8 u192 is years out of date.
The only way to be sure that the application will work on a particular version of Java is to try it. In general, there are no shortcuts.