Sync documentation of main branch

Author: actions-user

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

@@ -10081,6 +10081,29 @@ endif::add-copy-button-to-env-var[]
 |string
 |
 
+a|icon:lock[title=Fixed at build time] [[quarkus-core_quarkus-package-output-timestamp]] [.property-path]##link:#quarkus-core_quarkus-package-output-timestamp[`quarkus.package.output-timestamp`]##
+ifdef::add-copy-button-to-config-props[]
+config_property_copy_button:+++quarkus.package.output-timestamp+++[]
+endif::add-copy-button-to-config-props[]
+
+
+[.description]
+--
+The timestamp used as a reference for generating the packages (e.g. for the creation timestamp of ZIP entries).
+
+The approach is similar to what is done by the maven-jar-plugin with `project.build.outputTimestamp`.
+
+
+ifdef::add-copy-button-to-env-var[]
+Environment variable: env_var_with_copy_button:+++QUARKUS_PACKAGE_OUTPUT_TIMESTAMP+++[]
+endif::add-copy-button-to-env-var[]
+ifndef::add-copy-button-to-env-var[]
+Environment variable: `+++QUARKUS_PACKAGE_OUTPUT_TIMESTAMP+++`
+endif::add-copy-button-to-env-var[]
+--
+|link:https://docs.oracle.com/en/java/javase/17/docs/api/java.base/java/time/Instant.html[Instant]
+|
+
 a|icon:lock[title=Fixed at build time] [[quarkus-core_quarkus-package-write-transformed-bytecode-to-build-output]] [.property-path]##link:#quarkus-core_quarkus-package-write-transformed-bytecode-to-build-output[`quarkus.package.write-transformed-bytecode-to-build-output`]##
 ifdef::add-copy-button-to-config-props[]
 config_property_copy_button:+++quarkus.package.write-transformed-bytecode-to-build-output+++[]

_generated-doc/main/config/quarkus-core_quarkus.package.adoc

@@ -497,6 +497,29 @@ endif::add-copy-button-to-env-var[]
 |string
 |
 
+a|icon:lock[title=Fixed at build time] [[quarkus-core_quarkus-package-output-timestamp]] [.property-path]##link:#quarkus-core_quarkus-package-output-timestamp[`quarkus.package.output-timestamp`]##
+ifdef::add-copy-button-to-config-props[]
+config_property_copy_button:+++quarkus.package.output-timestamp+++[]
+endif::add-copy-button-to-config-props[]
+
+
+[.description]
+--
+The timestamp used as a reference for generating the packages (e.g. for the creation timestamp of ZIP entries).
+
+The approach is similar to what is done by the maven-jar-plugin with `project.build.outputTimestamp`.
+
+
+ifdef::add-copy-button-to-env-var[]
+Environment variable: env_var_with_copy_button:+++QUARKUS_PACKAGE_OUTPUT_TIMESTAMP+++[]
+endif::add-copy-button-to-env-var[]
+ifndef::add-copy-button-to-env-var[]
+Environment variable: `+++QUARKUS_PACKAGE_OUTPUT_TIMESTAMP+++`
+endif::add-copy-button-to-env-var[]
+--
+|link:https://docs.oracle.com/en/java/javase/17/docs/api/java.base/java/time/Instant.html[Instant]
+|
+
 a|icon:lock[title=Fixed at build time] [[quarkus-core_quarkus-package-write-transformed-bytecode-to-build-output]] [.property-path]##link:#quarkus-core_quarkus-package-write-transformed-bytecode-to-build-output[`quarkus.package.write-transformed-bytecode-to-build-output`]##
 ifdef::add-copy-button-to-config-props[]
 config_property_copy_button:+++quarkus.package.write-transformed-bytecode-to-build-output+++[]

_versions/main/guides/command-mode-reference.adoc

@@ -248,7 +248,17 @@ public class HelloIT extends HelloTest {
 }
 ----
 
-=== Mocking
+=== Limitations
+
+`@QuarkusMainTest` does **not** support the following features:
+
+- Injection of CDI beans
+- Using Panache entities
+- Using mocks with `@InjectMock`
+
+Usually, it's best to use a combination of `@QuarkusMainTest` tests for testing application externals, and `@QuarkusTest` tests for fine-grained testing which requires access to application internals.
+
+==== Mocking
 
 CDI injection is not supported in the `@QuarkusMainTest` tests.
 Consequently, mocking CDI beans with `QuarkusMock` or `@InjectMock` is not supported either.

_versions/main/guides/container-image.adoc

@@ -30,7 +30,7 @@ when all that is needed is the ability to push to a container image registry.
 
 To use this feature, add the following extension to your project:
 
-:add-extension-extensions: container-image-jib
+:add-extension-extensions: quarkus-container-image-jib
 include::{includes}/devtools/extension-add.adoc[]
 
 WARNING: In situations where all that is needed to build a container image and no push to a registry is necessary (essentially by having set `quarkus.container-image.build=true` and left `quarkus.container-image.push` unset - it defaults to `false`), then this extension creates a container image and registers
@@ -114,7 +114,7 @@ The extension `quarkus-container-image-docker` is using the Docker binary and th
 
 To use this feature, add the following extension to your project.
 
-:add-extension-extensions: container-image-docker
+:add-extension-extensions: quarkus-container-image-docker
 include::{includes}/devtools/extension-add.adoc[]
 
 The `quarkus-container-image-docker` extension is capable of https://docs.docker.com/buildx/working-with-buildx/#build-multi-platform-images/[creating multi-platform (or multi-arch)] images using https://docs.docker.com/engine/reference/commandline/buildx_build/[`docker buildx build`]. See the `quarkus.docker.buildx.*` configuration items in the <<#DockerOptions,Docker Options>> section below.
@@ -133,7 +133,7 @@ The extension `quarkus-container-image-podman` uses https://podman.io/[Podman] a
 
 To use this feature, add the following extension to your project.
 
-:add-extension-extensions: container-image-podman
+:add-extension-extensions: quarkus-container-image-podman
 include::{includes}/devtools/extension-add.adoc[]
 
 [TIP]
@@ -156,7 +156,7 @@ The benefit of this approach, is that it can be combined with OpenShift's `Deplo
 
 To use this feature, add the following extension to your project.
 
-:add-extension-extensions: container-image-openshift
+:add-extension-extensions: quarkus-container-image-openshift
 include::{includes}/devtools/extension-add.adoc[]
 
 OpenShift builds require creating a `BuildConfig` and two `ImageStream` resources, one for the builder image and one for the output image.
@@ -186,7 +186,7 @@ quarkus.buildpack.native-builder-image=<native builder image>
 
 To use this feature, add the following extension to your project.
 
-:add-extension-extensions: container-image-buildpack
+:add-extension-extensions: quarkus-container-image-buildpack
 include::{includes}/devtools/extension-add.adoc[]
 
 NOTE: When using the buildpack container image extension it is strongly advised to avoid adding `quarkus.container-image.build=true` in your properties configuration as it might trigger nesting builds within builds. It's preferable to pass it as an option to the build command instead.

_versions/main/guides/opentelemetry-metrics.adoc

@@ -362,9 +362,9 @@ IMPORTANT: Each unique combination of metric name and dimension produces a uniqu
 Using an unbounded set of dimensional data (many different values like a userId) can lead to a "cardinality explosion", an exponential increase in the creation of new time series.
 Avoid!
 
-OpenTelemetry provides many other types of Counters: `LongUpDownCounter`, `DoubleCounter`, `DoubleUpDownCounter` and also Observable, async counters like `ObservableLongCounter`, `ObservableDoubleCounter`, `ObservableLongUpDownCounter` and `ObservableDoubleUpDownCounter`.
+OpenTelemetry provides many other types of Counters: `LongUpDownCounter`, `DoubleCounter`, `UpDownCounter`,  `DoubleUpDownCounter` and also Observable, async counters like `ObservableLongCounter`, `ObservableDoubleCounter`, `ObservableLongUpDownCounter` and `ObservableDoubleUpDownCounter`.
 
-For more details please refer to the https://opentelemetry.io/docs/languages/java/instrumentation/#using-counters[OpenTelemetry Java documentation about Counters].
+For more details please refer to the https://opentelemetry.io/docs/languages/java/api/#counter[OpenTelemetry Java documentation about Counters].
 
 === Gauges
 Observable Gauges should be used to measure non-additive values.

_versions/main/guides/opentelemetry.adoc

@@ -398,7 +398,7 @@ You can also use the xref:logging-exporter-for-debugging[logging exporter] to ou
 
 Quarkus supports the OpenTelemetry Autoconfiguration for Traces.
 The configurations match what you can see at
-https://github.com/open-telemetry/opentelemetry-java/blob/main/sdk-extensions/autoconfigure/README.md[OpenTelemetry SDK Autoconfigure]
+https://opentelemetry.io/docs/languages/java/configuration/[OpenTelemetry SDK Autoconfigure]
 adding the usual `quarkus.*` prefix.
 
 Quarkus OpenTelemetry configuration properties now have the `quarkus.otel.*` prefix.

_versions/main/guides/rest.adoc

@@ -917,6 +917,15 @@ See <<execution-model,Execution Model documentation>> for more information.
 The link:{jdkapi}/java/util/concurrent/CompletionStage.html[`CompletionStage`] return
 type is also supported.
 
+==== Request cancellation
+
+Async endpoints that return `Uni` support request cancellation, which means that if the underlying HTTP connection is closed for whatever reason,
+the request pipeline defined by the returned `Uni` is also cancelled. This can be very useful in avoiding unnecessary work on the server
+when the client isn't going to use the response anyway.
+
+If instead of cancelling the pipeline, it should be completed regardless of the state of the HTTP connection, Quarkus REST provides the `org.jboss.resteasy.reactive.server.Cancellable` annotation
+which can be applied to REST classes or methods to control the cancellation behavior.
+
 === Streaming support
 
 If you want to stream your response element by element, you can make your endpoint method return a

_versions/main/guides/telemetry-micrometer-to-opentelemetry.adoc

@@ -134,73 +134,75 @@ quarkus.micrometer.binder.http-server.enabled=true
 
 The JVM and HTTP server metrics are collected by Micrometer.
 
-Next, are examples of the metrics collected by Micrometer and a comparison of what would be the `quarkus-micrometer-registry-prometheus` output vs the one on this bridge. A link to the equivalent OpenTelemetry Semantic Convention is also provided for reference and is not currently used in the bridge.
+Next, are examples of the metrics collected by Micrometer compared with what would be the `quarkus-micrometer-registry-prometheus` endpoint output (`/q/metrics`) vs the OTLP protocol output on this bridge.
 
+A link to the equivalent OpenTelemetry Semantic Convention is also provided for reference and is not currently used by the bridge.
+
+.Micrometer metrics output comparison. Prometheus registry vs. OpenTelemetry bridge
 |===
-|Micrometer Meter |Quarkus Micrometer Prometheus output | This bridge OpenTelemetry output name | Related OpenTelemetry Semantic Convention (not applied)
+|Micrometer Meter Java definition |Quarkus Micrometer Prometheus output (as seen at `/q/metrics/`) | This bridge OpenTelemetry output name (as seen in the OTLP output) | Related OpenTelemetry Semantic Convention (not applied)
 
-|Using the @Timed interceptor.
+|Using the xref:telemetry-micrometer#create-a-timer[@Timed] interceptor.
 |
-|method.timed (Histogram), method.timed.max (DoubleGauge)
+|method.timed (xref:opentelemetry-metrics#histograms[Histogram]), method.timed.max (xref:opentelemetry-metrics#gauges[DoubleGauge])
 |NA
 
-|Using the @Counted interceptor.
+|Using the xref:telemetry-micrometer#counters[@Counted] interceptor.
 |
-|method.counted (DoubleSum)
+|method.counted (https://opentelemetry.io/docs/specs/otel/metrics/sdk/#sum-aggregation[DoubleSum])
 |NA
 
-|`http.server.active.requests` (Gauge)
-|`http_server_active_requests` (Gauge)
-|`http.server.active.requests` (DoubleGauge)
-|https://opentelemetry.io/docs/specs/semconv/http/http-metrics/#metric-httpserveractive_requests[`http.server.active_requests`] (UpDownCounter)
+|`http.server.active.requests` (xref:telemetry-micrometer#gauges[Gauge])
+|`http_server_active_requests` (xref:telemetry-micrometer#gauges[Gauge])
+|`http.server.active.requests` (xref:opentelemetry-metrics#gauges[DoubleGauge])
+|https://opentelemetry.io/docs/specs/semconv/http/http-metrics/#metric-httpserveractive_requests[`http.server.active_requests`] (xref:opentelemetry-metrics#counters[UpDownCounter])
 
 |`http.server.requests` (Timer)
-|`http_server_requests_seconds_count`, `http_server_requests_seconds_sum`, `http_server_requests_seconds_max` (Gauge)
-|`http.server.requests` (Histogram), `http.server.requests.max` (DoubleGauge)
-|https://opentelemetry.io/docs/specs/semconv/http/http-metrics/#metric-httpserverrequestduration[`http.server.request.duration`] (Histogram)
-
-|`http.server.bytes.read` (DistributionSummary)
-|`http_server_bytes_read_count`, `http_server_bytes_read_sum` , `http_server_bytes_read_max` (Gauge)
-|`http.server.bytes.read` (Histogram), `http.server.bytes.read.max` (DoubleGauge)
-|https://opentelemetry.io/docs/specs/semconv/http/http-metrics/#metric-httpserverrequestbodysize[`http.server.request.body.size`] (Histogram)
-
-|`http.server.bytes.write` (DistributionSummary)
-|`http_server_bytes_write_count`, `http_server_bytes_write_sum` , `http_server_bytes_write_max` (Gauge)
-|`http.server.bytes.write` (Histogram), `http.server.bytes.write.max` (DoubleGauge)
-|https://opentelemetry.io/docs/specs/semconv/http/http-metrics/#metric-httpserverresponsebodysize[`http.server.response.body.size`] (Histogram)
-
-|`http.server.connections` (LongTaskTimer)
-|`http_server_connections_seconds_active_count`, `http_server_connections_seconds_duration_sum` `http_server_connections_seconds_max` (Gauge)
-|`http.server.connections.active` (LongSum), `http.server.connections.duration` (DoubleGauge)
+|`http_server_requests_seconds_count`, `http_server_requests_seconds_sum`, `http_server_requests_seconds_max` (xref:telemetry-micrometer#gauges[Gauge])
+|`http.server.requests` (xref:opentelemetry-metrics#histograms[Histogram]), `http.server.requests.max` (xref:opentelemetry-metrics#gauges[DoubleGauge])
+|https://opentelemetry.io/docs/specs/semconv/http/http-metrics/#metric-httpserverrequestduration[`http.server.request.duration`] (xref:opentelemetry-metrics#histograms[Histogram])
+
+|`http.server.bytes.read` (xref:telemetry-micrometer#create-a-distribution-summary[DistributionSummary])
+|`http_server_bytes_read_count`, `http_server_bytes_read_sum` , `http_server_bytes_read_max` (xref:telemetry-micrometer#gauges[Gauge])
+|`http.server.bytes.read` (xref:opentelemetry-metrics#histograms[Histogram]), `http.server.bytes.read.max` (xref:opentelemetry-metrics#gauges[DoubleGauge])
+|https://opentelemetry.io/docs/specs/semconv/http/http-metrics/#metric-httpserverrequestbodysize[`http.server.request.body.size`] (xref:opentelemetry-metrics#histograms[Histogram])
+
+|`http.server.bytes.write` (xref:telemetry-micrometer#create-a-distribution-summary[DistributionSummary])
+|`http_server_bytes_write_count`, `http_server_bytes_write_sum` , `http_server_bytes_write_max` (xref:telemetry-micrometer#gauges[Gauge])
+|`http.server.bytes.write` (xref:opentelemetry-metrics#histograms[Histogram]), `http.server.bytes.write.max` (xref:opentelemetry-metrics#gauges[DoubleGauge])
+|https://opentelemetry.io/docs/specs/semconv/http/http-metrics/#metric-httpserverresponsebodysize[`http.server.response.body.size`] (xref:opentelemetry-metrics#histograms[Histogram])
+
+|`http.server.connections` (https://docs.micrometer.io/micrometer/reference/concepts/long-task-timers.html[LongTaskTimer])
+|`http_server_connections_seconds_active_count`, `http_server_connections_seconds_duration_sum` `http_server_connections_seconds_max` (xref:telemetry-micrometer#gauges[Gauge])
+|`http.server.connections.active` (https://opentelemetry.io/docs/specs/otel/metrics/sdk/#sum-aggregation[LongSum]), `http.server.connections.duration` (xref:opentelemetry-metrics#gauges[DoubleGauge])
 | N/A
 
-|`jvm.threads.live` (Gauge)
-|`jvm_threads_live_threads` (Gauge)
-|`jvm.threads.live` (DoubleGauge)
-|https://opentelemetry.io/docs/specs/semconv/runtime/jvm-metrics/#metric-jvmthreadcount[`jvm.threads.live`] (UpDownCounter)
+|`jvm.threads.live` (xref:telemetry-micrometer#gauges[Gauge])
+|`jvm_threads_live_threads` (xref:telemetry-micrometer#gauges[Gauge])
+|`jvm.threads.live` (xref:opentelemetry-metrics#gauges[DoubleGauge])
+|https://opentelemetry.io/docs/specs/semconv/runtime/jvm-metrics/#metric-jvmthreadcount[`jvm.threads.live`] (xref:opentelemetry-metrics#counters[UpDownCounter])
 
-|`jvm.threads.started` (FunctionCounter)
-|`jvm_threads_started_threads_total` (Counter)
-|`jvm.threads.started` (DoubleSum)
-|https://opentelemetry.io/docs/specs/semconv/runtime/jvm-metrics/#metric-jvmthreadcount[`jvm.threads.live`] (UpDownCounter)
+|`jvm.threads.started` (https://docs.micrometer.io/micrometer/reference/concepts/counters.html#_function_tracking_counters[FunctionCounter])
+|`jvm_threads_started_threads_total` (xref:telemetry-micrometer#counters[Counter])
+|`jvm.threads.started` (https://opentelemetry.io/docs/specs/otel/metrics/sdk/#sum-aggregation[DoubleSum])
+|https://opentelemetry.io/docs/specs/semconv/runtime/jvm-metrics/#metric-jvmthreadcount[`jvm.threads.live`] (xref:opentelemetry-metrics#counters[UpDownCounter])
 
-|`jvm.threads.daemon` (Gauge)
-|`jvm_threads_daemon_threads` (Gauge)
-|`jvm.threads.daemon` (DoubleGauge)
-|https://opentelemetry.io/docs/specs/semconv/runtime/jvm-metrics/#metric-jvmthreadcount[`jvm.threads.live`] (UpDownCounter)
+|`jvm.threads.daemon` (xref:telemetry-micrometer#gauges[Gauge])
+|`jvm_threads_daemon_threads` (xref:telemetry-micrometer#gauges[Gauge])
+|`jvm.threads.daemon` (xref:opentelemetry-metrics#gauges[DoubleGauge])
+|https://opentelemetry.io/docs/specs/semconv/runtime/jvm-metrics/#metric-jvmthreadcount[`jvm.threads.live`] (xref:opentelemetry-metrics#counters[UpDownCounter])
 
-|`jvm.threads.peak` (Gauge)
-|`jvm_threads_peak_threads` (Gauge)
-|`jvm.threads.peak` (DoubleGauge)
+|`jvm.threads.peak` (xref:telemetry-micrometer#gauges[Gauge])
+|`jvm_threads_peak_threads` (xref:telemetry-micrometer#gauges[Gauge])
+|`jvm.threads.peak` (xref:opentelemetry-metrics#gauges[DoubleGauge])
 |N/A
 
-|`jvm.threads.states` (Gauge per state)
-|`jvm_threads_states_threads` (Gauge)
-|`jvm.threads.states` (DoubleGauge)
-|https://opentelemetry.io/docs/specs/semconv/runtime/jvm-metrics/#metric-jvmthreadcount[`jvm.threads.live`] (UpDownCounter)
+|`jvm.threads.states` (xref:telemetry-micrometer#gauges[Gauge] per state)
+|`jvm_threads_states_threads` (xref:telemetry-micrometer#gauges[Gauge])
+|`jvm.threads.states` (xref:opentelemetry-metrics#gauges[DoubleGauge])
+|https://opentelemetry.io/docs/specs/semconv/runtime/jvm-metrics/#metric-jvmthreadcount[`jvm.threads.live`] (xref:opentelemetry-metrics#counters[UpDownCounter])
 |===
 
-
 [NOTE]
 ====
 Some metrics might be missing from the output if they contain no data.