Sync documentation of main branch

Author: actions-user

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

@@ -83190,10 +83190,17 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-The max HTTP chunk size (8096 bytes by default).
+Configures two different things:
+
+ - The max HTTP chunk size
+ - The size of the chunk to be read when an `InputStream` is being used as an input
+
+
 
 Can be overwritten by client-specific settings.
 
+This property is not applicable to the RESTEasy Client.
+
 
 ifdef::add-copy-button-to-env-var[]
 Environment variable: env_var_with_copy_button:+++QUARKUS_REST_CLIENT_MAX_CHUNK_SIZE+++[]
@@ -84109,7 +84116,12 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-The max HTTP chunk size (8096 bytes by default).
+Configures two different things:
+
+ - The max HTTP chunk size
+ - The size of the chunk to be read when an `InputStream` is being read and sent to the server
+
+
 
 This property is not applicable to the RESTEasy Client.
 

_generated-doc/main/config/quarkus-rest-client-config.adoc

@@ -696,10 +696,17 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-The max HTTP chunk size (8096 bytes by default).
+Configures two different things:
+
+ - The max HTTP chunk size
+ - The size of the chunk to be read when an `InputStream` is being used as an input
+
+
 
 Can be overwritten by client-specific settings.
 
+This property is not applicable to the RESTEasy Client.
+
 
 ifdef::add-copy-button-to-env-var[]
 Environment variable: env_var_with_copy_button:+++QUARKUS_REST_CLIENT_MAX_CHUNK_SIZE+++[]
@@ -1615,7 +1622,12 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-The max HTTP chunk size (8096 bytes by default).
+Configures two different things:
+
+ - The max HTTP chunk size
+ - The size of the chunk to be read when an `InputStream` is being read and sent to the server
+
+
 
 This property is not applicable to the RESTEasy Client.
 

_generated-doc/main/config/quarkus-rest-client-config_quarkus.rest-client.adoc

@@ -696,10 +696,17 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-The max HTTP chunk size (8096 bytes by default).
+Configures two different things:
+
+ - The max HTTP chunk size
+ - The size of the chunk to be read when an `InputStream` is being used as an input
+
+
 
 Can be overwritten by client-specific settings.
 
+This property is not applicable to the RESTEasy Client.
+
 
 ifdef::add-copy-button-to-env-var[]
 Environment variable: env_var_with_copy_button:+++QUARKUS_REST_CLIENT_MAX_CHUNK_SIZE+++[]
@@ -1615,7 +1622,12 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-The max HTTP chunk size (8096 bytes by default).
+Configures two different things:
+
+ - The max HTTP chunk size
+ - The size of the chunk to be read when an `InputStream` is being read and sent to the server
+
+
 
 This property is not applicable to the RESTEasy Client.
 

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

@@ -200,6 +200,17 @@ _No Javadoc found_
 
 
 
+a| https://github.com/quarkusio/quarkus/blob/main/core/deployment/src/main/java/io/quarkus/deployment/sbom/ApplicationManifestsBuildItem.java[`io.quarkus.deployment.sbom.ApplicationManifestsBuildItem`, window="_blank"]
+[.description]
+--
+Application manifests collected in a build
+-- a|`java.util.Collection<ApplicationManifest> manifests` 
+
+_No Javadoc found_
+
+
+
+
 a| https://github.com/quarkusio/quarkus/blob/main/core/deployment/src/main/java/io/quarkus/deployment/builditem/ApplicationStartBuildItem.java[`io.quarkus.deployment.builditem.ApplicationStartBuildItem`, window="_blank"]
 [.description]
 --

_versions/main/guides/building-my-first-extension.adoc

@@ -171,7 +171,7 @@ Your extension is a multi-module project. So let's start by checking out the par
     <module>runtime</module>
   </modules>
   <properties>
-    <compiler-plugin.version>3.13.0</compiler-plugin.version><!--2-->
+    <compiler-plugin.version>3.14.0</compiler-plugin.version><!--2-->
     <failsafe-plugin.version>${surefire-plugin.version}</failsafe-plugin.version>
     <maven.compiler.release>17</maven.compiler.release>
     <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
@@ -872,7 +872,7 @@ $ mvn quarkus:dev
 [INFO] Building greeting-app 1.0.0-SNAPSHOT
 [INFO] --------------------------------[ jar ]---------------------------------
 [INFO]
-[INFO] --- maven-compiler-plugin:3.13.0:compile (default-compile) @ greeting-app ---
+[INFO] --- maven-compiler-plugin:3.14.0:compile (default-compile) @ greeting-app ---
 [INFO] Nothing to compile - all classes are up to date
 [INFO]
 [INFO] --- quarkus-maven-plugin:{quarkus-version}:dev (default-cli) @ greeting-app ---

_versions/main/guides/building-native-image.adoc

@@ -644,7 +644,7 @@ Sample Dockerfile for building with Gradle:
 ## Stage 1 : build with maven builder image with native capabilities
 FROM quay.io/quarkus/ubi9-quarkus-mandrel-builder-image:{mandrel-flavor} AS build
 USER root
-RUN microdnf install findutils
+RUN microdnf install findutils -y
 COPY --chown=quarkus:quarkus gradlew /code/gradlew
 COPY --chown=quarkus:quarkus gradle /code/gradle
 COPY --chown=quarkus:quarkus build.gradle /code/
@@ -730,7 +730,7 @@ Sample multistage Dockerfile for building an image from `scratch`:
 ## Stage 1 : build with maven builder image with native capabilities
 FROM quay.io/quarkus/ubi9-quarkus-graalvmce-builder-image:{graalvm-flavor} AS build
 USER root
-RUN microdnf install make gcc
+RUN microdnf install make gcc -y
 COPY --chown=quarkus:quarkus mvnw /code/mvnw
 COPY --chown=quarkus:quarkus .mvn /code/.mvn
 COPY --chown=quarkus:quarkus pom.xml /code/

_versions/main/guides/hibernate-orm.adoc

@@ -1008,6 +1008,7 @@ as it will also clone some enhancement-specific fields that are specific to the
 This limitation might be removed in the future.
 ====
 
+[[automatic-integration]]
 === Automatic integration
 
 Transaction Manager integration::
@@ -1265,6 +1266,9 @@ With this approach, all datasources used by the same persistence unit
 are assumed to point to a database of the same vendor (same `db-kind`) and version.
 
 Mismatches will not be detected, and may result in unpredictable behavior.
+
+The list of datasources is defined at build time, so with this approach the **list** of tenants is **fixed at build time**.
+If the list of tenants needs to change at runtime, you must <<programmatically-resolving-tenants-connections,resolve the tenant connections programmatically>>.
 ====
 
 [source,properties]
@@ -1367,6 +1371,61 @@ and annotating it with `@PersistenceUnitExtension` (or `@PersistenceUnitExtensio
 will replace the current Quarkus default implementation `io.quarkus.hibernate.orm.runtime.tenant.DataSourceTenantConnectionResolver`.
 Your custom connection resolver would allow for example to read tenant information from a database and create a connection per tenant at runtime based on it.
 
+[CAUTION]
+====
+<<automatic-integration,Automatic integrations>> will **not** work with programmatically-created `ConnectionProvider`.
+This implies all these integrations, including those from other Quarkus modules (e.g. xref:smallrye-health.adoc[SmallRye Health]) must be done manually.
+====
+
+Here is an implementation example of a `TenantConnectionResolver` implementation using standard Quarkus technologies – Agroal for pooling and Narayana for transactions:
+
+[source,java]
+----
+@ApplicationScoped
+@PersistenceUnitExtension
+public class ExampleTenantConnectionResolver implements TenantConnectionResolver {
+
+    private final jakarta.transaction.TransactionManager transactionManager;
+    private final TransactionSynchronizationRegistry transactionSynchronizationRegistry;
+
+    public ExampleTenantConnectionResolver(
+            TransactionManager transactionManager,
+            TransactionSynchronizationRegistry transactionSynchronizationRegistry) {
+        this.transactionManager = transactionManager;
+        this.transactionSynchronizationRegistry = transactionSynchronizationRegistry;
+    }
+
+    @Override
+    public ConnectionProvider resolve(String tenantId) {
+        // Use your own ConnectionProvider implementation here
+        return new YourOwnCustomConnectionProviderImpl(createDatasource(tenantId));
+    }
+
+    private AgroalDataSource createDatasource(String tenantId) {
+        try {
+            final var txIntegration = new NarayanaTransactionIntegration(
+                    transactionManager, transactionSynchronizationRegistry, null, false, null);
+            // Fetch JDBC URL, username, password & other values from a per-tenant dynamic source
+            final var dataSourceConfig = new AgroalDataSourceConfigurationSupplier()
+                    .connectionPoolConfiguration(pc -> pc.initialSize(2)
+                            .maxSize(10)
+                            .minSize(2)
+                            .maxLifetime(Duration.of(5, ChronoUnit.MINUTES))
+                            .acquisitionTimeout(Duration.of(30, ChronoUnit.SECONDS))
+                            .transactionIntegration(txIntegration)
+                            .connectionFactoryConfiguration(
+                                    cf -> cf.jdbcUrl("jdbc:postgresql://postgres:5432/" + tenantId)
+                                            .credential(new NamePrincipal(username))
+                                            .credential(new SimplePassword(password))));
+            return AgroalDataSource.from(dataSourceConfig.get());
+        } catch (SQLException ex) {
+            throw new IllegalStateException(
+                    "Failed to create a new data source based on the existing datasource configuration", ex);
+        }
+    }
+}
+----
+
 [[interceptors]]
 == Interceptors
 

_versions/main/guides/jreleaser.adoc

@@ -635,7 +635,7 @@ As a reference, these are the full contents of the `pom.xml`:
   <properties>
     <executable-suffix/>
     <distribution.directory>${project.build.directory}/distributions</distribution.directory>
-    <compiler-plugin.version>3.13.0</compiler-plugin.version>
+    <compiler-plugin.version>3.14.0</compiler-plugin.version>
     <maven.compiler.parameters>true</maven.compiler.parameters>
     <maven.compiler.source>17</maven.compiler.source>
     <maven.compiler.target>17</maven.compiler.target>

_versions/main/guides/quarkus-runtime-base-image.adoc

@@ -39,7 +39,7 @@ In this case, you need to use a multi-stage `dockerfile` to copy the required li
 ----
 # First stage - install the dependencies in an intermediate container
 FROM registry.access.redhat.com/ubi9/ubi-minimal:9.5 as BUILD
-RUN microdnf install freetype
+RUN microdnf install freetype -y
 
 # Second stage - copy the dependencies
 FROM quay.io/quarkus/ubi9-quarkus-micro-image:2.0
@@ -61,7 +61,7 @@ If you need to have access to the full AWT support, you need more than just `lib
 ----
 # First stage - install the dependencies in an intermediate container
 FROM registry.access.redhat.com/ubi9/ubi-minimal:9.5 as BUILD
-RUN microdnf install freetype fontconfig
+RUN microdnf install freetype fontconfig -y
 
 # Second stage - copy the dependencies
 FROM quay.io/quarkus/ubi9-quarkus-micro-image:2.0

_versions/main/guides/rest.adoc

@@ -1627,6 +1627,20 @@ public User userPrivate() {
 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.
 
+`@JsonView` is also supported for deserializing the request body. So for example in the following code:
+
+[source,java]
+----
+        @POST
+        @Produces(MediaType.APPLICATION_JSON)
+        @Consumes(MediaType.APPLICATION_JSON)
+        public RestResponse<User> create(@JsonView(Views.Public.class) User user) {
+            return RestResponse.status(CREATED, user);
+        }
+----
+
+inside the `create` method, `user` would only contain the value of `name` while `id` would always be `null` (regardless if the JSON request contained it)
+
 ===== Reflection-free Jackson serialization and deserialization
 
 By default, Jackson uses reflection to convert objects to and from JSON.