Sync documentation of main branch

actions-user · actions-user · commit c6b346217cc6 · 2025-05-07T01:59:42.000Z
diff --git a/_data/versioned/main/index/quarkus.yaml b/_data/versioned/main/index/quarkus.yaml
@@ -2991,7 +2991,7 @@ types:
     - io.quarkus:quarkus-smallrye-stork
     type: guide
     url: /guides/stork-kubernetes
-  - title: Using WebSockets
+  - title: Using WebSockets with Undertow
     filename: websockets.adoc
     summary: This guide explains how your Quarkus application can utilize web sockets to create interactive web applications.
     categories: web
diff --git a/_data/versioned/main/index/relations.yaml b/_data/versioned/main/index/relations.yaml
@@ -8655,7 +8655,7 @@
     url: /guides/tls-registry-reference
     type: reference
     matches: 1
-  - title: Using WebSockets
+  - title: Using WebSockets with Undertow
     url: /guides/websockets
     type: guide
     matches: 1
@@ -10944,7 +10944,7 @@
     url: /guides/reactive-routes
     type: guide
     matches: 1
-  - title: Using WebSockets
+  - title: Using WebSockets with Undertow
     url: /guides/websockets
     type: guide
     matches: 1
@@ -13882,7 +13882,7 @@
     url: /guides/tls-registry-reference
     type: reference
     matches: 1
-  - title: Using WebSockets
+  - title: Using WebSockets with Undertow
     url: /guides/websockets
     type: guide
     matches: 1
@@ -23372,7 +23372,7 @@
     url: /guides/tls-registry-reference
     type: reference
     matches: 1
-  - title: Using WebSockets
+  - title: Using WebSockets with Undertow
     url: /guides/websockets
     type: guide
     matches: 1
@@ -23426,7 +23426,7 @@
     url: /guides/tls-registry-reference
     type: reference
     matches: 1
-  - title: Using WebSockets
+  - title: Using WebSockets with Undertow
     url: /guides/websockets
     type: guide
     matches: 1
@@ -23470,7 +23470,7 @@
     url: /guides/websockets-next-tutorial
     type: tutorial
     matches: 2
-  - title: Using WebSockets
+  - title: Using WebSockets with Undertow
     url: /guides/websockets
     type: guide
     matches: 2
@@ -23501,7 +23501,7 @@
     matches: 1
 /guides/websockets-next-tutorial:
   sameTopics:
-  - title: Using WebSockets
+  - title: Using WebSockets with Undertow
     url: /guides/websockets
     type: guide
     matches: 2
diff --git a/_generated-doc/main/config/quarkus-all-config.adoc b/_generated-doc/main/config/quarkus-all-config.adoc
@@ -83977,9 +83977,9 @@ endif::add-copy-button-to-config-props[]
 --
 The name of the TLS configuration to use.
 
-If not set and the default TLS configuration is configured (`quarkus.tls.++*++`) then that will be used. If a name is configured, it uses the configuration from `quarkus.tls.<name>.++*++` If a name is configured, but no TLS configuration is found with that name then an error will be thrown.
+If a name is configured, it uses the configuration from `quarkus.tls.<name>.++*++` If a name is configured, but no TLS configuration is found with that name then an error will be thrown. The default TLS configuration will be ignored.
 
-If no TLS configuration is set, then the keys-tore, trust-store, etc. properties will be used.
+If no named TLS configuration is set, then the key-store, trust-store, etc. properties will be used.
 
 This property is not applicable to the RESTEasy Client.
 
@@ -84725,9 +84725,9 @@ endif::add-copy-button-to-config-props[]
 --
 The name of the TLS configuration to use.
 
-If not set and the default TLS configuration is configured (`quarkus.tls.++*++`) then that will be used. If a name is configured, it uses the configuration from `quarkus.tls.<name>.++*++` If a name is configured, but no TLS configuration is found with that name then an error will be thrown.
+If a name is configured, it uses the configuration from `quarkus.tls.<name>.++*++` If a name is configured, but no TLS configuration is found with that name then an error will be thrown. The default TLS configuration will be ignored.
 
-If no TLS configuration is set, then the keys-tore, trust-store, etc. properties will be used.
+If no named TLS configuration is set, then the key-store, trust-store, etc. properties will be used.
 
 This property is not applicable to the RESTEasy Client.
 
diff --git a/_generated-doc/main/config/quarkus-rest-client-config.adoc b/_generated-doc/main/config/quarkus-rest-client-config.adoc
@@ -650,9 +650,9 @@ endif::add-copy-button-to-config-props[]
 --
 The name of the TLS configuration to use.
 
-If not set and the default TLS configuration is configured (`quarkus.tls.++*++`) then that will be used. If a name is configured, it uses the configuration from `quarkus.tls.<name>.++*++` If a name is configured, but no TLS configuration is found with that name then an error will be thrown.
+If a name is configured, it uses the configuration from `quarkus.tls.<name>.++*++` If a name is configured, but no TLS configuration is found with that name then an error will be thrown. The default TLS configuration will be ignored.
 
-If no TLS configuration is set, then the keys-tore, trust-store, etc. properties will be used.
+If no named TLS configuration is set, then the key-store, trust-store, etc. properties will be used.
 
 This property is not applicable to the RESTEasy Client.
 
@@ -1398,9 +1398,9 @@ endif::add-copy-button-to-config-props[]
 --
 The name of the TLS configuration to use.
 
-If not set and the default TLS configuration is configured (`quarkus.tls.++*++`) then that will be used. If a name is configured, it uses the configuration from `quarkus.tls.<name>.++*++` If a name is configured, but no TLS configuration is found with that name then an error will be thrown.
+If a name is configured, it uses the configuration from `quarkus.tls.<name>.++*++` If a name is configured, but no TLS configuration is found with that name then an error will be thrown. The default TLS configuration will be ignored.
 
-If no TLS configuration is set, then the keys-tore, trust-store, etc. properties will be used.
+If no named TLS configuration is set, then the key-store, trust-store, etc. properties will be used.
 
 This property is not applicable to the RESTEasy Client.
 
diff --git a/_generated-doc/main/config/quarkus-rest-client-config_quarkus.rest-client.adoc b/_generated-doc/main/config/quarkus-rest-client-config_quarkus.rest-client.adoc
@@ -650,9 +650,9 @@ endif::add-copy-button-to-config-props[]
 --
 The name of the TLS configuration to use.
 
-If not set and the default TLS configuration is configured (`quarkus.tls.++*++`) then that will be used. If a name is configured, it uses the configuration from `quarkus.tls.<name>.++*++` If a name is configured, but no TLS configuration is found with that name then an error will be thrown.
+If a name is configured, it uses the configuration from `quarkus.tls.<name>.++*++` If a name is configured, but no TLS configuration is found with that name then an error will be thrown. The default TLS configuration will be ignored.
 
-If no TLS configuration is set, then the keys-tore, trust-store, etc. properties will be used.
+If no named TLS configuration is set, then the key-store, trust-store, etc. properties will be used.
 
 This property is not applicable to the RESTEasy Client.
 
@@ -1398,9 +1398,9 @@ endif::add-copy-button-to-config-props[]
 --
 The name of the TLS configuration to use.
 
-If not set and the default TLS configuration is configured (`quarkus.tls.++*++`) then that will be used. If a name is configured, it uses the configuration from `quarkus.tls.<name>.++*++` If a name is configured, but no TLS configuration is found with that name then an error will be thrown.
+If a name is configured, it uses the configuration from `quarkus.tls.<name>.++*++` If a name is configured, but no TLS configuration is found with that name then an error will be thrown. The default TLS configuration will be ignored.
 
-If no TLS configuration is set, then the keys-tore, trust-store, etc. properties will be used.
+If no named TLS configuration is set, then the key-store, trust-store, etc. properties will be used.
 
 This property is not applicable to the RESTEasy Client.
 
diff --git a/_generated-doc/main/infra/quarkus-all-build-items.adoc b/_generated-doc/main/infra/quarkus-all-build-items.adoc
@@ -9479,6 +9479,10 @@ This hold all files in the user's project root
 
 _No Javadoc found_
 
+`java.nio.file.Path rootPath` 
+
+_No Javadoc found_
+
 
 |===
 == Vert.x - HTTP - SPI
diff --git a/_versions/main/guides/building-native-image.adoc b/_versions/main/guides/building-native-image.adoc
@@ -75,10 +75,10 @@ This is particularly important when it comes to conformance and security.
 
 * Mandrel is recommended for building native executables that target Linux containerized environments.
 This means that Mandrel users are encouraged to use containers to build their native executables.
-If you are building native executables for macOS,
+If you are building native executables for macOS on amd64/x86,
 you should consider using Oracle GraalVM instead,
 because Mandrel does not currently target this platform.
-Building native executables directly on bare metal Linux or Windows is possible,
+Building native executables directly on bare metal Linux, macOS (on M processors), or Windows is possible,
 with details available in the https://github.com/graalvm/mandrel/blob/default/README.md[Mandrel README]
 and https://github.com/graalvm/mandrel/releases[Mandrel releases].
 
@@ -111,7 +111,7 @@ We recommend the _community edition_ of GraalVM. For example, install it with `s
 export GRAALVM_HOME=$HOME/Development/mandrel/
 ----
 +
-On macOS (not supported by Mandrel), point the variable to the `Home` sub-directory:
+On macOS (amd64/x86 based Macs not supported), point the variable to the `Home` sub-directory:
 +
 [source,bash]
 ----
diff --git a/_versions/main/guides/security-openid-connect-dev-services.adoc b/_versions/main/guides/security-openid-connect-dev-services.adoc
@@ -42,6 +42,11 @@ KeyCloak Dev Services Starting:
 2021-11-02 17:14:44,170 INFO  [io.qua.oid.dep.dev.key.KeycloakDevServicesProcessor] (build-10) Dev Services for Keycloak started.
 ----
 
+[NOTE]
+====
+Adding the `quarkus.keycloak.devservices.java-opts=-XX:UseSVE=0` configuration property may help to workaround Keycloak Dev Services startup problems on some Mac OS systems.
+====
+
 [IMPORTANT]
 ====
 When logging in to the Keycloak admin console, the username is `admin`, and the password is `admin`.
diff --git a/_versions/main/guides/tls-registry-reference.adoc b/_versions/main/guides/tls-registry-reference.adoc
@@ -55,6 +55,12 @@ Each named TLS configuration, or "TLS bucket," must provide its own properties.
 For instance, `quarkus.tls.reload-period` will only be applied to the default TLS configuration.
 ====
 
+[IMPORTANT]
+====
+As described in detail  link:https://github.com/quarkusio/quarkus/blob/main/adr/0004-using-the-tls-registry-for-clients.adoc#configuring-clients-with-the-tls-registry[here], Quarkus client extensions (REST, GRPC, etc) ignore properties, defined in default (ie unnamed) TLS configuration.
+The only exception is `quarkus.tls.trust-all` property.
+====
+
 === Configuring HTTPS for a HTTP server
 
 To ensure secure client-server communication, the client is often required to verify the server's authenticity.
diff --git a/_versions/main/guides/websockets-next-reference.adoc b/_versions/main/guides/websockets-next-reference.adoc
@@ -5,7 +5,6 @@ https://github.com/quarkusio/quarkus/tree/main/docs/src/main/asciidoc
 ////
 [id="websockets-next-reference-guide"]
 = WebSockets Next reference guide
-:extension-status: preview
 include::_attributes.adoc[]
 :numbered:
 :sectnums:
@@ -14,8 +13,6 @@ include::_attributes.adoc[]
 :topics: web,websockets
 :extensions: io.quarkus:quarkus-websockets-next
 
-include::{includes}/extension-status.adoc[]
-
 The `quarkus-websockets-next` extension provides a modern declarative API to define WebSocket server and client endpoints.
 
 == The WebSocket protocol
diff --git a/_versions/main/guides/websockets-next-tutorial.adoc b/_versions/main/guides/websockets-next-tutorial.adoc
@@ -14,9 +14,6 @@ include::_attributes.adoc[]
 This guide explains how your Quarkus application can utilize web sockets to create interactive web applications.
 In this guide, we will develop a very simple chat application using web sockets to receive and send messages to the other connected users.
 
-include::{includes}/extension-status.adoc[]
-
-
 == Prerequisites
 
 include::{includes}/prerequisites.adoc[]
diff --git a/_versions/main/guides/websockets.adoc b/_versions/main/guides/websockets.adoc
@@ -3,14 +3,22 @@ This guide is maintained in the main Quarkus repository
 and pull requests should be submitted there:
 https://github.com/quarkusio/quarkus/tree/main/docs/src/main/asciidoc
 ////
-= Using WebSockets
+= Using WebSockets with Undertow
 include::_attributes.adoc[]
 :categories: web
 :summary: This guide explains how your Quarkus application can utilize web sockets to create interactive web applications. Because it’s the canonical web socket application, we are going to create a simple chat application.
 :topics: web,websockets
 :extensions: io.quarkus:quarkus-websockets,io.quarkus:quarkus-websockets-client
 
-This guide explains how your Quarkus application can utilize web sockets to create interactive web applications.
+This guide explains how your Quarkus application can utilize web sockets to create interactive web applications,
+in the context of an Undertow-based Quarkus application, or if you rely on https://jakarta.ee/specifications/websocket/[Jakarta WebSocket].
+
+[TIP]
+====
+If you don't use Undertow or https://jakarta.ee/specifications/websocket/[Jakarta WebSocket],
+it is recommended to use the more modern xref:websockets-next-tutorial.adoc[WebSockets Next extensions].
+====
+
 Because it's the _canonical_ web socket application, we are going to create a simple chat application.
 
 == Prerequisites
