Sync web site with Quarkus documentation

Author: quarkusbot

_generated-doc/3.20/infra/quarkus-all-build-items.adoc

@@ -7235,7 +7235,11 @@ a| https://github.com/quarkusio/quarkus/blob/main/extensions/resteasy-reactive/r
 [.description]
 --
 Represents a JAX-RS resource that is generated. Meant to be used by extension that generate JAX-RS resources as part of their build time processing
--- a|`java.lang.String name` 
+-- a|`java.lang.String binaryName` 
+
+_No Javadoc found_
+
+`java.lang.String internalName` 
 
 _No Javadoc found_
 

_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.1
+:quarkus-version: 3.20.2
 :quarkus-platform-groupid: io.quarkus.platform
 // .
 :maven-version: 3.9.9

_versions/3.20/guides/databases-dev-services.adoc

@@ -150,12 +150,14 @@ Dev Services volumes can be mapped to the filesystem or the classpath:
 # Using a filesystem volume:
 quarkus.datasource.devservices.volumes."/path/from"=/container/to <1>
 # Using a classpath volume:
-quarkus.datasource.devservices.volumes."classpath:./file"=/container/to <2>
+quarkus.datasource.devservices.volumes."classpath\:./file"=/container/to <2>
 ----
 
 <1> The file or folder "/path/from" from the local machine will be accessible at "/container/to" in the container.
 <2> When using classpath volumes, the location has to start with "classpath:". The file or folder "./file" from the project's classpath will be accessible at "/container/to" in the container.
 
+CAUTION: The colon character `:` needs to be escaped in `.properties` files as `\:`, or it will be interpreted as a key/value separator.
+
 IMPORTANT: when using a classpath volume, the container will only be granted read permission. On the other hand, when using a filesystem volume, the container will be granted read and write permission.
 
 === Example of mapping volumes to persist the database data
@@ -217,7 +219,7 @@ Login credentials are the same for most databases, except when the database requ
 |`quarkus` for the default datasource or name of the datasource
 
 |Microsoft SQL Server
-|`SA`
+|`sa`
 |`Quarkus123`
 |
 

_versions/3.20/guides/flyway.adoc

@@ -448,3 +448,27 @@ quarkus.openshift.init-task-defaults.wait-for-container.image=my/wait-for-image:
 ----
 
 **Note**: In this context globally means `for all extensions that support init task externalization`.
+
+== Known Issues in Flyway
+
+=== Oracle: Multiple schemas in Dev Services
+
+When having multiple schemas in Oracle, you can use the `quarkus.flyway.schemas` property to specify the schemas that Flyway should manage.
+However, because this is executed in the DB as the `quarkus` user, you need to either give DBA privileges to the user that is executing the migration (`quarkus`) or perform the necessary DDLs before the Dev Service starts. This is done with the `quarkus.datasource.devservices.init-script-path` configuration.
+
+==== Giving DBA privileges to the user
+
+- In your application, create a SQL file named `001-devservice-init.sql` (for ordering purposes, it can be any name really) in your `src/main/resources` with the following content:
+
+[source,sql]
+----
+ALTER SESSION SET CONTAINER=quarkus;
+GRANT DBA TO quarkus;
+----
+
+- Add the following configuration to your `application.properties`:
+
+[source,properties]
+----
+quarkus.datasource.devservices.init-script-path=001-devservice-init.sql
+----

_versions/3.20/guides/observability-devservices-lgtm.adoc

@@ -53,15 +53,15 @@ This is the most common way to output metrics from Micrometer and the default wa
 .pom.xml
 ----
 <dependency>
-    <groupId>io.quarkiverse.micrometer.registry</groupId>
+    <groupId>io.quarkus</groupId>
     <artifactId>quarkus-micrometer-registry-prometheus</artifactId>
 </dependency>
 ----
 
 [source,gradle,role="secondary asciidoc-tabs-target-sync-gradle"]
 .build.gradle
 ----
-implementation("io.quarkiverse.micrometer.registry:quarkus-micrometer-registry-prometheus")
+implementation("io.quarkus:quarkus-micrometer-registry-prometheus")
 ----
 
 ==== Using the Micrometer OTLP registry

_versions/3.20/guides/qute-reference.adoc

@@ -2041,9 +2041,13 @@ public class ItemResource {
 [[type_safe_fragments]]
 ==== Type-safe Fragments
 
-You can also define a type-safe <<fragments,fragment>> in your Java code.
-A _native static_ method with the name that contains a dollar sign `$` denotes a method that represents a fragment of a type-safe template.
-The name of the fragment is derived from the annotated method name.
+You can also define a type-safe <<fragments,fragment>> of a type-safe template in your Java code.
+There are two ways to define a type-safe fragment:
+
+1. A _native static_ method annotated with `@CheckedTemplate`, with a name that contains a dollar sign `$`.
+2. A Java record that implements `io.quarkus.qute.TemplateInstance` and its name contains a dollar sign `$`.
+
+The name of the fragment is derived from the annotated member name.
 The part before the last occurrence of a dollar sign `$` is the method name of the related type-safe template.
 The part after the last occurrence of a dollar sign is the fragment identifier.
 The strategy defined by the relevant `CheckedTemplate#defaultName()` is honored when constructing the defaulted names.
@@ -2062,6 +2066,9 @@ class Templates {
 
   // defines a fragment of Templates#items() with identifier "item"
   static native TemplateInstance items$item(Item item); <1>
+  
+  // type-safe fragment as a Java record - functionally equivalent to the items$item() method above
+  record items$item(Item item) implements TemplateInstance {}
 }
 ----
 <1> Quarkus validates at build time that each template that corresponds to the `Templates#items()` contains a fragment with identifier `item`. Moreover, the parameters of the fragment method are validated too. In general, all type-safe expressions that are found in the fragment and that reference some data from the original/outer template require a specific parameter to be present.

_versions/3.20/guides/security-jwt-build.adoc

@@ -370,6 +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.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.

_versions/3.20/guides/security-openid-connect-providers.adoc

@@ -230,6 +230,21 @@ quarkus.oidc.client-id=<Client ID>
 quarkus.oidc.credentials.secret=<Secret>
 ----
 
+[NOTE]
+====
+By default, Quarkus GitHub provider submits the client id and secret in the HTTP Authorization header.
+However, GitHub may require that both client id and secret are submitted as form parameters instead.
+When you get HTTP 401 error after logging in to GitHub and being redirected back to Quarkus MCP server,
+replace the `quarkus.oidc.credentials.secret=<Secret>` property
+with the following two properties instead:
+
+[source,properties]
+----
+quarkus.oidc.credentials.client-secret.method=post
+quarkus.oidc.credentials.client-secret.value=<Secret>
+----
+====
+
 `quarkus.oidc.provider=github` will request GitHub to add a `user:email` scope to issued access tokens. For information about overriding this scope or requesting more scopes, see the  <<provider-scope>> section.
 
 TIP: You can also send access tokens issued by GitHub to `quarkus.oidc.application-type=service` or `quarkus.oidc.application-type=hybrid` Quarkus applications.

_versions/3.20/guides/telemetry-micrometer.adoc

@@ -727,15 +727,17 @@ The value cannot be overridden at runtime.
 If you enable the management interface without customizing the management network interface and port, the metrics are exposed under: `http://0.0.0.0:9000/q/metrics`.
 
 You can configure the path of each exposed format using:
+
 [source, properties]
 ----
-quarkus.micrometer.export.json.enabled=true # Enable json metrics
+quarkus.micrometer.export.json.enabled=true <1>
 quarkus.micrometer.export.json.path=metrics/json
 quarkus.micrometer.export.prometheus.path=metrics/prometheus
 ----
+<1> Enable JSON metrics
 
-With such a configuration, the json metrics will be available from `http://0.0.0.0:9000/q/metrics/json`.
-The prometheus metrics will be available from `http://0.0.0.0:9000/q/metrics/prometheus`.
+With such a configuration, the JSON metrics will be available from `http://0.0.0.0:9000/q/metrics/json`.
+The Prometheus metrics will be available from `http://0.0.0.0:9000/q/metrics/prometheus`.
 
 Refer to the xref:./management-interface-reference.adoc[management interface reference] for more information.
 

_versions/3.20/guides/vertx-reference.adoc

@@ -704,7 +704,7 @@ The `EventBus` object provides methods to:
 [source, java]
 ----
 // Case 1
-bus.sendAndForget("greeting", name)
+bus.send("greeting", name)
 // Case 2
 bus.publish("greeting", name)
 // Case 3
@@ -730,7 +730,7 @@ Read xref:./virtual-threads.adoc[the virtual thread guide] for more details.
 
 === Use codecs
 
-The https://vertx.io/docs/vertx-core/java/#event_bus[Vert.x Event Bus] uses https://vertx.io/docs/vertx-core/java/#_message_codecs[codecs] to _serialize_ and _deserialize_ message objects.
+The link:++https://vertx.io/docs/vertx-core/java/#event_bus++[Vert.x Event Bus] uses link:++https://vertx.io/docs/vertx-core/java/#_message_codecs++[codecs] to _serialize_ and _deserialize_ message objects.
 Quarkus provides a default codec for local delivery.
 This codec is automatically used for return types and message body parameters of local consumers, i.e. methods annotated with `@ConsumeEvent` where `ConsumeEvent#local() == true` (which is the default).