Sync web site with Quarkus documentation

quarkusbot · quarkusbot · commit 0ae7c5ec91ba · 2025-09-24T06:05:10.000Z
diff --git a/_generated-doc/3.20/config/quarkus-all-config.adoc b/_generated-doc/3.20/config/quarkus-all-config.adoc
@@ -71471,7 +71471,7 @@ Enable metrics with OpenTelemetry.
 
 This property is not available in the Open Telemetry SDK. It's Quarkus specific.
 
-Support for metrics will be enabled if OpenTelemetry support is enabled and either this value is true, or this value is unset.
+Support for OpenTelemetry Metrics will be enabled if this value is true. The OpenTelemetry SDK ( `io.quarkus.opentelemetry.runtime.config.build.OTelBuildConfig++#++enabled()` ) is enabled by default and if disabled, OpenTelemetry Metrics will also be disabled.
 
 
 ifdef::add-copy-button-to-env-var[]
@@ -71517,7 +71517,7 @@ Enable logs with OpenTelemetry.
 
 This property is not available in the Open Telemetry SDK. It's Quarkus specific.
 
-Support for logs will be enabled if OpenTelemetry support is enabled and either this value is true, or this value is unset.
+Support for OpenTelemetry Logs will be enabled if this value is true. The OpenTelemetry SDK ( `io.quarkus.opentelemetry.runtime.config.build.OTelBuildConfig++#++enabled()` ) is enabled by default and if disabled, OpenTelemetry Logs will also be disabled.
 
 
 ifdef::add-copy-button-to-env-var[]
@@ -88370,7 +88370,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[]
@@ -88381,7 +88381,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/3.20/config/quarkus-opentelemetry.adoc b/_generated-doc/3.20/config/quarkus-opentelemetry.adoc
@@ -138,7 +138,7 @@ Enable metrics with OpenTelemetry.
 
 This property is not available in the Open Telemetry SDK. It's Quarkus specific.
 
-Support for metrics will be enabled if OpenTelemetry support is enabled and either this value is true, or this value is unset.
+Support for OpenTelemetry Metrics will be enabled if this value is true. The OpenTelemetry SDK ( `io.quarkus.opentelemetry.runtime.config.build.OTelBuildConfig++#++enabled()` ) is enabled by default and if disabled, OpenTelemetry Metrics will also be disabled.
 
 
 ifdef::add-copy-button-to-env-var[]
@@ -184,7 +184,7 @@ Enable logs with OpenTelemetry.
 
 This property is not available in the Open Telemetry SDK. It's Quarkus specific.
 
-Support for logs will be enabled if OpenTelemetry support is enabled and either this value is true, or this value is unset.
+Support for OpenTelemetry Logs will be enabled if this value is true. The OpenTelemetry SDK ( `io.quarkus.opentelemetry.runtime.config.build.OTelBuildConfig++#++enabled()` ) is enabled by default and if disabled, OpenTelemetry Logs will also be disabled.
 
 
 ifdef::add-copy-button-to-env-var[]
diff --git a/_generated-doc/3.20/config/quarkus-opentelemetry_quarkus.otel.adoc b/_generated-doc/3.20/config/quarkus-opentelemetry_quarkus.otel.adoc
@@ -138,7 +138,7 @@ Enable metrics with OpenTelemetry.
 
 This property is not available in the Open Telemetry SDK. It's Quarkus specific.
 
-Support for metrics will be enabled if OpenTelemetry support is enabled and either this value is true, or this value is unset.
+Support for OpenTelemetry Metrics will be enabled if this value is true. The OpenTelemetry SDK ( `io.quarkus.opentelemetry.runtime.config.build.OTelBuildConfig++#++enabled()` ) is enabled by default and if disabled, OpenTelemetry Metrics will also be disabled.
 
 
 ifdef::add-copy-button-to-env-var[]
@@ -184,7 +184,7 @@ Enable logs with OpenTelemetry.
 
 This property is not available in the Open Telemetry SDK. It's Quarkus specific.
 
-Support for logs will be enabled if OpenTelemetry support is enabled and either this value is true, or this value is unset.
+Support for OpenTelemetry Logs will be enabled if this value is true. The OpenTelemetry SDK ( `io.quarkus.opentelemetry.runtime.config.build.OTelBuildConfig++#++enabled()` ) is enabled by default and if disabled, OpenTelemetry Logs will also be disabled.
 
 
 ifdef::add-copy-button-to-env-var[]
diff --git a/_generated-doc/3.20/config/quarkus-smallrye-openapi.adoc b/_generated-doc/3.20/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/3.20/config/quarkus-smallrye-openapi_quarkus.smallrye-openapi.adoc b/_generated-doc/3.20/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/3.20/infra/quarkus-all-build-items.adoc b/_generated-doc/3.20/infra/quarkus-all-build-items.adoc
@@ -9453,7 +9453,7 @@ a| https://github.com/quarkusio/quarkus/blob/main/extensions/vertx-http/deployme
 This build item aims to be used by extensions to generate static resources. 
 Those resources will be served on the given `GeneratedStaticResourceBuildItem#endpoint` . It is NOT necessary to create the file on disk. 
 Behind the scenes the build step will take care of add those resources to the final build, through `AdditionalStaticResourceBuildItem` , `NativeImageResourceBuildItem` and `io.quarkus.deployment.builditem.GeneratedResourceBuildItem` build items. 
-The value of `endpoint` should be prefixed with `'/'` .
+The value of `endpoint` should be prefixed with `'/'` and reference a file (no trailing `/`).
 -- a|`java.lang.String endpoint` 
 
 _No Javadoc found_
diff --git a/_versions/3.20/guides/_attributes.adoc b/_versions/3.20/guides/_attributes.adoc
@@ -1,7 +1,7 @@
 // Common attributes.
 // --> No blank lines (it ends the document header)
 :project-name: Quarkus
-:quarkus-version: 3.20.2.1
+:quarkus-version: 3.20.3
 :quarkus-platform-groupid: io.quarkus.platform
 // .
 :maven-version: 3.9.9
diff --git a/_versions/3.20/guides/container-image.adoc b/_versions/3.20/guides/container-image.adoc
@@ -150,7 +150,7 @@ For example, building multi-platform images is implemented differently for Docke
 === OpenShift
 
 The extension `quarkus-container-image-openshift` is using OpenShift binary builds in order to perform container builds inside the OpenShift cluster.
-The idea behind the binary build is that you just upload the artifact and its dependencies to the cluster and during the build they will be merged to a builder image (defaults to `fabric8/s2i-java`).
+The idea behind the binary build is that you just upload the artifact and its dependencies to the cluster and during the build they will be merged to a builder image (defaults to `ubi9/openjdk-17` or `ubi9/openjdk-21`).
 
 The benefit of this approach, is that it can be combined with OpenShift's `DeploymentConfig` that makes it easy to roll out changes to the cluster.
 
diff --git a/_versions/3.20/guides/deploying-to-openshift.adoc b/_versions/3.20/guides/deploying-to-openshift.adoc
@@ -483,7 +483,7 @@ quarkus.openshift.cron-job.schedule=0 * * * *
 ----
 
 IMPORTANT: CronJob resources require the https://en.wikipedia.org/wiki/Cron[Cron] expression to specify when to launch the job through the `quarkus.openshift.cron-job.schedule` property.
-If thet are not provided, the build fails.
+If they are not provided, the build fails.
 
 You can configure the rest of the Kubernetes CronJob configuration by using the properties under `quarkus.openshift.cron-job.xxx` (for more information, see xref:deploying-to-openshift.adoc#quarkus-kubernetes_quarkus-openshift-cron-job-parallelism[quarkus.openshift.cron-job.parallelism]).
 
diff --git a/_versions/3.20/guides/rest-client.adoc b/_versions/3.20/guides/rest-client.adoc
@@ -1382,7 +1382,7 @@ public class MyResponseExceptionMapper implements ResponseExceptionMapper<Runtim
     @Override
     public RuntimeException toThrowable(Response response) {
         if (response.getStatus() == 500) {
-            throw new RuntimeException("The remote service responded with HTTP 500");
+            return new RuntimeException("The remote service responded with HTTP 500");
         }
         return null;
     }
@@ -1392,7 +1392,7 @@ public class MyResponseExceptionMapper implements ResponseExceptionMapper<Runtim
 `ResponseExceptionMapper` also defines the `getPriority` method which is used in order to determine the priority with which `ResponseExceptionMapper` implementations will be called (implementations with a lower value for `getPriority` will be invoked first).
 If `toThrowable` returns an exception, then that exception will be thrown. If `null` is returned, the next implementation of `ResponseExceptionMapper` in the chain will be called (if there is any).
 
-The class as written above, would not be automatically be used by any REST Client. To make it available to every REST Client of the application, the class needs to be annotated with `@Provider` (as long as `quarkus.rest-client.provider-autodiscovery` is not set to `false`).
+The class as written above, would not be automatically used by any REST Client. To make it available to every REST Client of the application, the class needs to be annotated with `@Provider` (as long as `quarkus.rest-client.provider-autodiscovery` is not set to `false`).
 Alternatively, if the exception handling class should only apply to specific REST Client interfaces, you can either annotate the interfaces with `@RegisterProvider(MyResponseExceptionMapper.class)`, or register it using configuration using the `providers` property of the proper `quarkus.rest-client` configuration group.
 
 === Using @ClientExceptionMapper
diff --git a/_versions/3.20/guides/security-jwt-build.adoc b/_versions/3.20/guides/security-jwt-build.adoc
@@ -370,7 +370,7 @@ SmallRye JWT supports the following properties, which can be used to customize h
 |`smallrye.jwt.new-token.issuer` |none |Token issuer used to set an `iss` (issuer) claim value if this claim has not already been set.
 |`smallrye.jwt.new-token.audience` |none |Token audience used to set an `aud` (audience) claim value if this claim has not already been set.
 |`smallrye.jwt.new-token.override-matching-claims` |`false` | Set this property to `true` for `smallrye.jwt.new-token.issuer` and `smallrye.jwt.new-token.audience` values to override the already initialized `iss` (issuer) and `aud` (audience) claims.
-|smallrye.jwt.new-token.add-default-claims|true|Set this property to `false` to disable an automatic addition of the `iat` (issued at), `exp` (expiration time) and `jti` (token identifier) claims when such claims have not already been set.
+|`smallrye.jwt.new-token.add-default-claims`|true|Set this property to `false` to disable an automatic addition of the `iat` (issued at), `exp` (expiration time) and `jti` (token identifier) claims when such claims have not already been set.
 |`smallrye.jwt.keystore.type` |`JKS` |This property can be used to customize a keystore type if either `smallrye.jwt.sign.key.location` or `smallrye.jwt.encrypt.key.location` or both of these properties point to a `KeyStore` file. If it is not set then the file name will be checked to determine the keystore type before defaulting to `JKS`.
 |`smallrye.jwt.keystore.provider` | |This property can be used to customize a `KeyStore` provider if `smallrye.jwt.sign.key.location` or `smallrye.jwt.encrypt.key.location` point to a `KeyStore` file.
 |`smallrye.jwt.keystore.password` | |Keystore password. If `smallrye.jwt.sign.key.location` or `smallrye.jwt.encrypt.key.location` point to a `KeyStore` file, this property must be set.
diff --git a/_versions/3.20/guides/security-openid-connect-client-reference.adoc b/_versions/3.20/guides/security-openid-connect-client-reference.adoc
@@ -1295,7 +1295,7 @@ quarkus.oidc-client.credentials.secret=secret
 quarkus.oidc-client.grant.type=exchange
 quarkus.oidc-client.grant-options.exchange.audience=quarkus-app-exchange
 
-quarkus.resteasy-client-oidc-token-propagation.exchange-token=true <1>
+quarkus.rest-client-oidc-token-propagation.exchange-token=true <1>
 ----
 <1> Please note that the `exchange-token` configuration property is ignored when the OidcClient name is set with the `io.quarkus.oidc.token.propagation.common.AccessToken#exchangeTokenClient` annotation attribute.
 
diff --git a/_versions/3.20/guides/smallrye-fault-tolerance.adoc b/_versions/3.20/guides/smallrye-fault-tolerance.adoc
@@ -576,7 +576,7 @@ implementation("io.quarkus:quarkus-smallrye-fault-tolerance")
 == Additional resources
 
 SmallRye Fault Tolerance has more features than shown here.
-Please check the link:https://smallrye.io/docs/smallrye-fault-tolerance/6.9.0/index.html[SmallRye Fault Tolerance documentation] to learn about them.
+Please check the link:https://smallrye.io/docs/smallrye-fault-tolerance/6.9.2/index.html[SmallRye Fault Tolerance documentation] to learn about them.
 
 In Quarkus, you can use the SmallRye Fault Tolerance optional features out of the box.
 
@@ -608,7 +608,7 @@ quarkus.fault-tolerance.mp-compatibility=true
 ----
 ====
 
-The link:https://smallrye.io/docs/smallrye-fault-tolerance/6.9.0/reference/programmatic-api.html[programmatic API] is present and integrated with the declarative, annotation-based API.
+The link:https://smallrye.io/docs/smallrye-fault-tolerance/6.9.2/reference/programmatic-api.html[programmatic API] is present and integrated with the declarative, annotation-based API.
 You can use the `Guard`, `TypedGuard` and `@ApplyGuard` APIs out of the box.
 
 Support for Kotlin is present (assuming you use the Quarkus extension for Kotlin), so you can guard your `suspend` functions with fault tolerance annotations.
