Sync web site with Quarkus documentation

quarkusbot · quarkusbot · commit 6999d95718e9 · 2025-03-12T16:32:44.000Z
diff --git a/_data/versioned/latest/index/quarkus.yaml b/_data/versioned/latest/index/quarkus.yaml
@@ -769,7 +769,7 @@ types:
     url: /guides/extension-writing-dev-service
   - title: YAML configuration
     filename: config-yaml.adoc
-    summary: "Optionally, use `application.yaml` instead of `application.properties` to configure your application."
+    summary: "Optionally, use application.yaml instead of application.properties to configure your application."
     categories: core
     topics:
     - configuration
@@ -996,7 +996,7 @@ types:
     url: /guides/aws-lambda-http
   - title: Accessing application properties with Spring Boot properties API
     filename: spring-boot-properties.adoc
-    summary: Use Spring Boot's `@ConfigurationProperties` in place of MicroProfile Config annotations
+    summary: Use Spring Boot's @ConfigurationProperties in place of MicroProfile Config annotations
     categories: compatibility
     topics:
     - spring
diff --git a/_generated-doc/latest/config/quarkus-all-config.adoc b/_generated-doc/latest/config/quarkus-all-config.adoc
@@ -11424,7 +11424,7 @@ Environment variable: `+++QUARKUS_KEYCLOAK_DEVSERVICES_IMAGE_NAME+++`
 endif::add-copy-button-to-env-var[]
 --
 |string
-|`quay.io/keycloak/keycloak:26.0.7`
+|`quay.io/keycloak/keycloak:26.1.3`
 
 a|icon:lock[title=Fixed at build time] [[quarkus-devservices-keycloak_quarkus-keycloak-devservices-keycloak-x-image]] [.property-path]##link:#quarkus-devservices-keycloak_quarkus-keycloak-devservices-keycloak-x-image[`quarkus.keycloak.devservices.keycloak-x-image`]##
 ifdef::add-copy-button-to-config-props[]
diff --git a/_generated-doc/latest/config/quarkus-devservices-keycloak.adoc b/_generated-doc/latest/config/quarkus-devservices-keycloak.adoc
@@ -47,7 +47,7 @@ Environment variable: `+++QUARKUS_KEYCLOAK_DEVSERVICES_IMAGE_NAME+++`
 endif::add-copy-button-to-env-var[]
 --
 |string
-|`quay.io/keycloak/keycloak:26.0.7`
+|`quay.io/keycloak/keycloak:26.1.3`
 
 a|icon:lock[title=Fixed at build time] [[quarkus-devservices-keycloak_quarkus-keycloak-devservices-keycloak-x-image]] [.property-path]##link:#quarkus-devservices-keycloak_quarkus-keycloak-devservices-keycloak-x-image[`quarkus.keycloak.devservices.keycloak-x-image`]##
 ifdef::add-copy-button-to-config-props[]
diff --git a/_generated-doc/latest/config/quarkus-devservices-keycloak_quarkus.keycloak.adoc b/_generated-doc/latest/config/quarkus-devservices-keycloak_quarkus.keycloak.adoc
@@ -47,7 +47,7 @@ Environment variable: `+++QUARKUS_KEYCLOAK_DEVSERVICES_IMAGE_NAME+++`
 endif::add-copy-button-to-env-var[]
 --
 |string
-|`quay.io/keycloak/keycloak:26.0.7`
+|`quay.io/keycloak/keycloak:26.1.3`
 
 a|icon:lock[title=Fixed at build time] [[quarkus-devservices-keycloak_quarkus-keycloak-devservices-keycloak-x-image]] [.property-path]##link:#quarkus-devservices-keycloak_quarkus-keycloak-devservices-keycloak-x-image[`quarkus.keycloak.devservices.keycloak-x-image`]##
 ifdef::add-copy-button-to-config-props[]
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.19.2
+:quarkus-version: 3.19.3
 :quarkus-platform-groupid: io.quarkus.platform
 // .
 :maven-version: 3.9.9
@@ -18,7 +18,7 @@
 :infinispan-protostream-version: ${infinispan.protostream.version}
 :logstash-image: docker.io/elastic/logstash:8.15.0
 :kibana-image: docker.io/elastic/kibana:8.15.0
-:keycloak-docker-image: quay.io/keycloak/keycloak:26.0.7
+:keycloak-docker-image: quay.io/keycloak/keycloak:26.1.3
 :jandex-version: 3.2.7
 :jandex-gradle-plugin-version: 1.0.0
 :kotlin-version: 2.0.21
diff --git a/_guides/config-yaml.adoc b/_guides/config-yaml.adoc
@@ -7,7 +7,7 @@ https://github.com/quarkusio/quarkus/tree/main/docs/src/main/asciidoc
 include::_attributes.adoc[]
 :diataxis-type: howto
 :categories: core
-:summary: Optionally, use `application.yaml` instead of `application.properties` to configure your application.
+:summary: Optionally, use application.yaml instead of application.properties to configure your application.
 :topics: configuration
 :extensions: io.quarkus:quarkus-config-yaml
 
diff --git a/_guides/maven-tooling.adoc b/_guides/maven-tooling.adoc
@@ -295,7 +295,7 @@ A user may choose to disable all the Java options provided by extensions by conf
                 <version>${quarkus.platform.version}</version>
                 <configuration>
                     <extensionJvmOptions>
-                        <disableAll>false</disableAll>
+                        <disableAll>true</disableAll>
                     </extensionJvmOptions>
                 </configuration>
             </plugin>
diff --git a/_guides/rest.adoc b/_guides/rest.adoc
@@ -1407,7 +1407,7 @@ Instead of importing `io.quarkus:quarkus-rest`, you can import either of the fol
 |https://github.com/FasterXML/jackson[Jackson support]
 
 |`io.quarkus:quarkus-rest-jsonb`
-|https://eclipse-ee4j.github.io/jsonb-api/[JSON-B support]
+|https://github.com/jakartaee/jsonb-api/[JSON-B support]
 
 |===
 
@@ -1624,7 +1624,7 @@ public User userPrivate() {
 }
 ----
 
-When the result the `userPublic` method is serialized, the `id` field will not be contained in the response as the `Public` view does not include it.
+When the result of the `userPublic` method is serialized, the `id` field will not be contained in the response as the `Public` view does not include it.
 The result of `userPrivate` however will include the `id` as expected when serialized.
 
 ===== Reflection-free Jackson serialization
diff --git a/_guides/security-keycloak-authorization.adoc b/_guides/security-keycloak-authorization.adoc
@@ -319,8 +319,7 @@ docker run --name keycloak \
   quay.io/keycloak/keycloak:{keycloak.version} \ <1>
   start --hostname-strict=false --https-key-store-file=/etc/keycloak-keystore.jks <2>
 ----
-
-<1> For `keycloak.version`, ensure the version is `26.0.7` or later.
+<1> For `keycloak.version`, ensure the version is `26.1.3` or later.
 <2> For Keycloak keystore, use the `keycloak-keystore.jks` file located at https://github.com/quarkusio/quarkus-quickstarts/blob/main/security-keycloak-authorization-quickstart/config/keycloak-keystore.jks[quarkus-quickstarts/security-keycloak-authorization-quickstart/config].
 
 .Accessing the Keycloak server
diff --git a/_guides/security-oidc-bearer-token-authentication-tutorial.adoc b/_guides/security-oidc-bearer-token-authentication-tutorial.adoc
@@ -217,7 +217,7 @@ For more information, see the <<bearer-token-tutorial-keycloak-dev-mode>> sectio
 docker run --name keycloak -e KC_BOOTSTRAP_ADMIN_USERNAME=admin -e KC_BOOTSTRAP_ADMIN_PASSWORD=admin -p 8180:8080 quay.io/keycloak/keycloak:{keycloak.version} start-dev
 ----
 ====
-* Where the `keycloak.version` is set to version `26.0.7` or later.
+* Where the `keycloak.version` is set to version `26.1.3` or later.
 . You can access your Keycloak server at http://localhost:8180[localhost:8180].
 . To access the Keycloak Administration console, log in as the `admin` user by using the following login credentials:
 
diff --git a/_guides/security-oidc-code-flow-authentication-tutorial.adoc b/_guides/security-oidc-code-flow-authentication-tutorial.adoc
@@ -201,7 +201,7 @@ To start a Keycloak server, use Docker and run the following command:
 docker run --name keycloak -e KC_BOOTSTRAP_ADMIN_USERNAME=admin -e KC_BOOTSTRAP_ADMIN_PASSWORD=admin -p 8180:8080 quay.io/keycloak/keycloak:{keycloak.version} start-dev
 ----
 
-where `keycloak.version` is set to `26.0.7` or later.
+where `keycloak.version` is set to `26.1.3` or later.
 
 You can access your Keycloak Server at http://localhost:8180[localhost:8180].
 
diff --git a/_guides/security-openid-connect-client.adoc b/_guides/security-openid-connect-client.adoc
@@ -505,7 +505,7 @@ To start a Keycloak Server, you can use Docker and just run the following comman
 docker run --name keycloak -e KC_BOOTSTRAP_ADMIN_USERNAME=admin -e KC_BOOTSTRAP_ADMIN_PASSWORD=admin -p 8180:8080 quay.io/keycloak/keycloak:{keycloak.version} start-dev
 ----
 
-Set `{keycloak.version}` to `26.0.7` or later.
+Set `{keycloak.version}` to `26.1.3` or later.
 
 You can access your Keycloak Server at http://localhost:8180[localhost:8180].
 
diff --git a/_guides/security-openid-connect-dev-services.adoc b/_guides/security-openid-connect-dev-services.adoc
@@ -242,7 +242,7 @@ For more information, see xref:security-oidc-bearer-token-authentication.adoc#be
 [[keycloak-initialization]]
 === Keycloak initialization
 
-The `quay.io/keycloak/keycloak:26.0.7` image which contains a Keycloak distribution powered by Quarkus is used to start a container by default.
+The `quay.io/keycloak/keycloak:26.1.3` image which contains a Keycloak distribution powered by Quarkus is used to start a container by default.
 `quarkus.keycloak.devservices.image-name` can be used to change the Keycloak image name.
 For example, set it to `quay.io/keycloak/keycloak:19.0.3-legacy` to use a Keycloak distribution powered by WildFly.
 Be aware that a Quarkus-based Keycloak distribution is only available starting from Keycloak `20.0.0`.
diff --git a/_guides/spring-boot-properties.adoc b/_guides/spring-boot-properties.adoc
@@ -6,7 +6,7 @@ https://github.com/quarkusio/quarkus/tree/main/docs/src/main/asciidoc
 = Accessing application properties with Spring Boot properties API
 include::_attributes.adoc[]
 :categories: compatibility
-:summary: Use Spring Boot's `@ConfigurationProperties` in place of MicroProfile Config annotations
+:summary: Use Spring Boot's @ConfigurationProperties in place of MicroProfile Config annotations
 :topics: spring,configuration,compatibility
 :extensions: io.quarkus:quarkus-spring-boot-properties
 
diff --git a/_guides/telemetry-micrometer.adoc b/_guides/telemetry-micrometer.adoc
@@ -10,7 +10,7 @@ include::_attributes.adoc[]
 :categories: observability
 :summary: Use Micrometer to collect metrics produced by Quarkus, its extensions, and your application.
 :base-units: https://github.com/micrometer-metrics/micrometer/blob/main/micrometer-core/src/main/java/io/micrometer/core/instrument/binder/BaseUnits.java
-:concepts: https://micrometer.io/docs/concepts
+:concepts: https://docs.micrometer.io/micrometer/reference/concepts
 :topics: observability,micrometer
 :extensions: io.quarkus:quarkus-micrometer
 
@@ -188,7 +188,7 @@ For hierarchical systems that only support a flat metric name, Micrometer will f
 
 Tags can be specified when a meter is registered with a `MeterRegistry` or using a <<meter-filter,Meter Filter>>.
 
-See the Micrometer documentation for additional advice on link:{concepts}#_tag_naming[tag naming].
+See the Micrometer documentation for additional advice on link:{concepts}/naming[tag naming].
 
 IMPORTANT: Each unique combination of metric name and dimension produces a unique time series.
 Using an unbounded set of dimensional data can lead to a "cardinality explosion", an exponential increase in the creation of new time series.
@@ -279,7 +279,7 @@ Gauge.builder("jvm.threads.peak", threadBean, ThreadMXBean::getPeakThreadCount)
 <4> Associate <<define-tags,tags>> with the gauge
 <5> Register the Gauge with the MeterRegistry
 
-See link:{concepts}#_gauges[Gauges] in the Micrometer documentation for more information and examples.
+See link:{concepts}/gauges[Gauges] in the Micrometer documentation for more information and examples.
 Of note are two special cases: `TimeGauge` for measuring time, and a `MultiGauge` for reporting several criteria together.
 
 NOTE: Micrometer does not create strong references to the objects it observes by default.
@@ -336,7 +336,7 @@ void countThisMethod(){
 <1> A CDI interceptor will create and register a counter called `counted.method`
 <2> The interceptor-created counter will have the "extra" dimension tag with value "annotated"
 
-See link:{concepts}#_counters[Counters] in the Micrometer documentation for more information and examples, including the less common `FunctionCounter` that can be used to measure the result returned by an always increasing function.
+See link:{concepts}/counters[Counters] in the Micrometer documentation for more information and examples, including the less common `FunctionCounter` that can be used to measure the result returned by an always increasing function.
 
 When should you use a counter?
 Use a counter if you are doing something that can not be either timed or summarized.
@@ -478,7 +478,7 @@ sample.stop(registry.timer("my.timer", "response", response.status())); // <3>
 ==== Histograms and percentiles
 
 Both timers and distribution summaries can be configured to emit additional statistics, like histogram data, precomputed percentiles, or service level objective (SLO) boundaries.
-See link:{concepts}#_timers[Timers] and link:{concepts}#_distribution_summaries[Distribution Summaries] in the Micrometer documentation for more information and examples, including memory footprint estimation for both types.
+See link:{concepts}/timers[Timers] and link:{concepts}/distribution-summaries[Distribution Summaries] in the Micrometer documentation for more information and examples, including memory footprint estimation for both types.
 
 [IMPORTANT]
 ====
