-
Bug
-
Resolution: Delivered
-
P4
-
None
-
11.0.18
-
generic
-
generic
A DESCRIPTION OF THE PROBLEM :
In the discussion of the change, "Disable Side-by-Side Installations of Multiple JDK Updates in Windows JDK Installers", there is a sentence discussing installation of a later version like 11.0.19, where it mistakenly says:
"Thus the 11.0.8 and 11.0.19 releases will both install into %Program Files%\Java\jdk-11 by default, and they both cannot be installed at the same time."
That should, of course, be referring to the new release itself, 11.0.18. While it may seem an obvious mistake, and to some should be easily "understood" by readers, it could confuse some folks if they take it literally, as-is.
FWIW, the direct URL to the section of the page is https://www.oracle.com/java/technologies/javase/11-0-18-relnotes.html?1#JDK-8292822 .
If it helps save someone time, I can confirm that the problem does NOT exist in the other release notes for the Jan 2023 updates. With the release notes for 17.0.6 (which has the same section), it correctly refers to 17.0.6 and a future 17.0.7. And of course the matter is not mentioned in the 19.0.2 release notes because this single-version approach was implemented from the initial release of 19.
In the discussion of the change, "Disable Side-by-Side Installations of Multiple JDK Updates in Windows JDK Installers", there is a sentence discussing installation of a later version like 11.0.19, where it mistakenly says:
"Thus the 11.0.8 and 11.0.19 releases will both install into %Program Files%\Java\jdk-11 by default, and they both cannot be installed at the same time."
That should, of course, be referring to the new release itself, 11.0.18. While it may seem an obvious mistake, and to some should be easily "understood" by readers, it could confuse some folks if they take it literally, as-is.
FWIW, the direct URL to the section of the page is https://www.oracle.com/java/technologies/javase/11-0-18-relnotes.html?1#JDK-8292822 .
If it helps save someone time, I can confirm that the problem does NOT exist in the other release notes for the Jan 2023 updates. With the release notes for 17.0.6 (which has the same section), it correctly refers to 17.0.6 and a future 17.0.7. And of course the matter is not mentioned in the 19.0.2 release notes because this single-version approach was implemented from the initial release of 19.