Sync documentation of main branch

_data/versioned/main/index/quarkus.yaml

@@ -30,7 +30,7 @@ types:
   - title: Configure data sources in Quarkus
     filename: datasource.adoc
     summary: Use a unified configuration model to define datasources for Java Database Connectivity (JDBC) and Reactive drivers.
-    categories: "getting-started, data"
+    categories: "data, getting-started"
     id: datasources
     type: reference
     url: /guides/datasource
@@ -55,7 +55,7 @@ types:
   - title: Logging configuration
     filename: logging.adoc
     summary: "Read about the use of logging API in Quarkus, configuring logging output, and using logging adapters to unify the output from other logging APIs."
-    categories: "core, getting-started, observability"
+    categories: "getting-started, core, observability"
     id: logging
     type: reference
     url: /guides/logging
@@ -180,7 +180,7 @@ types:
   - title: "Duplicated context, context locals, asynchronous processing and propagation"
     filename: duplicated-context.adoc
     summary: "When using a traditional, blocking, and synchronous framework, processing of each request is performed in a dedicated thread."
-    categories: "core, architecture"
+    categories: "architecture, core"
     id: duplicated-context
     type: concepts
     url: /guides/duplicated-context
@@ -236,7 +236,7 @@ types:
   - title: Security vulnerability detection and reporting in Quarkus
     filename: security-vulnerability-detection.adoc
     summary: Most of the Quarkus tags are registered in the US National Vulnerability Database (NVD) in Common Platform Enumeration (CPE) name format.
-    categories: "contributing, security"
+    categories: "security, contributing"
     id: security-vulnerability-detection
     type: concepts
     url: /guides/security-vulnerability-detection
@@ -265,15 +265,15 @@ types:
   - title: Use virtual threads in REST applications
     filename: resteasy-reactive-virtual-threads.adoc
     summary: How to use virtual threads in a REST application
-    categories: "core, web"
+    categories: "web, core"
     id: resteasy-reactive-virtual-threads
     type: howto
     url: /guides/resteasy-reactive-virtual-threads
   tutorial:
   - title: Building a Native Executable
     filename: building-native-image.adoc
     summary: Build native executables with GraalVM or Mandrel.
-    categories: "getting-started, native"
+    categories: "native, getting-started"
     type: tutorial
     url: /guides/building-native-image
   - title: Collect metrics using Micrometer
@@ -338,7 +338,7 @@ types:
   - title: Your second Quarkus application
     filename: getting-started-dev-services.adoc
     summary: This tutorial shows you how to create an application which writes to and reads from a database.
-    categories: "core, getting-started, data"
+    categories: "data, getting-started, core"
     id: getting-started-dev-services-tutorial
     type: tutorial
     url: /guides/getting-started-dev-services
@@ -394,7 +394,7 @@ types:
   - title: AppCDS
     filename: appcds.adoc
     summary: This reference guide explains how to enable AppCDS with Quarkus.
-    categories: "core, cloud"
+    categories: "cloud, core"
     type: guide
     url: /guides/appcds
   - title: Application Data Caching
@@ -1033,7 +1033,7 @@ types:
   - title: Simplified Hibernate ORM with Panache and Kotlin
     filename: hibernate-orm-panache-kotlin.adoc
     summary: This explains the specifics of using Hibernate ORM with Panache in a Kotlin project.
-    categories: "data, alt-languages"
+    categories: "alt-languages, data"
     type: guide
     url: /guides/hibernate-orm-panache-kotlin
   - title: Simplified Hibernate Reactive with Panache
@@ -1051,13 +1051,13 @@ types:
   - title: Simplified MongoDB with Panache and Kotlin
     filename: mongodb-panache-kotlin.adoc
     summary: This guide covers the usage of MongoDB using active records and repositories in a Kotlin project.
-    categories: "data, alt-languages"
+    categories: "alt-languages, data"
     type: guide
     url: /guides/mongodb-panache-kotlin
   - title: SmallRye Fault Tolerance
     filename: smallrye-fault-tolerance.adoc
     summary: This guide demonstrates how your Quarkus application can utilize the SmallRye Fault Tolerance specification through the SmallRye Fault Tolerance extension.
-    categories: "observability, web"
+    categories: "web, observability"
     type: guide
     url: /guides/smallrye-fault-tolerance
   - title: SmallRye GraphQL
@@ -1087,14 +1087,14 @@ types:
   - title: Testing Your Application
     filename: getting-started-testing.adoc
     summary: "This guide covers testing in JVM mode, native mode, and injection of resources into tests"
-    categories: "core, native, tooling"
+    categories: "native, tooling, core"
     id: testing
     type: guide
     url: /guides/getting-started-testing
   - title: Tips for writing native applications
     filename: writing-native-applications-tips.adoc
     summary: This guide is a collection of tips to help you solve the problems you encounter when compiling applications to native executable.
-    categories: "core, writing-extensions, native"
+    categories: "writing-extensions, native, core"
     type: guide
     url: /guides/writing-native-applications-tips
   - title: Using Apache Kafka Streams
@@ -1223,7 +1223,7 @@ types:
   - title: Using SSL With Native Executables
     filename: native-and-ssl.adoc
     summary: "In this guide, we will discuss how you can get your native images to support SSL, as native images don't support it out of the box."
-    categories: "core, security, native"
+    categories: "security, native, core"
     type: guide
     url: /guides/native-and-ssl
   - title: Using Security with .properties File
@@ -1342,7 +1342,7 @@ types:
   - title: Writing JSON REST Services
     filename: rest-json.adoc
     summary: JSON is now the lingua franca between microservices.
-    categories: "serialization, web"
+    categories: "web, serialization"
     type: guide
     url: /guides/rest-json
   - title: Writing REST Services with RESTEasy Reactive

_generated-doc/main/config/quarkus-agroal-config-group-data-source-jdbc-runtime-config.adoc

@@ -817,11 +817,17 @@ ifndef::no-duration-note[]
 [id='duration-note-anchor-{summaryTableId}']
 .About the Duration format
 ====
-The format for durations uses the standard `java.time.Duration` format.
-You can learn more about it in the link:https://docs.oracle.com/javase/8/docs/api/java/time/Duration.html#parse-java.lang.CharSequence-[Duration#parse() javadoc].
+To write duration values, use the standard `java.time.Duration` format.
+See the link:https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/time/Duration.html#parse(java.lang.CharSequence)[Duration#parse() javadoc] for more information.
 
-You can also provide duration values starting with a number.
-In this case, if the value consists only of a number, the converter treats the value as seconds.
-Otherwise, `PT` is implicitly prepended to the value to obtain a standard `java.time.Duration` format.
+You can also use a simplified format, starting with a number:
+
+* If the value is only a number, it represents time in seconds.
+* If the value is a number followed by `ms`, it represents time in milliseconds.
+
+In other cases, the simplified format is translated to the `java.time.Duration` format for parsing:
+
+* If the value is a number followed by `h`, `m`, or `s`, it is prefixed with `PT`.
+* If the value is a number followed by `d`, it is prefixed with `P`.
 ====
 endif::no-duration-note[]

_generated-doc/main/config/quarkus-agroal-config-group-data-sources-jdbc-runtime-config-data-source-jdbc-outer-named-runtime-config.adoc

@@ -416,11 +416,17 @@ ifndef::no-duration-note[]
 [id='duration-note-anchor-{summaryTableId}']
 .About the Duration format
 ====
-The format for durations uses the standard `java.time.Duration` format.
-You can learn more about it in the link:https://docs.oracle.com/javase/8/docs/api/java/time/Duration.html#parse-java.lang.CharSequence-[Duration#parse() javadoc].
+To write duration values, use the standard `java.time.Duration` format.
+See the link:https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/time/Duration.html#parse(java.lang.CharSequence)[Duration#parse() javadoc] for more information.
 
-You can also provide duration values starting with a number.
-In this case, if the value consists only of a number, the converter treats the value as seconds.
-Otherwise, `PT` is implicitly prepended to the value to obtain a standard `java.time.Duration` format.
+You can also use a simplified format, starting with a number:
+
+* If the value is only a number, it represents time in seconds.
+* If the value is a number followed by `ms`, it represents time in milliseconds.
+
+In other cases, the simplified format is translated to the `java.time.Duration` format for parsing:
+
+* If the value is a number followed by `h`, `m`, or `s`, it is prefixed with `PT`.
+* If the value is a number followed by `d`, it is prefixed with `P`.
 ====
 endif::no-duration-note[]

_generated-doc/main/config/quarkus-agroal-general-config-items.adoc

@@ -944,11 +944,17 @@ ifndef::no-duration-note[]
 [id='duration-note-anchor-{summaryTableId}']
 .About the Duration format
 ====
-The format for durations uses the standard `java.time.Duration` format.
-You can learn more about it in the link:https://docs.oracle.com/javase/8/docs/api/java/time/Duration.html#parse-java.lang.CharSequence-[Duration#parse() javadoc].
+To write duration values, use the standard `java.time.Duration` format.
+See the link:https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/time/Duration.html#parse(java.lang.CharSequence)[Duration#parse() javadoc] for more information.
 
-You can also provide duration values starting with a number.
-In this case, if the value consists only of a number, the converter treats the value as seconds.
-Otherwise, `PT` is implicitly prepended to the value to obtain a standard `java.time.Duration` format.
+You can also use a simplified format, starting with a number:
+
+* If the value is only a number, it represents time in seconds.
+* If the value is a number followed by `ms`, it represents time in milliseconds.
+
+In other cases, the simplified format is translated to the `java.time.Duration` format for parsing:
+
+* If the value is a number followed by `h`, `m`, or `s`, it is prefixed with `PT`.
+* If the value is a number followed by `d`, it is prefixed with `P`.
 ====
 endif::no-duration-note[]

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

@@ -944,11 +944,17 @@ ifndef::no-duration-note[]
 [id='duration-note-anchor-{summaryTableId}']
 .About the Duration format
 ====
-The format for durations uses the standard `java.time.Duration` format.
-You can learn more about it in the link:https://docs.oracle.com/javase/8/docs/api/java/time/Duration.html#parse-java.lang.CharSequence-[Duration#parse() javadoc].
+To write duration values, use the standard `java.time.Duration` format.
+See the link:https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/time/Duration.html#parse(java.lang.CharSequence)[Duration#parse() javadoc] for more information.
 
-You can also provide duration values starting with a number.
-In this case, if the value consists only of a number, the converter treats the value as seconds.
-Otherwise, `PT` is implicitly prepended to the value to obtain a standard `java.time.Duration` format.
+You can also use a simplified format, starting with a number:
+
+* If the value is only a number, it represents time in seconds.
+* If the value is a number followed by `ms`, it represents time in milliseconds.
+
+In other cases, the simplified format is translated to the `java.time.Duration` format for parsing:
+
+* If the value is a number followed by `h`, `m`, or `s`, it is prefixed with `PT`.
+* If the value is a number followed by `d`, it is prefixed with `P`.
 ====
 endif::no-duration-note[]

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

@@ -65933,8 +65933,6 @@ a| [[quarkus-grpc_quarkus.grpc.clients.-client-name-.deadline]]`link:#quarkus-gr
 --
 The deadline used for each call.
 
-The format uses the standard `java.time.Duration` format. You can also provide duration values starting with a number. In this case, if the value consists only of a number, the converter treats the value as seconds. Otherwise, `PT` is implicitly prepended to the value to obtain a standard `java.time.Duration` format.
-
 ifdef::add-copy-button-to-env-var[]
 Environment variable: env_var_with_copy_button:+++QUARKUS_GRPC_CLIENTS__CLIENT_NAME__DEADLINE+++[]
 endif::add-copy-button-to-env-var[]
@@ -66510,12 +66508,18 @@ ifndef::no-duration-note[]
 [id='duration-note-anchor-{summaryTableId}']
 .About the Duration format
 ====
-The format for durations uses the standard `java.time.Duration` format.
-You can learn more about it in the link:https://docs.oracle.com/javase/8/docs/api/java/time/Duration.html#parse-java.lang.CharSequence-[Duration#parse() javadoc].
+To write duration values, use the standard `java.time.Duration` format.
+See the link:https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/time/Duration.html#parse(java.lang.CharSequence)[Duration#parse() javadoc] for more information.
+
+You can also use a simplified format, starting with a number:
+
+* If the value is only a number, it represents time in seconds.
+* If the value is a number followed by `ms`, it represents time in milliseconds.
+
+In other cases, the simplified format is translated to the `java.time.Duration` format for parsing:
 
-You can also provide duration values starting with a number.
-In this case, if the value consists only of a number, the converter treats the value as seconds.
-Otherwise, `PT` is implicitly prepended to the value to obtain a standard `java.time.Duration` format.
+* If the value is a number followed by `h`, `m`, or `s`, it is prefixed with `PT`.
+* If the value is a number followed by `d`, it is prefixed with `P`.
 ====
 endif::no-duration-note[]
 

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

@@ -216,11 +216,17 @@ ifndef::no-duration-note[]
 [id='duration-note-anchor-{summaryTableId}']
 .About the Duration format
 ====
-The format for durations uses the standard `java.time.Duration` format.
-You can learn more about it in the link:https://docs.oracle.com/javase/8/docs/api/java/time/Duration.html#parse-java.lang.CharSequence-[Duration#parse() javadoc].
+To write duration values, use the standard `java.time.Duration` format.
+See the link:https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/time/Duration.html#parse(java.lang.CharSequence)[Duration#parse() javadoc] for more information.
 
-You can also provide duration values starting with a number.
-In this case, if the value consists only of a number, the converter treats the value as seconds.
-Otherwise, `PT` is implicitly prepended to the value to obtain a standard `java.time.Duration` format.
+You can also use a simplified format, starting with a number:
+
+* If the value is only a number, it represents time in seconds.
+* If the value is a number followed by `ms`, it represents time in milliseconds.
+
+In other cases, the simplified format is translated to the `java.time.Duration` format for parsing:
+
+* If the value is a number followed by `h`, `m`, or `s`, it is prefixed with `PT`.
+* If the value is a number followed by `d`, it is prefixed with `P`.
 ====
 endif::no-duration-note[]

_generated-doc/main/config/quarkus-cache-config-group-cache-config-caffeine-config-caffeine-cache-config.adoc

@@ -189,11 +189,17 @@ ifndef::no-duration-note[]
 [id='duration-note-anchor-{summaryTableId}']
 .About the Duration format
 ====
-The format for durations uses the standard `java.time.Duration` format.
-You can learn more about it in the link:https://docs.oracle.com/javase/8/docs/api/java/time/Duration.html#parse-java.lang.CharSequence-[Duration#parse() javadoc].
+To write duration values, use the standard `java.time.Duration` format.
+See the link:https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/time/Duration.html#parse(java.lang.CharSequence)[Duration#parse() javadoc] for more information.
 
-You can also provide duration values starting with a number.
-In this case, if the value consists only of a number, the converter treats the value as seconds.
-Otherwise, `PT` is implicitly prepended to the value to obtain a standard `java.time.Duration` format.
+You can also use a simplified format, starting with a number:
+
+* If the value is only a number, it represents time in seconds.
+* If the value is a number followed by `ms`, it represents time in milliseconds.
+
+In other cases, the simplified format is translated to the `java.time.Duration` format for parsing:
+
+* If the value is a number followed by `h`, `m`, or `s`, it is prefixed with `PT`.
+* If the value is a number followed by `d`, it is prefixed with `P`.
 ====
 endif::no-duration-note[]

_generated-doc/main/config/quarkus-cache-config-group-cache-config-caffeine-config.adoc

@@ -194,11 +194,17 @@ ifndef::no-duration-note[]
 [id='duration-note-anchor-{summaryTableId}']
 .About the Duration format
 ====
-The format for durations uses the standard `java.time.Duration` format.
-You can learn more about it in the link:https://docs.oracle.com/javase/8/docs/api/java/time/Duration.html#parse-java.lang.CharSequence-[Duration#parse() javadoc].
+To write duration values, use the standard `java.time.Duration` format.
+See the link:https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/time/Duration.html#parse(java.lang.CharSequence)[Duration#parse() javadoc] for more information.
 
-You can also provide duration values starting with a number.
-In this case, if the value consists only of a number, the converter treats the value as seconds.
-Otherwise, `PT` is implicitly prepended to the value to obtain a standard `java.time.Duration` format.
+You can also use a simplified format, starting with a number:
+
+* If the value is only a number, it represents time in seconds.
+* If the value is a number followed by `ms`, it represents time in milliseconds.
+
+In other cases, the simplified format is translated to the `java.time.Duration` format for parsing:
+
+* If the value is a number followed by `h`, `m`, or `s`, it is prefixed with `PT`.
+* If the value is a number followed by `d`, it is prefixed with `P`.
 ====
 endif::no-duration-note[]

_generated-doc/main/config/quarkus-cache-general-config-items.adoc

@@ -194,11 +194,17 @@ ifndef::no-duration-note[]
 [id='duration-note-anchor-{summaryTableId}']
 .About the Duration format
 ====
-The format for durations uses the standard `java.time.Duration` format.
-You can learn more about it in the link:https://docs.oracle.com/javase/8/docs/api/java/time/Duration.html#parse-java.lang.CharSequence-[Duration#parse() javadoc].
+To write duration values, use the standard `java.time.Duration` format.
+See the link:https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/time/Duration.html#parse(java.lang.CharSequence)[Duration#parse() javadoc] for more information.
 
-You can also provide duration values starting with a number.
-In this case, if the value consists only of a number, the converter treats the value as seconds.
-Otherwise, `PT` is implicitly prepended to the value to obtain a standard `java.time.Duration` format.
+You can also use a simplified format, starting with a number:
+
+* If the value is only a number, it represents time in seconds.
+* If the value is a number followed by `ms`, it represents time in milliseconds.
+
+In other cases, the simplified format is translated to the `java.time.Duration` format for parsing:
+
+* If the value is a number followed by `h`, `m`, or `s`, it is prefixed with `PT`.
+* If the value is a number followed by `d`, it is prefixed with `P`.
 ====
 endif::no-duration-note[]