Merge pull request #7458 from OpenLiberty/7427-versionless

24008 issues to staging

modules/ROOT/pages/deployment-openshift.adoc

@@ -6,7 +6,7 @@
 // Contributors:
 //     IBM Corporation
 //
-// This doc is hosted in the Red Hat Runtimes documentation. Any changes made to this doc also need to be made to the version that's located in the PurpleLiberty GitHub repo (https://github.com/PurpleLiberty/docs).
+//
 //
 :page-description: Red Hat OpenShift is a Kubernetes-based application platform. After you write your applications, you can containerize and deploy them to Red Hat OpenShift to orchestrate and automate your containers.
 :seo-title: Deployment on Red Hat OpenShift - OpenLiberty.io

modules/ROOT/pages/integration-testing.adoc

@@ -6,7 +6,7 @@
 // Contributors:
 //     IBM Corporation
 //
-// This doc is hosted in the Red Hat Runtimes documentation. Any changes made to this doc also need to be made to the version that's located in the PurpleLiberty GitHub repo (https://github.com/PurpleLiberty/docs).
+//
 //
 :page-layout: general-reference
 :page-type: general
@@ -128,4 +128,3 @@ The number of IDs is checked to ensure that only one person exists in the servic
 Another `GET` request is sent to retrieve the details of the person with the extracted ID. The response is validated to ensure a successful status code `(200)`. The name of the person is extracted from the response by using JSONPath.
 
 Finally, the extracted name is compared with the expected value `bob` using the `assertEquals()` method.
-

modules/ROOT/pages/log-trace-configuration.adoc

@@ -6,7 +6,7 @@
 // Contributors:
 //     IBM Corporation
 //
-// This doc is hosted in the Red Hat Runtimes documentation. Any changes made to this doc also need to be made to the version that's located in the PurpleLiberty GitHub repo (https://github.com/PurpleLiberty/docs).
+//
 //
 :page-layout: general-reference
 :page-type: general

modules/ROOT/pages/thread-pool-tuning.adoc

@@ -6,7 +6,7 @@
 // Contributors:
 //     IBM Corporation
 //
-// This doc is hosted in the Red Hat Runtimes documentation. Any changes made to this doc also need to be made to the version that's located in the PurpleLiberty GitHub repo (https://github.com/PurpleLiberty/docs).
+//
 //
 :page-description: Open Liberty provides a self-tuning algorithm that controls the size of its thread pool. For most applications that run on Open Liberty, it is not necessary to tune the size of the thread pool.
 :page-layout: general-reference

modules/reference/pages/command/featureUtility-commands.adoc

@@ -24,7 +24,6 @@ The following `featureUtility` commands are available:
 * xref:command/featureUtility-installServerFeatures.adoc[featureUtility installServerFeatures]: The command installs the required features that are listed in the `server.xml` file of a server.
 * xref:command/featureUtility-viewSettings.adoc[featureUtility viewSettings]: The command is used to view Maven repository and proxy settings when Maven repositories other than Maven Central are configured.
 
-
 [#mod]
 == Modifications for featureUtility commands
 

modules/reference/pages/command/featureUtility-installServerFeatures.adoc

@@ -16,6 +16,8 @@
 
 The `featureUtility installServerFeatures` command installs the required features that are listed in the `server.xml` file of a server.
 
+You can use the `featureUtility installServerFeatures` command to install both versioned and xref:reference:feature/versionless-features.adoc[versionless features].
+
 == Usage example
 
 Install the server features for the `myserver` server:
@@ -65,7 +67,7 @@ The name of the server to run the command against.
 |Displays additional debug information while the action runs.
 
 |--verify=_verify_option_
-a|Specifies how features must be verified during a process or an installation. 
+a|Specifies how features must be verified during a process or an installation.
 Supported values are `enforce`, `skip`, `all`, and `warn`. If this option is not specified, the default value is `enforce`.
 
 * `enforce`: Verifies the signatures of all Liberty features except for user features. It checks the integrity and authenticity of the features that are provided by the Liberty framework.

modules/reference/pages/config/server-configuration-overview.adoc

@@ -28,7 +28,7 @@ This example `server.xml` file configures the server to do the following things:
     <applicationManager autoExpand="true" />
 </server>
 ----
-* The `feature` element configures Open Liberty to support the JavaServer Pages 2.3 (`jsp-2.3`) feature.
+* The `feature` element configures Open Liberty to support the JavaServer Pages 2.3 (`jsp-2.3`) feature. You can also xref:reference:feature/versionless-features.adoc[configure versionless features] for any features that are part of the Java EE, Jakarta EE, or MicroProfile platforms.
 * The `httpPort` attribute is set to `9080`, which configures Open Liberty to listen to incoming traffic to `localhost` on port `9080`.
 * The `autoExpand` attribute is set to `true` so that WAR files are automatically expanded when they are deployed.
 

modules/reference/pages/feature/audit/description.adoc

@@ -6,4 +6,4 @@ The Audit feature introduces an infrastructure that serves two purposes:
 The Audit feature can capture a range of auditable events that include
 events related to authentication, authorization, and logout. The feature provides a default audit file handler implementation that emits human-readable audit records to a file-based log. Each audit record is emitted in JSON format.
 
-
+The Audit 2.0 feature (`audit-2.0`) provides the same audit records as the Audit 1.0 feature (`audit-1.0`) except it does not generate records for REST Handler applications. If you need to keep audit records for REST Handler applications, use `audit-1.0`.

modules/reference/pages/feature/feature-overview.adoc

@@ -6,7 +6,7 @@
 // Contributors:
 //     IBM Corporation
 //
-// This doc is hosted in the Red Hat Runtimes documentation. Any changes made to this doc also need to be made to the version that's located in the PurpleLiberty GitHub repo (https://github.com/PurpleLiberty/docs).
+//
 //
 :page-description: Features are the discrete units of functionality by which you control the pieces of the runtime environment that are loaded into a particular server. By adding or removing features from your server configuration, you can control what functions the server can perform.
 :seo-title: Feature overview - OpenLiberty.io
@@ -53,6 +53,8 @@ Occasionally, Liberty features that are not listed in the `server.xml` file are
 === Feature combinations and compatibility
 Not all Open Liberty features and feature versions are interoperable and some combinations might result in compatibility errors if they are enabled in the same server configuration.
 
+To avoid compatibility issues, you can xref:reference:feature/versionless-features.adoc[configure versionless features] for any features that are part of the Java EE, Jakarta EE, or MicroProfile platforms.
+
 ==== Singleton features and feature versions
 
 A singleton feature is a feature for which you can configure only one version per server. Most Open Liberty features are singleton features. If your server configuration includes multiple versions of the same singleton feature, either in the `server.xml` file or through feature dependencies, an error occurs and neither version of that feature loads.
@@ -63,7 +65,8 @@ If you have hard requirements on both feature versions, you must move some of yo
 ==== MicroProfile, Jakarta EE, and Java EE features
 Open Liberty features that support the MicroProfile, Jakarta EE, and Java EE specifications are sensitive to the version of whatever platform specification they target. For example, features that support Jakarta EE 10 do not interoperate with features that support Jakarta EE 8. Errors occur if you enable these features in the same server configuration.
 
-To avoid these errors, see the **Features that this feature enables** section on the feature:microprofile[display=MicroProfile], feature:jakartaee[display=Jakarta EE Platform] or feature:javaee[display=Java EE Platform] convenience feature pages. You can use this list to determine which individual feature versions align with each platform specification version. Alternatively, to enable all the features that support a particular platform specification version, use the MicroProfile, Jakarta EE, or Java EE <<#conv,convenience features>>.
+To avoid these errors, you can xref:reference:feature/versionless-features.adoc[configure versionless features] for any features that are part of the Java EE, Jakarta EE, or MicroProfile platforms.
+Alternatively, to enable all the features that support a particular platform specification version, use the MicroProfile, Jakarta EE, or Java EE <<#conv,convenience features>>.
 
 For more information about migrating your applications from one version of a MicroProfile or Jakarta EE specification to another, see the relevant _Differences between..._ pages in the xref:microprofile-api.adoc[MicroProfile API] and xref:jakarta-ee-api.adoc[Jakarta EE API] sections of the documentation.