Sync documentation of main branch

Author: actions-user

_generated-doc/main/config/quarkus-all-config.adoc

@@ -3043,7 +3043,7 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-The base image to be used when a container image is being produced for the jar build. When the application is built against Java 21 or higher, `registry.access.redhat.com/ubi8/openjdk-21-runtime:1.20` is used as the default. Otherwise `registry.access.redhat.com/ubi8/openjdk-17-runtime:1.20` is used as the default.
+The base image to be used when a container image is being produced for the jar build. When the application is built against Java 21 or higher, `registry.access.redhat.com/ubi9/openjdk-21-runtime:1.21` is used as the default. Otherwise `registry.access.redhat.com/ubi9/openjdk-17-runtime:1.21` is used as the default.
 
 
 ifdef::add-copy-button-to-env-var[]
@@ -3064,7 +3064,7 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-The base image to be used when a container image is being produced for the native binary build. The default is "quay.io/quarkus/quarkus-micro-image". You can also use "registry.access.redhat.com/ubi8/ubi-minimal" which is a bigger base image, but provide more built-in utilities such as the microdnf package manager.
+The base image to be used when a container image is being produced for the native binary build. The default is "quay.io/quarkus/ubi9-quarkus-micro-image:2.0". You can also use "registry.access.redhat.com/ubi9/ubi-minimal" which is a bigger base image, but provide more built-in utilities such as the microdnf package manager.
 
 
 ifdef::add-copy-button-to-env-var[]
@@ -3598,7 +3598,7 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-The base image to be used when a container image is being produced for the jar build. The value of this property is used to create an ImageStream for the builder image used in the Openshift build. When it references images already available in the internal Openshift registry, the corresponding streams are used instead. When the application is built against Java 21 or higher, `registry.access.redhat.com/ubi8/openjdk-21:1.20` is used as the default. Otherwise `registry.access.redhat.com/ubi8/openjdk-17:1.20` is used as the default.
+The base image to be used when a container image is being produced for the jar build. The value of this property is used to create an ImageStream for the builder image used in the Openshift build. When it references images already available in the internal Openshift registry, the corresponding streams are used instead. When the application is built against Java 21 or higher, `registry.access.redhat.com/ubi9/openjdk-21:1.21` is used as the default. Otherwise `registry.access.redhat.com/ubi9/openjdk-17:1.21` is used as the default.
 
 
 ifdef::add-copy-button-to-env-var[]
@@ -8179,7 +8179,9 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-Defines the file encoding as in `-Dfile.encoding=...`. Native image runtime uses the host's (i.e. build time) value of `file.encoding` system property. We intentionally default this to UTF-8 to avoid platform specific defaults to be picked up which can then result in inconsistent behavior in the generated native executable.
+Defines the file encoding as in `-Dfile.encoding=...`.
+
+Native image runtime uses the host's (i.e. build time) value of `file.encoding` system property. We intentionally default this to UTF-8 to avoid platform specific defaults to be picked up which can then result in inconsistent behavior in the generated native executable.
 
 
 ifdef::add-copy-button-to-env-var[]
@@ -8498,7 +8500,16 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-The docker image to use to do the image build. It can be one of `graalvm`, `mandrel`, or the full image path, e.g. `quay.io/quarkus/ubi-quarkus-mandrel-builder-image:jdk-21`.
+The docker image to use to do the image build. It can be one of `graalvm`, `mandrel`, or the full image path, e.g. `quay.io/quarkus/ubi9-quarkus-mandrel-builder-image:jdk-21`.
+
+*Note:* Builder images are available using UBI 8 and UBI 9 base images, for example:
+
+ - UBI 8: `quay.io/quarkus/ubi-quarkus-mandrel-builder-image:jdk-21` (UBI 8)
+ - UBI 9: `quay.io/quarkus/ubi9-quarkus-mandrel-builder-image:jdk-21` (UBI 9)
+
+
+
+You need to be aware that if you use a builder image using UBI9 and you plan to build a container, you must ensure that the base image used in the container is also UBI9.
 
 
 ifdef::add-copy-button-to-env-var[]
@@ -8659,7 +8670,9 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-If errors should be reported at runtime. This is a more relaxed setting, however it is not recommended as it means your application may fail at runtime if an unsupported feature is used by accident. Note that the use of this flag may result in build time failures due to `ClassNotFoundException`s. Reason most likely being that the Quarkus extension already optimized it away or do not actually need it. In such cases you should explicitly add the corresponding dependency providing the missing classes as a dependency to your project.
+If errors should be reported at runtime. This is a more relaxed setting, however it is not recommended as it means your application may fail at runtime if an unsupported feature is used by accident.
+
+Note that the use of this flag may result in build time failures due to `ClassNotFoundException`s. Reason most likely being that the Quarkus extension already optimized it away or do not actually need it. In such cases you should explicitly add the corresponding dependency providing the missing classes as a dependency to your project.
 
 
 ifdef::add-copy-button-to-env-var[]
@@ -8680,7 +8693,11 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-Don't build a native image if it already exists. This is useful if you have already built an image and you want to use Quarkus to deploy it somewhere. Note that this is not able to detect if the existing image is outdated, if you have modified source or config and want a new image you must not use this flag.
+Don't build a native image if it already exists.
+
+This is useful if you have already built an image and you want to use Quarkus to deploy it somewhere.
+
+Note that this is not able to detect if the existing image is outdated, if you have modified source or config and want a new image you must not use this flag.
 
 
 ifdef::add-copy-button-to-env-var[]
@@ -8713,6 +8730,8 @@ Example: Given that you have `src/main/resources/ignored.png` and `src/main/reso
 quarkus.native.resources.includes = foo/**,bar/**/*.txt
 ```
 
+
+
 the files `src/main/resources/foo/selected.png` and `bar/some.txt` will be included in the native image, while `src/main/resources/ignored.png` will not be included.
 
 Supported glob features
@@ -8793,6 +8812,8 @@ quarkus.native.resources.includes = **/*.png
 quarkus.native.resources.excludes = foo/**,**/green.png
 ```
 
+
+
 the resource `red.png` will be available in the native image while the resources `foo/green.png` and `bar/blue.png` will not be available in the native image.
 
 
@@ -8900,7 +8921,9 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-Allows passing extra arguments to the UPX command line (like --brute). The arguments are comma-separated. The exhaustive list of parameters can be found in link:https://github.com/upx/upx/blob/devel/doc/upx.pod[https://github.com/upx/upx/blob/devel/doc/upx.pod].
+Allows passing extra arguments to the UPX command line (like --brute). The arguments are comma-separated.
+
+The exhaustive list of parameters can be found in link:https://github.com/upx/upx/blob/devel/doc/upx.pod[https://github.com/upx/upx/blob/devel/doc/upx.pod].
 
 
 ifdef::add-copy-button-to-env-var[]
@@ -87040,9 +87063,9 @@ endif::add-copy-button-to-env-var[]
 |Map<String,String>
 |
 
-a| [[quarkus-smallrye-health_quarkus-smallrye-health-check-check-name-enabled]] [.property-path]##link:#quarkus-smallrye-health_quarkus-smallrye-health-check-check-name-enabled[`quarkus.smallrye-health.check."check-name".enabled`]##
+a| [[quarkus-smallrye-health_quarkus-smallrye-health-check-check-classname-enabled]] [.property-path]##link:#quarkus-smallrye-health_quarkus-smallrye-health-check-check-classname-enabled[`quarkus.smallrye-health.check."check-classname".enabled`]##
 ifdef::add-copy-button-to-config-props[]
-config_property_copy_button:+++quarkus.smallrye-health.check."check-name".enabled+++[]
+config_property_copy_button:+++quarkus.smallrye-health.check."check-classname".enabled+++[]
 endif::add-copy-button-to-config-props[]
 
 
@@ -87052,10 +87075,10 @@ Whether the HealthCheck should be enabled.
 
 
 ifdef::add-copy-button-to-env-var[]
-Environment variable: env_var_with_copy_button:+++QUARKUS_SMALLRYE_HEALTH_CHECK__CHECK_NAME__ENABLED+++[]
+Environment variable: env_var_with_copy_button:+++QUARKUS_SMALLRYE_HEALTH_CHECK__CHECK_CLASSNAME__ENABLED+++[]
 endif::add-copy-button-to-env-var[]
 ifndef::add-copy-button-to-env-var[]
-Environment variable: `+++QUARKUS_SMALLRYE_HEALTH_CHECK__CHECK_NAME__ENABLED+++`
+Environment variable: `+++QUARKUS_SMALLRYE_HEALTH_CHECK__CHECK_CLASSNAME__ENABLED+++`
 endif::add-copy-button-to-env-var[]
 --
 |boolean

_generated-doc/main/config/quarkus-container-image-jib.adoc

@@ -15,7 +15,7 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-The base image to be used when a container image is being produced for the jar build. When the application is built against Java 21 or higher, `registry.access.redhat.com/ubi8/openjdk-21-runtime:1.20` is used as the default. Otherwise `registry.access.redhat.com/ubi8/openjdk-17-runtime:1.20` is used as the default.
+The base image to be used when a container image is being produced for the jar build. When the application is built against Java 21 or higher, `registry.access.redhat.com/ubi9/openjdk-21-runtime:1.21` is used as the default. Otherwise `registry.access.redhat.com/ubi9/openjdk-17-runtime:1.21` is used as the default.
 
 
 ifdef::add-copy-button-to-env-var[]
@@ -36,7 +36,7 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-The base image to be used when a container image is being produced for the native binary build. The default is "quay.io/quarkus/quarkus-micro-image". You can also use "registry.access.redhat.com/ubi8/ubi-minimal" which is a bigger base image, but provide more built-in utilities such as the microdnf package manager.
+The base image to be used when a container image is being produced for the native binary build. The default is "quay.io/quarkus/ubi9-quarkus-micro-image:2.0". You can also use "registry.access.redhat.com/ubi9/ubi-minimal" which is a bigger base image, but provide more built-in utilities such as the microdnf package manager.
 
 
 ifdef::add-copy-button-to-env-var[]

_generated-doc/main/config/quarkus-container-image-jib_quarkus.jib.adoc

@@ -15,7 +15,7 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-The base image to be used when a container image is being produced for the jar build. When the application is built against Java 21 or higher, `registry.access.redhat.com/ubi8/openjdk-21-runtime:1.20` is used as the default. Otherwise `registry.access.redhat.com/ubi8/openjdk-17-runtime:1.20` is used as the default.
+The base image to be used when a container image is being produced for the jar build. When the application is built against Java 21 or higher, `registry.access.redhat.com/ubi9/openjdk-21-runtime:1.21` is used as the default. Otherwise `registry.access.redhat.com/ubi9/openjdk-17-runtime:1.21` is used as the default.
 
 
 ifdef::add-copy-button-to-env-var[]
@@ -36,7 +36,7 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-The base image to be used when a container image is being produced for the native binary build. The default is "quay.io/quarkus/quarkus-micro-image". You can also use "registry.access.redhat.com/ubi8/ubi-minimal" which is a bigger base image, but provide more built-in utilities such as the microdnf package manager.
+The base image to be used when a container image is being produced for the native binary build. The default is "quay.io/quarkus/ubi9-quarkus-micro-image:2.0". You can also use "registry.access.redhat.com/ubi9/ubi-minimal" which is a bigger base image, but provide more built-in utilities such as the microdnf package manager.
 
 
 ifdef::add-copy-button-to-env-var[]

_generated-doc/main/config/quarkus-container-image-openshift.adoc

@@ -36,7 +36,7 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-The base image to be used when a container image is being produced for the jar build. The value of this property is used to create an ImageStream for the builder image used in the Openshift build. When it references images already available in the internal Openshift registry, the corresponding streams are used instead. When the application is built against Java 21 or higher, `registry.access.redhat.com/ubi8/openjdk-21:1.20` is used as the default. Otherwise `registry.access.redhat.com/ubi8/openjdk-17:1.20` is used as the default.
+The base image to be used when a container image is being produced for the jar build. The value of this property is used to create an ImageStream for the builder image used in the Openshift build. When it references images already available in the internal Openshift registry, the corresponding streams are used instead. When the application is built against Java 21 or higher, `registry.access.redhat.com/ubi9/openjdk-21:1.21` is used as the default. Otherwise `registry.access.redhat.com/ubi9/openjdk-17:1.21` is used as the default.
 
 
 ifdef::add-copy-button-to-env-var[]

_generated-doc/main/config/quarkus-container-image-openshift_quarkus.openshift.adoc

@@ -36,7 +36,7 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-The base image to be used when a container image is being produced for the jar build. The value of this property is used to create an ImageStream for the builder image used in the Openshift build. When it references images already available in the internal Openshift registry, the corresponding streams are used instead. When the application is built against Java 21 or higher, `registry.access.redhat.com/ubi8/openjdk-21:1.20` is used as the default. Otherwise `registry.access.redhat.com/ubi8/openjdk-17:1.20` is used as the default.
+The base image to be used when a container image is being produced for the jar build. The value of this property is used to create an ImageStream for the builder image used in the Openshift build. When it references images already available in the internal Openshift registry, the corresponding streams are used instead. When the application is built against Java 21 or higher, `registry.access.redhat.com/ubi9/openjdk-21:1.21` is used as the default. Otherwise `registry.access.redhat.com/ubi9/openjdk-17:1.21` is used as the default.
 
 
 ifdef::add-copy-button-to-env-var[]

_generated-doc/main/config/quarkus-core_quarkus.native.adoc

@@ -141,7 +141,9 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-Defines the file encoding as in `-Dfile.encoding=...`. Native image runtime uses the host's (i.e. build time) value of `file.encoding` system property. We intentionally default this to UTF-8 to avoid platform specific defaults to be picked up which can then result in inconsistent behavior in the generated native executable.
+Defines the file encoding as in `-Dfile.encoding=...`.
+
+Native image runtime uses the host's (i.e. build time) value of `file.encoding` system property. We intentionally default this to UTF-8 to avoid platform specific defaults to be picked up which can then result in inconsistent behavior in the generated native executable.
 
 
 ifdef::add-copy-button-to-env-var[]
@@ -460,7 +462,16 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-The docker image to use to do the image build. It can be one of `graalvm`, `mandrel`, or the full image path, e.g. `quay.io/quarkus/ubi-quarkus-mandrel-builder-image:jdk-21`.
+The docker image to use to do the image build. It can be one of `graalvm`, `mandrel`, or the full image path, e.g. `quay.io/quarkus/ubi9-quarkus-mandrel-builder-image:jdk-21`.
+
+*Note:* Builder images are available using UBI 8 and UBI 9 base images, for example:
+
+ - UBI 8: `quay.io/quarkus/ubi-quarkus-mandrel-builder-image:jdk-21` (UBI 8)
+ - UBI 9: `quay.io/quarkus/ubi9-quarkus-mandrel-builder-image:jdk-21` (UBI 9)
+
+
+
+You need to be aware that if you use a builder image using UBI9 and you plan to build a container, you must ensure that the base image used in the container is also UBI9.
 
 
 ifdef::add-copy-button-to-env-var[]
@@ -621,7 +632,9 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-If errors should be reported at runtime. This is a more relaxed setting, however it is not recommended as it means your application may fail at runtime if an unsupported feature is used by accident. Note that the use of this flag may result in build time failures due to `ClassNotFoundException`s. Reason most likely being that the Quarkus extension already optimized it away or do not actually need it. In such cases you should explicitly add the corresponding dependency providing the missing classes as a dependency to your project.
+If errors should be reported at runtime. This is a more relaxed setting, however it is not recommended as it means your application may fail at runtime if an unsupported feature is used by accident.
+
+Note that the use of this flag may result in build time failures due to `ClassNotFoundException`s. Reason most likely being that the Quarkus extension already optimized it away or do not actually need it. In such cases you should explicitly add the corresponding dependency providing the missing classes as a dependency to your project.
 
 
 ifdef::add-copy-button-to-env-var[]
@@ -642,7 +655,11 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-Don't build a native image if it already exists. This is useful if you have already built an image and you want to use Quarkus to deploy it somewhere. Note that this is not able to detect if the existing image is outdated, if you have modified source or config and want a new image you must not use this flag.
+Don't build a native image if it already exists.
+
+This is useful if you have already built an image and you want to use Quarkus to deploy it somewhere.
+
+Note that this is not able to detect if the existing image is outdated, if you have modified source or config and want a new image you must not use this flag.
 
 
 ifdef::add-copy-button-to-env-var[]
@@ -675,6 +692,8 @@ Example: Given that you have `src/main/resources/ignored.png` and `src/main/reso
 quarkus.native.resources.includes = foo/**,bar/**/*.txt
 ```
 
+
+
 the files `src/main/resources/foo/selected.png` and `bar/some.txt` will be included in the native image, while `src/main/resources/ignored.png` will not be included.
 
 Supported glob features
@@ -755,6 +774,8 @@ quarkus.native.resources.includes = **/*.png
 quarkus.native.resources.excludes = foo/**,**/green.png
 ```
 
+
+
 the resource `red.png` will be available in the native image while the resources `foo/green.png` and `bar/blue.png` will not be available in the native image.
 
 
@@ -862,7 +883,9 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-Allows passing extra arguments to the UPX command line (like --brute). The arguments are comma-separated. The exhaustive list of parameters can be found in link:https://github.com/upx/upx/blob/devel/doc/upx.pod[https://github.com/upx/upx/blob/devel/doc/upx.pod].
+Allows passing extra arguments to the UPX command line (like --brute). The arguments are comma-separated.
+
+The exhaustive list of parameters can be found in link:https://github.com/upx/upx/blob/devel/doc/upx.pod[https://github.com/upx/upx/blob/devel/doc/upx.pod].
 
 
 ifdef::add-copy-button-to-env-var[]