Quick update of the documentation

Signed-off-by: David Matějček <[email protected]>

Author: dmatej

README.md

@@ -7,6 +7,8 @@ sponsored by the Eclipse Foundation.
 
 ### Compatibility
 
+* Eclipse GlassFish 8.0.0 is Jakarta EE 11 compatible, requires Java 21, experimentally also higher versions.
+* Eclipse GlassFish 7.1.0 is Jakarta EE 10 compatible, requires Java 17 or 21, experimentally also higher versions.
 * Eclipse GlassFish 7.0.25 is Jakarta EE 10 compatible, requires Java 11, 17 or 21, experimentally also higher versions.
 * Eclipse GlassFish 6.2.5 is Jakarta EE 9.1 compatible, requires Java 11 or 17
 * Eclipse GlassFish 6.1.0 is Jakarta EE 9.1 compatible, requires Java 11

docs/installation-guide/src/main/asciidoc/installing.adoc

@@ -14,7 +14,7 @@ prev=preface.html
 == 1 Installing {productName} 7
 
 This chapter provides instructions for installing {productName} 7
-software on Solaris, Linux, Mac OS X, and Windows systems.
+software on Linux, Mac OS X, and Windows systems.
 
 The following topics are addressed here:
 
@@ -36,8 +36,8 @@ does not meet release requirements. Also see "xref:release-notes.adoc#GSRLN00253
 Issues]" in {productName} Release Notes for known
 issues related to installation.
 
-* On Solaris, Linux, macOS and Windows systems, JDK software is available from the
-https://www.oracle.com/java/technologies/downloads/[Java SE downloads page].
+* On Linux, macOS and Windows systems, JDK software is available from the
+https://adoptium.net/temurin/releases[Eclipse Temurin JDK downloads page].
 
 [[javassist-library-license-notice]]
 
@@ -581,8 +581,7 @@ available by download from the
 https://glassfish.org/download.html[{productName} Downloads]
 page.
 
-{productName} 7 is also part of the Jakarta EE SDK
-distributions. The specifications are available from
+The Jakarta EE specifications are available from
 https://jakarta.ee/specifications/[Jakarta EE specifications page]
 and are not described in this document.
 
@@ -598,8 +597,8 @@ installation instructions for each method.
 ====
 Before performing any {productName} installation, ensure that your
 environment adheres to the JDK guidelines in
-"https://github.com/eclipse-ee4j/glassfishdoc/5.0/release-notes.pdf[Paths and
-Environment Settings for the JDK Software]" in {productName} Release Notes.
+"xref:release-notes.adoc#paths-and-environment-settings-for-the-jdk-software[Paths and Environment Settings for the JDK Software]"
+in {productName} Release Notes.
 ====
 
 

docs/performance-tuning-guide/src/main/asciidoc/tuning-java.adoc

@@ -115,7 +115,7 @@ which the surviving objects are moved to the old generation. When the
 old generation fills up, it triggers a major collection which involves
 the entire object heap.
 
-Both HotSpot and Solaris JDK use thread local object allocation pools
+HotSpot JDK uses thread local object allocation pools
 for lock-free, fast, and scalable object allocation. So, custom object
 pooling is not often required. Consider pooling only if object
 construction cost is high and significantly affects execution profiles.

docs/reference-manual/src/main/asciidoc/generate-jvm-report.adoc

@@ -39,7 +39,7 @@ and MXBeans that are provided in the Java Platform, Standard Edition
 (Java SE) or JDK software with which {productName} is being used.
 
 If {productName} is running in the Java Runtime Environment (JRE)
-software from JDK release 11 or Java SE 11, additional information is
+software from JDK release 17 or Java SE 17, additional information is
 provided. For example:
 
 * System load on the available processors

docs/reference-manual/src/main/asciidoc/package-appclient.adoc

@@ -39,7 +39,7 @@ After unjarring on the client machine, modify
 * set `AS_WEBSERVICES_LIB` to path-to-appclient`/appclient/lib`
 * set `AS_IMQ_LIB` to path-to-appclient`/appclient/mq/lib`
 * set `AS_INSTALL` to path-to-appclient``/appclient``
-* set `AS_JAVA` to your JDK 7 or JRE 7 home directory
+* set `AS_JAVA` to your JDK 17 home directory
 * set `AS_ACC_CONFIG` to
 path-to-appclient``/appclient/glassfish/domains/domain1/config/sun-acc.xml``
 

docs/release-notes/src/main/asciidoc/release-notes.adoc

@@ -121,7 +121,8 @@ The following topics are addressed here:
 
 ==== Required JDK Versions
 
-{productName} Release 7 requires Java 11 minimum and runs on JDK 11 to JDK 23.
+{productName} Release 7.1 requires Java 17 minimum and runs on JDK 17 to JDK 21, experimentally on higher versions.
+{productName} Release 7.0 requires Java 11 minimum and runs on JDK 11 to JDK 21, experimentally on higher versions.
 
 Also be sure to see xref:#paths-and-environment-settings-for-the-jdk-software[Paths and Environment Settings for the
 JDK Software] for important JDK configuration instructions.

docs/troubleshooting-guide/src/main/asciidoc/overview.adoc

@@ -54,7 +54,7 @@ is not supported or on a system that in some other way does not meet release req
 Also see "xref:release-notes.adoc#GSRLN00253[Known Issues]"
 in {productName} Release Notes for known issues related to installation.
 
-{productName} requires JDK release 11 or newer.
+{productName} requires JDK release 17 or newer.
 If necessary, download and install the required JDK software.
 
 On Solaris, Linux, and Windows systems, JDK software is available from the

docs/troubleshooting-guide/src/main/asciidoc/specific-issues.adoc

@@ -340,7 +340,7 @@ You experience JDK-related issues in a variety of circumstances.
 
 ==== Solution
 
-{productName} 7 requires JDK 11, so check your system for that dependency.
+{productName} 7.1 requires JDK 17, so check your system for that dependency.
 
 Ensure that the required JDK software is installed and that the
 `JAVA_HOME` environment variable points to the JDK installation
@@ -590,7 +590,7 @@ profilers also stop tracing as soon as they reach a class object or
 classloader.
 
 One diagnostic approach involves undeploying the application and
-triggering a memory dump using the JDK 11 `jcmd` tool.
+triggering a memory dump using the JDK 17 `jcmd` tool.
 The simplest analysis is to list all instances of `java.lang.Class`
 and look for class objects that have many instances.
 This is a sign that the class has been loaded