diff --git a/help/en/html/doc/Technical/JVMCapabilities.shtml b/help/en/html/doc/Technical/JVMCapabilities.shtml index ca208261764..c48d7b906a1 100644 --- a/help/en/html/doc/Technical/JVMCapabilities.shtml +++ b/help/en/html/doc/Technical/JVMCapabilities.shtml @@ -78,26 +78,7 @@ using very large fonts as a workaround, but it quickly breaks as text overlaps widget boundaries) - 8? - - 9 - - - - It seems that MacOS X (macOS) users will lose the use - of the OS X App menu for About, Preferences, and - (critically) Quit handling on that platform - - 9 - - 9 - - - - It seems that MacOS X (macOS) users will lose - Applescript scripting - - 9 + 8 9 @@ -106,9 +87,9 @@ Multi-version JARs can help with migration, see discussion - ? - 9 + + ? @@ -120,18 +101,6 @@ 8 - - JMRI uses several com.sun classes that will, at some point, - no longer be accessible. This was originally scheduled as part of JPMS for - 1.9, but was later removed. At some point, we will - need to migrate away from these before using a more - advanced JRE or JDK. - - ? - - ? - - Java Platform Module System @@ -161,27 +130,65 @@ JLink - improve packaging, faster startup - ? - 9 + + ? - Even better support for immutable collections + var syntax - improves readability of code, use of generics + + 10
11 ? + + + + Even better support for immutable collections 10 + + ? - Improved String whitespace support + It seems that MacOS X (macOS) users will lose the use + of the OS X App menu for About, Preferences, and + (critically) Quit handling on that platform - ? + > 10 + + > 10 + + + + It seems that MacOS X (macOS) users will lose + Applescript scripting + + > 10 + + > 10 + + + + Improved String whitespace support 11 + + ? + + JMRI uses several com.sun classes that will, at some point, + no longer be accessible. This was originally scheduled as part of JPMS for + 1.9, but was later removed. At some point, we will + need to migrate away from these before using a more + advanced JRE or JDK. + + > 11 + + > 11 + (* indicates that a compatibility library is used in the early version) @@ -199,12 +206,18 @@ As of April 8, 2014 Microsoft stopped supporting Windows XP and therefore it is no longer a supported platform." Google finds numerous pages that show how to install Java 1.7 on XP - or XP SP2. JMRI's - Windows installation page - will have updated information on this. - The corresponding + or XP SP2. + Although the corresponding Java 8 page - makes no mention of XP.

+ makes no mention of XP, it seems reasonable to assume the same applies. + JMRI's + Windows installation page + keeps updated information on this. + Several JMRI users have reporter that Java 1.8_151 is the last one that + can be cleanly installed and run on XP. See + the + Java download archive page + for links to that.

Updated Feb 10, 2018: At that time, although Java 9 was available, it was diff --git a/help/en/html/doc/Technical/TechRoadMap.shtml b/help/en/html/doc/Technical/TechRoadMap.shtml index 5d431c031fa..fed30445ad5 100644 --- a/help/en/html/doc/Technical/TechRoadMap.shtml +++ b/help/en/html/doc/Technical/TechRoadMap.shtml @@ -257,25 +257,28 @@ releases in Fall 2015 started the requirement for Java 8, also known as Java 1.8. This has continued through the following release series. - The June 2018 release, notionally JMRI 4.12 will - remain with Java 8, but may involve other updates. + The December 2018 release, notionally JMRI 4.14 will + remain with Java 8, but may involve other library updates. + This includes doing development, test and production release + builds using Java 1.8.0_72.

The next long-term-support Java release will be - Java 11 in Fall of 2018. Oracle intendes to + Java 11 in Fall of 2018. Oracle intends to align their Java and the OpenJDK at that point. Because some people will need to have that on their computers for other purposes, - we intend to support JMRI running on Oracle Java 8 through 11 + we intend to support JMRI building and/or running on Oracle Java 8 through 11 and OpenJDK version 11 - by JMRI 4.14 in December 2018. + by JMRI 4.14 in December 2018.

At some point, the Java version required by JMRI has to move forward. For example, Oracle has announced that they'll stop providing standalone JRE installers by the end of 2020, by which time JMRI distributions will have to contain - the Java runtime components. That in turn might require tools like - jlink from Java 9 or late. + the Java runtime components or it won't be possible to run JMRI on newly-bought PCs. + That in turn might require tools like + jlink from Java 9 or later.

While we don't know yet when JMRI will have to move past Java 1.8,