Sync web site with Quarkus documentation

quarkusbot · quarkusbot · commit 3492d953642b · 2025-05-07T15:30:06.000Z
diff --git a/_data/versioned/latest/index/quarkus.yaml b/_data/versioned/latest/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/latest/index/relations.yaml b/_data/versioned/latest/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/latest/config/quarkus-all-config.adoc b/_generated-doc/latest/config/quarkus-all-config.adoc
@@ -1522,7 +1522,7 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-If set to true then the dependency graphs are generated and available in the Dev UI.
+If set to `true` then the dependency graphs are generated and available in the Dev UI. If set to `auto` then the dependency graphs are generated if there's less than 1000 beans in the application. If set to `false` the dependency graphs are not generated.
 
 
 ifdef::add-copy-button-to-env-var[]
@@ -1532,8 +1532,8 @@ ifndef::add-copy-button-to-env-var[]
 Environment variable: `+++QUARKUS_ARC_DEV_MODE_GENERATE_DEPENDENCY_GRAPHS+++`
 endif::add-copy-button-to-env-var[]
 --
-|boolean
-|`true`
+a|`true`, `false`, `auto`
+|`auto`
 
 a|icon:lock[title=Fixed at build time] [[quarkus-arc_quarkus-arc-test-disable-application-lifecycle-observers]] [.property-path]##link:#quarkus-arc_quarkus-arc-test-disable-application-lifecycle-observers[`quarkus.arc.test.disable-application-lifecycle-observers`]##
 ifdef::add-copy-button-to-config-props[]
@@ -83942,10 +83942,12 @@ 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.
 
 If no TLS configuration is set, then the keys-tore, trust-store, etc. properties will be used.
 
+The default TLS configuration is *not* used by default.
+
 This property is not applicable to the RESTEasy Client.
 
 
@@ -84690,10 +84692,12 @@ 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.
 
 If no TLS configuration is set, then the keys-tore, trust-store, etc. properties will be used.
 
+The default TLS configuration is *not* used by default.
+
 This property is not applicable to the RESTEasy Client.
 
 
@@ -90887,7 +90891,7 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-Set this boolean value to enable the merging of the deprecated `@Schema` `example` property into the `examples` array introduced in OAS 3.1.0. If not set, it will default to `false` and the deprecated `example` will be kept as a separate annotation on the schema in the OpenAPI model.
+Set this boolean value to enable or disable the merging of the deprecated `@Schema` `example` property into the `examples` array introduced in OAS 3.1.0. If set to `false`, the deprecated `example` will be kept as a separate annotation on the schema in the OpenAPI model.
 
 
 ifdef::add-copy-button-to-env-var[]
@@ -90898,7 +90902,7 @@ Environment variable: `+++QUARKUS_SMALLRYE_OPENAPI_MERGE_SCHEMA_EXAMPLES+++`
 endif::add-copy-button-to-env-var[]
 --
 |boolean
-|`false`
+|`true`
 
 a| [[quarkus-smallrye-openapi_quarkus-smallrye-openapi-enable]] [.property-path]##link:#quarkus-smallrye-openapi_quarkus-smallrye-openapi-enable[`quarkus.smallrye-openapi.enable`]##
 ifdef::add-copy-button-to-config-props[]
diff --git a/_generated-doc/latest/config/quarkus-arc.adoc b/_generated-doc/latest/config/quarkus-arc.adoc
@@ -409,7 +409,7 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-If set to true then the dependency graphs are generated and available in the Dev UI.
+If set to `true` then the dependency graphs are generated and available in the Dev UI. If set to `auto` then the dependency graphs are generated if there's less than 1000 beans in the application. If set to `false` the dependency graphs are not generated.
 
 
 ifdef::add-copy-button-to-env-var[]
@@ -419,8 +419,8 @@ ifndef::add-copy-button-to-env-var[]
 Environment variable: `+++QUARKUS_ARC_DEV_MODE_GENERATE_DEPENDENCY_GRAPHS+++`
 endif::add-copy-button-to-env-var[]
 --
-|boolean
-|`true`
+a|`true`, `false`, `auto`
+|`auto`
 
 a|icon:lock[title=Fixed at build time] [[quarkus-arc_quarkus-arc-test-disable-application-lifecycle-observers]] [.property-path]##link:#quarkus-arc_quarkus-arc-test-disable-application-lifecycle-observers[`quarkus.arc.test.disable-application-lifecycle-observers`]##
 ifdef::add-copy-button-to-config-props[]
diff --git a/_generated-doc/latest/config/quarkus-arc_quarkus.arc.adoc b/_generated-doc/latest/config/quarkus-arc_quarkus.arc.adoc
@@ -409,7 +409,7 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-If set to true then the dependency graphs are generated and available in the Dev UI.
+If set to `true` then the dependency graphs are generated and available in the Dev UI. If set to `auto` then the dependency graphs are generated if there's less than 1000 beans in the application. If set to `false` the dependency graphs are not generated.
 
 
 ifdef::add-copy-button-to-env-var[]
@@ -419,8 +419,8 @@ ifndef::add-copy-button-to-env-var[]
 Environment variable: `+++QUARKUS_ARC_DEV_MODE_GENERATE_DEPENDENCY_GRAPHS+++`
 endif::add-copy-button-to-env-var[]
 --
-|boolean
-|`true`
+a|`true`, `false`, `auto`
+|`auto`
 
 a|icon:lock[title=Fixed at build time] [[quarkus-arc_quarkus-arc-test-disable-application-lifecycle-observers]] [.property-path]##link:#quarkus-arc_quarkus-arc-test-disable-application-lifecycle-observers[`quarkus.arc.test.disable-application-lifecycle-observers`]##
 ifdef::add-copy-button-to-config-props[]
diff --git a/_generated-doc/latest/config/quarkus-rest-client-config.adoc b/_generated-doc/latest/config/quarkus-rest-client-config.adoc
@@ -650,10 +650,12 @@ 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.
 
 If no TLS configuration is set, then the keys-tore, trust-store, etc. properties will be used.
 
+The default TLS configuration is *not* used by default.
+
 This property is not applicable to the RESTEasy Client.
 
 
@@ -1398,10 +1400,12 @@ 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.
 
 If no TLS configuration is set, then the keys-tore, trust-store, etc. properties will be used.
 
+The default TLS configuration is *not* used by default.
+
 This property is not applicable to the RESTEasy Client.
 
 
diff --git a/_generated-doc/latest/config/quarkus-rest-client-config_quarkus.rest-client.adoc b/_generated-doc/latest/config/quarkus-rest-client-config_quarkus.rest-client.adoc
@@ -650,10 +650,12 @@ 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.
 
 If no TLS configuration is set, then the keys-tore, trust-store, etc. properties will be used.
 
+The default TLS configuration is *not* used by default.
+
 This property is not applicable to the RESTEasy Client.
 
 
@@ -1398,10 +1400,12 @@ 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.
 
 If no TLS configuration is set, then the keys-tore, trust-store, etc. properties will be used.
 
+The default TLS configuration is *not* used by default.
+
 This property is not applicable to the RESTEasy Client.
 
 
diff --git a/_generated-doc/latest/config/quarkus-smallrye-openapi.adoc b/_generated-doc/latest/config/quarkus-smallrye-openapi.adoc
@@ -834,7 +834,7 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-Set this boolean value to enable the merging of the deprecated `@Schema` `example` property into the `examples` array introduced in OAS 3.1.0. If not set, it will default to `false` and the deprecated `example` will be kept as a separate annotation on the schema in the OpenAPI model.
+Set this boolean value to enable or disable the merging of the deprecated `@Schema` `example` property into the `examples` array introduced in OAS 3.1.0. If set to `false`, the deprecated `example` will be kept as a separate annotation on the schema in the OpenAPI model.
 
 
 ifdef::add-copy-button-to-env-var[]
@@ -845,7 +845,7 @@ Environment variable: `+++QUARKUS_SMALLRYE_OPENAPI_MERGE_SCHEMA_EXAMPLES+++`
 endif::add-copy-button-to-env-var[]
 --
 |boolean
-|`false`
+|`true`
 
 a| [[quarkus-smallrye-openapi_quarkus-smallrye-openapi-enable]] [.property-path]##link:#quarkus-smallrye-openapi_quarkus-smallrye-openapi-enable[`quarkus.smallrye-openapi.enable`]##
 ifdef::add-copy-button-to-config-props[]
diff --git a/_generated-doc/latest/config/quarkus-smallrye-openapi_quarkus.smallrye-openapi.adoc b/_generated-doc/latest/config/quarkus-smallrye-openapi_quarkus.smallrye-openapi.adoc
@@ -834,7 +834,7 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-Set this boolean value to enable the merging of the deprecated `@Schema` `example` property into the `examples` array introduced in OAS 3.1.0. If not set, it will default to `false` and the deprecated `example` will be kept as a separate annotation on the schema in the OpenAPI model.
+Set this boolean value to enable or disable the merging of the deprecated `@Schema` `example` property into the `examples` array introduced in OAS 3.1.0. If set to `false`, the deprecated `example` will be kept as a separate annotation on the schema in the OpenAPI model.
 
 
 ifdef::add-copy-button-to-env-var[]
@@ -845,7 +845,7 @@ Environment variable: `+++QUARKUS_SMALLRYE_OPENAPI_MERGE_SCHEMA_EXAMPLES+++`
 endif::add-copy-button-to-env-var[]
 --
 |boolean
-|`false`
+|`true`
 
 a| [[quarkus-smallrye-openapi_quarkus-smallrye-openapi-enable]] [.property-path]##link:#quarkus-smallrye-openapi_quarkus-smallrye-openapi-enable[`quarkus.smallrye-openapi.enable`]##
 ifdef::add-copy-button-to-config-props[]
diff --git a/_generated-doc/latest/infra/quarkus-all-build-items.adoc b/_generated-doc/latest/infra/quarkus-all-build-items.adoc
@@ -9441,6 +9441,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/_guides/_attributes.adoc b/_guides/_attributes.adoc
@@ -1,7 +1,7 @@
 // Common attributes.
 // --> No blank lines (it ends the document header)
 :project-name: Quarkus
-:quarkus-version: 3.22.1
+:quarkus-version: 3.22.2
 :quarkus-platform-groupid: io.quarkus.platform
 // .
 :maven-version: 3.9.9
diff --git a/_guides/_includes/extension-status.adoc b/_guides/_includes/extension-status.adoc
@@ -1,3 +1,4 @@
+ifdef::extension-status[]
 [NOTE]
 ====
 This technology is considered {extension-status}.
@@ -21,3 +22,4 @@ endif::[]
 
 For a full list of possible statuses, check our https://quarkus.io/faq/#what-are-the-extension-statuses[FAQ entry].
 ====
+endif::[]
diff --git a/_guides/building-native-image.adoc b/_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/_guides/deploying-to-openshift-docker-howto.adoc b/_guides/deploying-to-openshift-docker-howto.adoc
@@ -145,7 +145,7 @@ openshift-helloworld   openshift-helloworld-username-dev.apps.sandbox-m2.ll9k.p1
 Be aware that the route is now listening on port 80 and is no longer on port 8080.
 ====
 +
-You can test the application demonstrated in this example with a web browser or a terminal by using `curl` and the complete URL output from `oc get routes`, that is, "\http://openshift-helloworld-username-dev.apps.sandbox-m2.ll9k.p1.openshiftapps.com".
+You can test the application demonstrated in this example with a web browser or a terminal by using `curl` and the complete URL output from `oc get routes`, that is, `\http://openshift-helloworld-username-dev.apps.sandbox-m2.ll9k.p1.openshiftapps.com`.
 +
 For example: `curl \http://openshift-helloworld-username-dev.apps.sandbox-m2.ll9k.p1.openshiftapps.com`.
 
diff --git a/_guides/getting-started-testing.adoc b/_guides/getting-started-testing.adoc
@@ -1431,7 +1431,7 @@ An example use of this could be the following Maven command, that forces `@Quark
 ./mvnw verify -Dquarkus.http.test-host=1.2.3.4 -Dquarkus.http.test-port=4321
 ----
 
-To test against a running instance that only accepts SSL/TLS connection (example: `https://1.2.3.4:4321`) set the system property `quarkus.http.test-ssl-enabled` to `true`.
+To test against a running instance that only accepts SSL/TLS connection (example: `https://1.2.3.4:4321`) set the system property `quarkus.http.test-ssl-enabled` to `true` and `quarkus.http.test-ssl-port` to the target HTTPS port.
 
 == Mixing `@QuarkusTest` with other type of tests
 
diff --git a/_guides/security-openid-connect-dev-services.adoc b/_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/_guides/tls-registry-reference.adoc b/_guides/tls-registry-reference.adoc
@@ -849,7 +849,8 @@ quarkus.tls.http.key-store.pem.0.key=tls.key
 [IMPORTANT]
 ====
 Impacted servers and clients may need to listen to the `CertificateUpdatedEvent` to apply the new certificates.
-This is automatically done for the Quarkus HTTP server, such as the Quarkus REST server, gRPC server, and WebSocket server, as well as the management interface if it is enabled.
+This is automatically done for the Quarkus HTTP server, as well as the Quarkus REST server, gRPC server, and WebSocket server, as well as the management interface if it is enabled.
+On the client side, Quarkus REST Client automatically handles certificate update events.
 ====
 
 NOTE: In Quarkus dev mode, when files are touched, it will trigger the `CertificateUpdatedEvent` much more frequently.
diff --git a/_guides/websockets-next-reference.adoc b/_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/_guides/websockets-next-tutorial.adoc b/_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/_guides/websockets.adoc b/_guides/websockets.adoc
