Sync documentation of main branch

actions-user · actions-user · commit fec699d34bb6 · 2024-11-27T02:01:59.000Z
diff --git a/_generated-doc/main/config/quarkus-all-config.adoc b/_generated-doc/main/config/quarkus-all-config.adoc
@@ -16029,10 +16029,12 @@ endif::add-copy-button-to-config-props[]
 --
 The HTTP host
 
-Defaults to 0.0.0.0
+In dev/test mode this defaults to localhost, in prod mode this defaults to 0.0.0.0
 
 Defaulting to 0.0.0.0 makes it easier to deploy Quarkus to container, however it is not suitable for dev/test mode as other people on the network can connect to your development machine.
 
+As an exception, when running in Windows Subsystem for Linux (WSL), the HTTP host defaults to 0.0.0.0 even in dev/test mode since using localhost makes the application inaccessible.
+
 
 ifdef::add-copy-button-to-env-var[]
 Environment variable: env_var_with_copy_button:+++QUARKUS_MANAGEMENT_HOST+++[]
@@ -16042,7 +16044,7 @@ Environment variable: `+++QUARKUS_MANAGEMENT_HOST+++`
 endif::add-copy-button-to-env-var[]
 --
 |string
-|
+|required icon:exclamation-circle[title=Configuration property is required]
 
 a| [[quarkus-vertx-http_quarkus-management-host-enabled]] [.property-path]##link:#quarkus-vertx-http_quarkus-management-host-enabled[`quarkus.management.host-enabled`]##
 ifdef::add-copy-button-to-config-props[]
@@ -80998,7 +81000,7 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-The hostname verification algorithm to use in case the server's identity should be checked. Should be `HTTPS`, `LDAPS` or an `NONE` (default).
+The hostname verification algorithm to use in case the server's identity should be checked. Should be `HTTPS`, `LDAPS` or `NONE` (default).
 
 If set to `NONE`, it does not verify the hostname.
 
@@ -81997,7 +81999,7 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-The hostname verification algorithm to use in case the server's identity should be checked. Should be `HTTPS`, `LDAPS` or an `NONE` (default).
+The hostname verification algorithm to use in case the server's identity should be checked. Should be `HTTPS`, `LDAPS` or `NONE` (default).
 
 If set to `NONE`, it does not verify the hostname.
 
@@ -90800,7 +90802,7 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-The hostname verification algorithm to use in case the server's identity should be checked. Should be `HTTPS` (default), `LDAPS` or an `NONE`.
+The hostname verification algorithm to use in case the server's identity should be checked. Should be `HTTPS` (default), `LDAPS` or `NONE`.
 
 If set to `NONE`, it does not verify the hostname.
 
@@ -91734,7 +91736,7 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-The hostname verification algorithm to use in case the server's identity should be checked. Should be `HTTPS` (default), `LDAPS` or an `NONE`.
+The hostname verification algorithm to use in case the server's identity should be checked. Should be `HTTPS` (default), `LDAPS` or `NONE`.
 
 If set to `NONE`, it does not verify the hostname.
 
diff --git a/_generated-doc/main/config/quarkus-redis-client.adoc b/_generated-doc/main/config/quarkus-redis-client.adoc
@@ -2503,7 +2503,7 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-The hostname verification algorithm to use in case the server's identity should be checked. Should be `HTTPS`, `LDAPS` or an `NONE` (default).
+The hostname verification algorithm to use in case the server's identity should be checked. Should be `HTTPS`, `LDAPS` or `NONE` (default).
 
 If set to `NONE`, it does not verify the hostname.
 
@@ -3502,7 +3502,7 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-The hostname verification algorithm to use in case the server's identity should be checked. Should be `HTTPS`, `LDAPS` or an `NONE` (default).
+The hostname verification algorithm to use in case the server's identity should be checked. Should be `HTTPS`, `LDAPS` or `NONE` (default).
 
 If set to `NONE`, it does not verify the hostname.
 
diff --git a/_generated-doc/main/config/quarkus-redis-client_quarkus.redis.adoc b/_generated-doc/main/config/quarkus-redis-client_quarkus.redis.adoc
@@ -2503,7 +2503,7 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-The hostname verification algorithm to use in case the server's identity should be checked. Should be `HTTPS`, `LDAPS` or an `NONE` (default).
+The hostname verification algorithm to use in case the server's identity should be checked. Should be `HTTPS`, `LDAPS` or `NONE` (default).
 
 If set to `NONE`, it does not verify the hostname.
 
@@ -3502,7 +3502,7 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-The hostname verification algorithm to use in case the server's identity should be checked. Should be `HTTPS`, `LDAPS` or an `NONE` (default).
+The hostname verification algorithm to use in case the server's identity should be checked. Should be `HTTPS`, `LDAPS` or `NONE` (default).
 
 If set to `NONE`, it does not verify the hostname.
 
diff --git a/_generated-doc/main/config/quarkus-tls-registry.adoc b/_generated-doc/main/config/quarkus-tls-registry.adoc
@@ -794,7 +794,7 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-The hostname verification algorithm to use in case the server's identity should be checked. Should be `HTTPS` (default), `LDAPS` or an `NONE`.
+The hostname verification algorithm to use in case the server's identity should be checked. Should be `HTTPS` (default), `LDAPS` or `NONE`.
 
 If set to `NONE`, it does not verify the hostname.
 
@@ -1728,7 +1728,7 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-The hostname verification algorithm to use in case the server's identity should be checked. Should be `HTTPS` (default), `LDAPS` or an `NONE`.
+The hostname verification algorithm to use in case the server's identity should be checked. Should be `HTTPS` (default), `LDAPS` or `NONE`.
 
 If set to `NONE`, it does not verify the hostname.
 
diff --git a/_generated-doc/main/config/quarkus-tls-registry_quarkus.tls.adoc b/_generated-doc/main/config/quarkus-tls-registry_quarkus.tls.adoc
@@ -794,7 +794,7 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-The hostname verification algorithm to use in case the server's identity should be checked. Should be `HTTPS` (default), `LDAPS` or an `NONE`.
+The hostname verification algorithm to use in case the server's identity should be checked. Should be `HTTPS` (default), `LDAPS` or `NONE`.
 
 If set to `NONE`, it does not verify the hostname.
 
@@ -1728,7 +1728,7 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-The hostname verification algorithm to use in case the server's identity should be checked. Should be `HTTPS` (default), `LDAPS` or an `NONE`.
+The hostname verification algorithm to use in case the server's identity should be checked. Should be `HTTPS` (default), `LDAPS` or `NONE`.
 
 If set to `NONE`, it does not verify the hostname.
 
diff --git a/_generated-doc/main/config/quarkus-vertx-http_quarkus.management.adoc b/_generated-doc/main/config/quarkus-vertx-http_quarkus.management.adoc
@@ -279,10 +279,12 @@ endif::add-copy-button-to-config-props[]
 --
 The HTTP host
 
-Defaults to 0.0.0.0
+In dev/test mode this defaults to localhost, in prod mode this defaults to 0.0.0.0
 
 Defaulting to 0.0.0.0 makes it easier to deploy Quarkus to container, however it is not suitable for dev/test mode as other people on the network can connect to your development machine.
 
+As an exception, when running in Windows Subsystem for Linux (WSL), the HTTP host defaults to 0.0.0.0 even in dev/test mode since using localhost makes the application inaccessible.
+
 
 ifdef::add-copy-button-to-env-var[]
 Environment variable: env_var_with_copy_button:+++QUARKUS_MANAGEMENT_HOST+++[]
@@ -292,7 +294,7 @@ Environment variable: `+++QUARKUS_MANAGEMENT_HOST+++`
 endif::add-copy-button-to-env-var[]
 --
 |string
-|
+|required icon:exclamation-circle[title=Configuration property is required]
 
 a| [[quarkus-vertx-http_quarkus-management-host-enabled]] [.property-path]##link:#quarkus-vertx-http_quarkus-management-host-enabled[`quarkus.management.host-enabled`]##
 ifdef::add-copy-button-to-config-props[]
diff --git a/_generated-doc/main/infra/quarkus-all-build-items.adoc b/_generated-doc/main/infra/quarkus-all-build-items.adoc
@@ -953,6 +953,14 @@ _No Javadoc found_
 
 _No Javadoc found_
 
+`java.lang.String binaryName` 
+
+_No Javadoc found_
+
+`java.lang.String internalName` 
+
+_No Javadoc found_
+
 `byte[] classData` 
 
 _No Javadoc found_
@@ -4185,7 +4193,7 @@ h|Attributes
 
 
 
-a| https://github.com/quarkusio/quarkus/blob/main/extensions/panache/hibernate-reactive-panache/deployment/src/main/java/io/quarkus/hibernate/reactive/panache/common/deployment/PanacheEntityClassBuildItem.java[`io.quarkus.hibernate.reactive.panache.common.deployment.PanacheEntityClassBuildItem`, window="_blank"]
+a| https://github.com/quarkusio/quarkus/blob/main/extensions/panache/hibernate-reactive-panache/deployment/src/main/java/io/quarkus/hibernate/reactive/panache/deployment/PanacheEntityClassBuildItem.java[`io.quarkus.hibernate.reactive.panache.deployment.PanacheEntityClassBuildItem`, window="_blank"]
 [.description]
 --
 Represents a regular Panache entity class.
diff --git a/_versions/main/guides/conditional-extension-dependencies.adoc b/_versions/main/guides/conditional-extension-dependencies.adoc
@@ -9,19 +9,19 @@ include::_attributes.adoc[]
 :summary: Trigger the inclusion on additional extensions based on certain conditions.
 :topics: extensions
 
-Quarkus extension dependencies are usually configured in the same way as any other project dependencies in a project's build file, e.g. the Maven `pom.xml` or the Gradle build scripts. However, Quarkus also supports types of dependencies that aren't supported out-of-the-box by Maven and Gradle. Conditional Quarkus extension dependencies falls into that category.
+Quarkus extension dependencies are usually configured in the same way as any other project dependencies in a project's build file, for example the Maven `pom.xml` or the Gradle build scripts. However, Quarkus also supports types of dependencies that aren't supported out-of-the-box by Maven and Gradle. Conditional Quarkus extension dependencies is one such example.
 
 == Conditional Dependencies
 
-A conditional dependency is a dependency that is activated only if a certain condition is satisfied. If the condition is not satisfied then the dependency **must not** be activated. In that regard, conditional dependencies can be categorized as optional, meaning they may or may not appear in the resulting dependency graph.
+A conditional dependency is a dependency that is activated only if a certain condition is satisfied. If the condition is not satisfied then the dependency **will not** be activated. In that regard, conditional dependencies can be categorized as optional, meaning they may or may not appear in the resulting dependency graph.
 
 A typical example of a conditional dependency would be a component that should be added to the classpath **only** in case all of its required dependencies are present on the classpath. If one or more of the component's required dependencies aren't available, instead of failing, the component should simply not be added.
 
 == Conditional Quarkus Extension Dependencies
 
-A Quarkus extension may declare one or more conditional dependencies on other Quarkus extensions. Conditional dependencies on and from non-extension artifacts aren't supported.
+A Quarkus extension may declare one or more conditional dependencies on other Quarkus extensions or regular Maven artifacts.
 
-Let's consider the following scenario as an example: `quarkus-extension-a` has an optional dependency on `quarkus-extension-b` which should be included in a Quarkus application only if `quarkus-extension-c` is found among the application dependencies (direct or transitive). In this case, the presence of `quarkus-extension-c` is the condition which, if satisfied, will trigger inclusion of the `quarkus-extension-b` when Quarkus application dependencies are resolved.
+Let's consider the following scenario as an example: `quarkus-extension-a` has an optional dependency on `quarkus-extension-b` which should be included in a Quarkus application only if `quarkus-extension-c` is found among the application dependencies (direct or transitive). In this case, the presence of `quarkus-extension-c` is the condition, which, if satisfied, will trigger inclusion of the `quarkus-extension-b` when Quarkus application dependencies are resolved.
 
 The condition which triggers activation of an extension is configured in the extension's `META-INF/quarkus-extension.properties`, which is included in the runtime artifact of the extension. Extension developers can add the following configuration to express the condition which would have to be satisfied for the extension to be activated:
 
@@ -66,11 +66,13 @@ The condition which triggers activation of an extension is configured in the ext
 <3> configuration of the dependency condition which will have to be satisfied for this extension to be added to a Quarkus application expressed as a list of artifacts that must be present among the application dependencies;
 <4> an artifact key (in the format of `groupId:artifactId[:<classifier>:<extension>]` but typically simply `<groupId>:<artifactId>`) of the artifact that must be present among the application dependencies for the condition to be satisfied.
 
-NOTE: In the example above the `artifact` used in the condition configuration happens to be a runtime Quarkus extension artifact but it could as well be any other artifact. There could also be more than one `artifact` element in the body of the `dependencyCondition`.
+NOTE: In the example above the `artifact` used in the condition configuration happens to be a runtime Quarkus extension artifact but it could as well be any other artifact.
+
+The `dependencyCondition` element may contain more than `artifact`, in which case all the configured artifacts must be present on the classpath for the condition to be satisfied.
 
 Now, having a dependency condition recorded in the descriptor of the `quarkus-extension-b`, other extensions may declare a conditional dependency on it.
 
-NOTE: extensions with dependency conditions present in their metadata could still appear as regular dependencies in Maven `pom.xml` and Gradle build scripts.
+NOTE: extensions with dependency conditions present in their metadata could still appear as regular dependencies in Maven `pom.xml` and Gradle build scripts, in which case their conditions will simply be ignored.
 
 A conditional dependency is configured in the runtime artifact of a Quarkus extension. In this example, the `quarkus-extension-a` will declare a conditional dependency on the `quarkus-extension-b`, which can be done in the following two ways.
 
@@ -164,7 +166,7 @@ Conditional dependencies can also be configured in the Quarkus extension descrip
             </goals>
             <configuration>
               <conditionalDependencies> <3>
-                <extension>org.acme:quarkus-extension-b:${b.version}</extension> <4>
+                <artifact>org.acme:quarkus-extension-b:${b.version}</artifact> <4>
               </conditionalDependencies>
             </configuration>
           </execution>
@@ -212,7 +214,7 @@ Dev mode-only extension dependencies can be configured in the Quarkus extension
             </goals>
             <configuration>
               <conditionalDevDependencies> <3>
-                <extension>org.acme:quarkus-extension-b:${b.version}</extension> <4>
+                <artifact>org.acme:quarkus-extension-b:${b.version}</artifact> <4>
               </conditionalDevDependencies>
             </configuration>
           </execution>
@@ -223,11 +225,58 @@ Dev mode-only extension dependencies can be configured in the Quarkus extension
 ----
 <1> the runtime Quarkus extension artifact ID;
 <2> the goal that generates the extension descriptor which every Quarkus runtime extension project should be configured with;
-<3> the dev mode conditional dependency configuration element;
-<4> the artifact coordinates of conditional dependencies on extensions that should be evaluated only if an application is launched in dev mode.
+<3> conditional dependencies that should be evaluated only in dev mode;
+<4> the artifact coordinates of a conditional dependency.
 
 The `quarkus-extension-b`, in this example, may or may not define its own condition to be evaluated.
 
 If the `quarkus-extension-b` does not define a dependency condition on its own (there is no dependency condition recorded in its `META-INF/quarkus-extension.properties`), the `quarkus-extension-b` will only be added as a dependency of the `quarkus-extension-a` in dev mode but not in other modes (prod or test).
 
 If the `quarkus-extension-b` does define a dependency condition on its own (a dependency condition recorded in its `META-INF/quarkus-extension.properties`), the `quarkus-extension-b` will be added as a dependency of the `quarkus-extension-a` in dev mode only if its condition is satisfied (the artifacts it requires are present in the application dependency graph).
+
+=== Dev mode dependencies on regular Maven artifacts
+
+Extensions may also declare conditional dependencies on regular Maven artifacts, that are not Quarkus extensions. Given that regular Maven artifacts do not include Quarkus metadata, the condition for their inclusion is configured by an extension depending on them.
+
+For example
+[source,xml]
+----
+<project xmlns="http://maven.apache.org/POM/4.0.0"
+         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd">
+
+  <!-- SKIPPED CONTENT -->
+
+  <artifactId>quarkus-extension-a</artifactId> <1>
+
+  <!-- SKIPPED CONTENT -->
+
+  <build>
+    <plugins>
+      <plugin>
+        <groupId>io.quarkus</groupId>
+        <artifactId>quarkus-extension-maven-plugin</artifactId>
+        <version>${quarkus.version}</version>
+        <executions>
+          <execution>
+            <phase>process-resources</phase>
+            <goals>
+              <goal>extension-descriptor</goal> <2>
+            </goals>
+            <configuration>
+              <conditionalDevDependencies> <3>
+                <artifact>org.acme:library-b:${b.version}</artifact> <4>
+              </conditionalDevDependencies>
+            </configuration>
+          </execution>
+        </executions>
+      </plugin>
+
+  <!-- SKIPPED CONTENT -->
+----
+<1> the runtime Quarkus extension artifact ID;
+<2> the goal that generates the extension descriptor which every Quarkus runtime extension project should be configured with;
+<3> conditional dependencies that should be evaluated only in dev mode;
+<4> the artifact coordinates of a conditional dependency.
+
+In this example `library-b` is a regular Maven artifact that will be added as a dependency of the `quarkus-extension-a` only when an application is launched in dev mode.
diff --git a/_versions/main/guides/management-interface-reference.adoc b/_versions/main/guides/management-interface-reference.adoc
@@ -40,15 +40,30 @@ NOTE: The management interface is disabled when no extensions relying on it (suc
 By default, the management interface is exposed on the interface: `0.0.0.0` (all interfaces) and on the port `9000` (`9001` in test mode).
 It does not use TLS (`https`) by default.
 
-You can configure the host, ports, and TLS certificates using the following properties:
+You can configure the host, ports, and TLS configuration name using the following properties:
 
 * `quarkus.management.host` - the interface / host
 * `quarkus.management.port` - the port
 * `quarkus.management.test-port` - the port to use in test mode
-* `quarkus.management.ssl` - the TLS configuration, xref:http-reference#ssl[same as for the main HTTP server].
+* `quarkus.management.tls-configuration-name` - the TLS configuration name, xref:http-reference.adoc#using-the-tls-centralized-configuration[same as for the main HTTP server].
 
 Here is a configuration example exposing the management interface on _https://localhost:9002_:
 
+[source, properties]
+----
+quarkus.management.enabled=true
+quarkus.management.host=localhost
+quarkus.management.port=9002
+quarkus.management.tls-configuration-name=management
+
+# Your TLS registry configuration
+...
+----
+
+With this configuration, TLS is enabled and configured as defined in the `management` configuration of the TLS registry.
+
+You can also configure the management interface with the legacy SSL configuration, as for (xref:http-reference.adoc#ssl[the main HTTP server]):
+
 [source, properties]
 ----
 quarkus.management.enabled=true
diff --git a/_versions/main/guides/rest-client.adoc b/_versions/main/guides/rest-client.adoc
