Sync documentation of main branch

actions-user · actions-user · commit f87e94d98868 · 2025-12-19T01:59:48.000Z
diff --git a/_generated-doc/main/config/quarkus-all-config.adoc b/_generated-doc/main/config/quarkus-all-config.adoc
@@ -98493,4 +98493,4 @@ A size configuration option recognizes strings in this format (shown as a regula
 
 If no suffix is given, assume bytes.
 ====
-ifndef::no-memory-size-note[]
+endif::no-memory-size-note[]
diff --git a/_generated-doc/main/config/quarkus-core_quarkus.log.adoc b/_generated-doc/main/config/quarkus-core_quarkus.log.adoc
@@ -2442,4 +2442,4 @@ A size configuration option recognizes strings in this format (shown as a regula
 
 If no suffix is given, assume bytes.
 ====
-ifndef::no-memory-size-note[]
+endif::no-memory-size-note[]
diff --git a/_generated-doc/main/config/quarkus-devservices-keycloak.adoc b/_generated-doc/main/config/quarkus-devservices-keycloak.adoc
@@ -505,4 +505,4 @@ A size configuration option recognizes strings in this format (shown as a regula
 
 If no suffix is given, assume bytes.
 ====
-ifndef::no-memory-size-note[]
+endif::no-memory-size-note[]
diff --git a/_generated-doc/main/config/quarkus-devservices-keycloak_quarkus.keycloak.adoc b/_generated-doc/main/config/quarkus-devservices-keycloak_quarkus.keycloak.adoc
@@ -505,4 +505,4 @@ A size configuration option recognizes strings in this format (shown as a regula
 
 If no suffix is given, assume bytes.
 ====
-ifndef::no-memory-size-note[]
+endif::no-memory-size-note[]
diff --git a/_generated-doc/main/config/quarkus-rest-client-config.adoc b/_generated-doc/main/config/quarkus-rest-client-config.adoc
@@ -2010,4 +2010,4 @@ A size configuration option recognizes strings in this format (shown as a regula
 
 If no suffix is given, assume bytes.
 ====
-ifndef::no-memory-size-note[]
+endif::no-memory-size-note[]
diff --git a/_generated-doc/main/config/quarkus-rest-client-config_quarkus.rest-client.adoc b/_generated-doc/main/config/quarkus-rest-client-config_quarkus.rest-client.adoc
@@ -2010,4 +2010,4 @@ A size configuration option recognizes strings in this format (shown as a regula
 
 If no suffix is given, assume bytes.
 ====
-ifndef::no-memory-size-note[]
+endif::no-memory-size-note[]
diff --git a/_generated-doc/main/config/quarkus-rest-common_quarkus.rest.adoc b/_generated-doc/main/config/quarkus-rest-common_quarkus.rest.adoc
@@ -276,4 +276,4 @@ A size configuration option recognizes strings in this format (shown as a regula
 
 If no suffix is given, assume bytes.
 ====
-ifndef::no-memory-size-note[]
+endif::no-memory-size-note[]
diff --git a/_generated-doc/main/config/quarkus-resteasy-common_quarkus.resteasy.adoc b/_generated-doc/main/config/quarkus-resteasy-common_quarkus.resteasy.adoc
@@ -83,4 +83,4 @@ A size configuration option recognizes strings in this format (shown as a regula
 
 If no suffix is given, assume bytes.
 ====
-ifndef::no-memory-size-note[]
+endif::no-memory-size-note[]
diff --git a/_generated-doc/main/config/quarkus-undertow.adoc b/_generated-doc/main/config/quarkus-undertow.adoc
@@ -170,4 +170,4 @@ A size configuration option recognizes strings in this format (shown as a regula
 
 If no suffix is given, assume bytes.
 ====
-ifndef::no-memory-size-note[]
+endif::no-memory-size-note[]
diff --git a/_generated-doc/main/config/quarkus-undertow_quarkus.servlet.adoc b/_generated-doc/main/config/quarkus-undertow_quarkus.servlet.adoc
@@ -170,4 +170,4 @@ A size configuration option recognizes strings in this format (shown as a regula
 
 If no suffix is given, assume bytes.
 ====
-ifndef::no-memory-size-note[]
+endif::no-memory-size-note[]
diff --git a/_generated-doc/main/config/quarkus-vertx-http_quarkus.http.limits.adoc b/_generated-doc/main/config/quarkus-vertx-http_quarkus.http.limits.adoc
@@ -358,4 +358,4 @@ A size configuration option recognizes strings in this format (shown as a regula
 
 If no suffix is given, assume bytes.
 ====
-ifndef::no-memory-size-note[]
+endif::no-memory-size-note[]
diff --git a/_generated-doc/main/config/quarkus-vertx-http_quarkus.management.adoc b/_generated-doc/main/config/quarkus-vertx-http_quarkus.management.adoc
@@ -2183,4 +2183,4 @@ A size configuration option recognizes strings in this format (shown as a regula
 
 If no suffix is given, assume bytes.
 ====
-ifndef::no-memory-size-note[]
+endif::no-memory-size-note[]
diff --git a/_generated-doc/main/infra/quarkus-all-build-items.adoc b/_generated-doc/main/infra/quarkus-all-build-items.adoc
@@ -1724,6 +1724,25 @@ _No Javadoc found_
 
 
 
+a| https://github.com/quarkusio/quarkus/blob/main/core/deployment/src/main/java/io/quarkus/deployment/builditem/ModuleOpenBuildItem.java[`io.quarkus.deployment.builditem.ModuleOpenBuildItem`, window="_blank"]
+[.description]
+--
+This will generate the equivalent of "--add-opens=[openedModule/package(s)]=[openingModule]" for all runners of the generated application. Some limitations apply which will depend on the launch mode of Quarkus; specifically, when generating a runnable Jar we can only open a module to ALL-UNNAMED; this is considered acceptable at the time of writing as extensions are generally placed on the classpath for both fast-jar and uber-jar packaging formats. We expect this to evolve as further packaging formats are introduced which would better leverage the module system. We specifically don't allow opening a module to "ALL-UNNAMED" explicitly to encourage using the module names that a library has or will have in the near future: for this reason, when a module name is provided which doesn't exist, we map it to the unnamed module. This should be treated as an implementation detail of the current packaging format and is most likely bound to evolve. When running integration tests, we aim to run the tests within module access rules consistent with the production packaging modes, but as we need to dynamically modify the module system's access restrictions we need to apply these rules to specific, targeted classloaders: we'll only instrument the unnamed module relating to the Quarkus app classloader. This should be effective but is based on the general understanding that libraries within Quarkus shouldn't use custom classloaders; should this assumption be violated, there's the risk of a "module opens" instruction to not be applied automatically, and users would be required to issue the matching command line flags.
+-- a|`java.lang.String openedModuleName` 
+
+_No Javadoc found_
+
+`java.lang.String openingModuleName` 
+
+_No Javadoc found_
+
+`java.util.Set<String> packageNames` 
+
+_No Javadoc found_
+
+
+
+
 a| https://github.com/quarkusio/quarkus/blob/main/core/deployment/src/main/java/io/quarkus/deployment/builditem/NamedLogHandlersBuildItem.java[`io.quarkus.deployment.builditem.NamedLogHandlersBuildItem`, window="_blank"]
 [.description]
 --
diff --git a/_versions/main/guides/_attributes.adoc b/_versions/main/guides/_attributes.adoc
@@ -17,13 +17,13 @@
 :mysql-image: docker.io/library/mysql:8.4
 :oracle-image: docker.io/gvenzl/oracle-free:23-slim-faststart
 :postgres-image: docker.io/library/postgres:17
-:elasticsearch-version: 9.1.5
-:elasticsearch-image: docker.io/elastic/elasticsearch:9.1.5
-:opensearch-image: docker.io/opensearchproject/opensearch:3.1.0
+:elasticsearch-version: 9.2.2
+:elasticsearch-image: docker.io/elastic/elasticsearch:9.2.2
+:opensearch-image: docker.io/opensearchproject/opensearch:3.3.2
 :infinispan-version: ${infinispan.version}
 :infinispan-protostream-version: ${infinispan.protostream.version}
-:logstash-image: docker.io/elastic/logstash:9.1.5
-:kibana-image: docker.io/elastic/kibana:9.1.5
+:logstash-image: docker.io/elastic/logstash:9.2.2
+:kibana-image: docker.io/elastic/kibana:9.2.2
 :keycloak-image: quay.io/keycloak/keycloak:26.4.7
 :amqp-image: quay.io/artemiscloud/activemq-artemis-broker:1.0.25
 :apicurio-registry-image: quay.io/apicurio/apicurio-registry-mem:2.6.13.Final
@@ -35,14 +35,14 @@
 :infinispan-image: quay.io/infinispan/server:latest
 :jandex-version: 3.5.3
 :jandex-gradle-plugin-version: 2.3.0
-:kotlin-version: 2.2.21
+:kotlin-version: 2.3.0
 :grpc-version: 1.77.0
 :protoc-version: 4.32.1
 :gcf-invoker-version: 1.4.1
 // Cannot simply use the name 'hibernate-*-version' here as it somehow gets
 // overridden to the full version, at least when building locally.
-:hibernate-orm-version-major-minor: 7.1
-:hibernate-search-version-major-minor: 8.1
+:hibernate-orm-version-major-minor: 7.2
+:hibernate-search-version-major-minor: 8.2
 :hibernate-validator-version-major-minor: 9.1
 :jakarta-persistence-version-major-minor: 3.2
 // .
diff --git a/_versions/main/guides/_includes/extension-status.adoc b/_versions/main/guides/_includes/extension-status.adoc
@@ -22,4 +22,4 @@ endif::[]
 
 For a full list of possible statuses, check our https://quarkus.io/faq/#what-are-the-extension-statuses[FAQ entry].
 ====
-endif::[]
+endif::extension-status[]
diff --git a/_versions/main/guides/config-reference.adoc b/_versions/main/guides/config-reference.adoc
@@ -823,7 +823,7 @@ Maven projects could add the following goal to their `quarkus-maven-plugin` conf
               <goal>track-config-changes</goal>
             </goals>
           </execution>
-          <!-- other executions would follow below -->
+        </executions>
 ----
 
 The `track-config-changes` goal looks for `${project.basedir}/.quarkus/quarkus-prod-config-dump` (file name and directory are configurable) and, if the file already exists, checks whether the values stored in the config dump have changed.
diff --git a/_versions/main/guides/getting-started.adoc b/_versions/main/guides/getting-started.adoc
@@ -102,15 +102,6 @@ In addition, you can see the `quarkus-maven-plugin` responsible of the packaging
             <artifactId>quarkus-maven-plugin</artifactId>
             <version>${quarkus.platform.version}</version>
             <extensions>true</extensions>
-            <executions>
-                <execution>
-                    <goals>
-                        <goal>build</goal>
-                        <goal>generate-code</goal>
-                        <goal>generate-code-tests</goal>
-                    </goals>
-                </execution>
-            </executions>
         </plugin>
     </plugins>
 </build>
diff --git a/_versions/main/guides/grpc-generation-reference.adoc b/_versions/main/guides/grpc-generation-reference.adoc
@@ -29,26 +29,8 @@ To enable gRPC code generation, add the following dependency to your project:
 </dependency>
 ----
 
-Next, ensure that the `generate-code` phase is enabled in the Quarkus Maven plugin:
-
-[source,xml,subs=attributes+]
-----
-<plugin>
-    <groupId>${quarkus.platform.group-id}</groupId>
-    <artifactId>quarkus-maven-plugin</artifactId>
-    <version>${quarkus.platform.version}</version>
-    <extensions>true</extensions>
-    <executions>
-        <execution>
-            <goals>
-                <goal>build</goal>
-                <goal>generate-code</goal>
-                <goal>generate-code-tests</goal>
-            </goals>
-        </execution>
-    </executions>
-</plugin>
-----
+The `quarkus:generate-code` goal is executed by default during the Quarkus Maven plugin default lifecycle when using the `quarkus` packaging,
+and will handle the code generation.
 
 === Using Gradle
 
@@ -75,11 +57,6 @@ With Maven, add the following configuration:
     <extensions>true</extensions>
     <executions>
         <execution>
-            <goals>
-                <goal>build</goal>
-                <goal>generate-code</goal>
-                <goal>generate-code-tests</goal>
-            </goals>
             <configuration>
                 <properties>
                     <quarkus.grpc.codegen.proto-directory>${project.basedir}/ext/proto</quarkus.grpc.codegen.proto-directory>
diff --git a/_versions/main/guides/grpc-getting-started.adoc b/_versions/main/guides/grpc-getting-started.adoc
@@ -63,34 +63,9 @@ Under the `dependencies` section of your `pom.xml` file, make sure you have the
 implementation("io.quarkus:quarkus-rest")
 ----
 
-If you are using Maven, make sure you have the `generate-code` goal of `quarkus-maven-plugin` enabled in your `pom.xml`.
-If you wish to generate code from different `proto` files for tests, also add the `generate-code-tests` goal.
-Please note that no additional task/goal is required for the Gradle plugin.
+Whether you use Maven or Gradle, the code generation goals/tasks are automatically executed when using the default lifecycle of the plugins.
 
-[source,xml]
-----
-<build>
-    <plugins>
-        <plugin>
-            <groupId>io.quarkus</groupId>
-            <artifactId>quarkus-maven-plugin</artifactId>
-            <version>${quarkus-plugin.version}</version>
-            <extensions>true</extensions>
-            <executions>
-                <execution>
-                    <goals>
-                        <goal>build</goal>
-                        <goal>generate-code</goal>
-                        <goal>generate-code-tests</goal>
-                    </goals>
-                </execution>
-            </executions>
-        </plugin>
-    </plugins>
-</build>
-----
-
-With this configuration, you can put your service and message definitions in the `src/main/proto` directory.
+You can put your service and message definitions in the `src/main/proto` directory.
 `quarkus-maven-plugin` will generate Java files from your `proto` files.
 
 `quarkus-maven-plugin` retrieves a version of `protoc` (the protobuf compiler) from Maven repositories. The retrieved version matches your operating system and CPU architecture.
diff --git a/_versions/main/guides/grpc-reference.adoc b/_versions/main/guides/grpc-reference.adoc
@@ -29,26 +29,8 @@ To enable gRPC, add the following dependency to your project:
 </dependency>
 ----
 
-Next, ensure that the `generate-code` phase is enabled in the Quarkus Maven plugin:
-
-[source,xml,subs=attributes+]
-----
-<plugin>
-    <groupId>${quarkus.platform.group-id}</groupId>
-    <artifactId>quarkus-maven-plugin</artifactId>
-    <version>${quarkus.platform.version}</version>
-    <extensions>true</extensions>
-    <executions>
-        <execution>
-            <goals>
-                <goal>build</goal>
-                <goal>generate-code</goal>
-                <goal>generate-code-tests</goal>
-            </goals>
-        </execution>
-    </executions>
-</plugin>
-----
+The `quarkus:generate-code` goal is executed by default during the Quarkus Maven plugin default lifecycle when using the `quarkus` packaging,
+and will handle the code generation.
 
 === Using Gradle
 
diff --git a/_versions/main/guides/grpc-virtual-threads.adoc b/_versions/main/guides/grpc-virtual-threads.adoc
@@ -76,15 +76,6 @@ or to use the Quarkus Dev mode, insert the following to the `quarkus-maven-plugi
     <groupId>io.quarkus</groupId>
     <artifactId>quarkus-maven-plugin</artifactId>
     <version>${quarkus.version}</version>
-    <executions>
-        <execution>
-            <goals>
-                <goal>build</goal>
-                <goal>generate-code</goal>
-                <goal>generate-code-tests</goal>
-            </goals>
-        </execution>
-    </executions>
     <configuration>
       <source>21</source>
       <target>21</target>
diff --git a/_versions/main/guides/hibernate-search-orm-elasticsearch.adoc b/_versions/main/guides/hibernate-search-orm-elasticsearch.adoc
@@ -820,7 +820,7 @@ as shown below.
 
 [source,properties]
 ----
-quarkus.hibernate-search-orm.elasticsearch.version=opensearch:3.1
+quarkus.hibernate-search-orm.elasticsearch.version=opensearch:3.3
 ----
 
 All other configuration options and APIs are exactly the same as with Elasticsearch.
diff --git a/_versions/main/guides/hibernate-search-standalone-elasticsearch.adoc b/_versions/main/guides/hibernate-search-standalone-elasticsearch.adoc
@@ -738,7 +738,7 @@ as shown below.
 
 [source,properties]
 ----
-quarkus.hibernate-search-standalone.elasticsearch.version=opensearch:3.1
+quarkus.hibernate-search-standalone.elasticsearch.version=opensearch:3.3
 ----
 
 All other configuration options and APIs are exactly the same as with Elasticsearch.
diff --git a/_versions/main/guides/jreleaser.adoc b/_versions/main/guides/jreleaser.adoc
@@ -693,15 +693,6 @@ As a reference, these are the full contents of the `pom.xml`:
         <artifactId>quarkus-maven-plugin</artifactId>
         <version>${quarkus.platform.version}</version>
         <extensions>true</extensions>
-        <executions>
-          <execution>
-            <goals>
-              <goal>build</goal>
-              <goal>generate-code</goal>
-              <goal>generate-code-tests</goal>
-            </goals>
-          </execution>
-        </executions>
       </plugin>
       <plugin>
         <artifactId>maven-compiler-plugin</artifactId>
diff --git a/_versions/main/guides/logging.adoc b/_versions/main/guides/logging.adoc
diff --git a/_versions/main/guides/maven-tooling.adoc b/_versions/main/guides/maven-tooling.adoc
diff --git a/_versions/main/guides/native-reference.adoc b/_versions/main/guides/native-reference.adoc
diff --git a/_versions/main/guides/quarkus-maven-plugin.adoc b/_versions/main/guides/quarkus-maven-plugin.adoc
diff --git a/_versions/main/guides/rest-client.adoc b/_versions/main/guides/rest-client.adoc
