Sync documentation of main branch

Author: actions-user

_generated-doc/main/infra/quarkus-maven-plugin-goals.adoc

@@ -1245,6 +1245,15 @@ a| [[quarkus-maven-plugin-goal-dev-environmentVariables]] environmentVariables
 |`Map`
 |
 
+a| [[quarkus-maven-plugin-goal-dev-forceC2]] forceC2
+
+[.description]
+--
+This value is intended to be set to true when we want to require C2 compilation instead of preventing it from ever kicking in. Setting this will likely have a small negative effect on startup time and should only be done when it absolutely makes sense.
+--
+|`boolean`
+|`${forceC2}`
+
 a| [[quarkus-maven-plugin-goal-dev-jvmArgs]] jvmArgs
 
 [.description]
@@ -2905,6 +2914,15 @@ a| [[quarkus-maven-plugin-goal-remote-dev-environmentVariables]] environmentVari
 |`Map`
 |
 
+a| [[quarkus-maven-plugin-goal-remote-dev-forceC2]] forceC2
+
+[.description]
+--
+This value is intended to be set to true when we want to require C2 compilation instead of preventing it from ever kicking in. Setting this will likely have a small negative effect on startup time and should only be done when it absolutely makes sense.
+--
+|`boolean`
+|`${forceC2}`
+
 a| [[quarkus-maven-plugin-goal-remote-dev-jvmArgs]] jvmArgs
 
 [.description]
@@ -3380,6 +3398,15 @@ a| [[quarkus-maven-plugin-goal-test-environmentVariables]] environmentVariables
 |`Map`
 |
 
+a| [[quarkus-maven-plugin-goal-test-forceC2]] forceC2
+
+[.description]
+--
+This value is intended to be set to true when we want to require C2 compilation instead of preventing it from ever kicking in. Setting this will likely have a small negative effect on startup time and should only be done when it absolutely makes sense.
+--
+|`boolean`
+|`${forceC2}`
+
 a| [[quarkus-maven-plugin-goal-test-jvmArgs]] jvmArgs
 
 [.description]

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

@@ -579,7 +579,7 @@ Sample Dockerfile for building with Maven:
 ----
 ## Stage 1 : build with maven builder image with native capabilities
 FROM quay.io/quarkus/ubi-quarkus-mandrel-builder-image:{mandrel-flavor} AS build
-COPY --chown=quarkus:quarkus mvnw /code/mvnw
+COPY --chown=quarkus:quarkus --chmod=0755 mvnw /code/mvnw
 COPY --chown=quarkus:quarkus .mvn /code/.mvn
 COPY --chown=quarkus:quarkus pom.xml /code/
 USER quarkus

_versions/main/guides/datasource.adoc

@@ -259,26 +259,13 @@ For more information about configuring JDBC, see <<jdbc-url,JDBC URL format refe
 [[other-databases]]
 ===== Custom databases and drivers
 
-If you need to connect to a database for which Quarkus does not provide an extension with the JDBC driver, you can use a custom driver instead.
-For example, if you are using the OpenTracing JDBC driver in your project.
+If you need to connect to a database for which Quarkus does not provide an extension with the JDBC driver,
+you can use a custom driver instead. For example, if you are using the OpenTelemetry JDBC driver in your project.
 
 Without an extension, the driver will work correctly in any Quarkus app running in JVM mode.
 However, the driver is unlikely to work when compiling your application to a native executable.
 If you plan to make a native executable, use the existing JDBC Quarkus extensions, or contribute one for your driver.
 
-[WARNING]
-====
-OpenTracing has been deprecated in favor of OpenTelemetry.
-For tracing information, please check the related section about <<datasource-tracing>>, bellow.
-====
-
-.A custom driver definition example with the legacy OpenTracing driver:
-
-[source,properties]
-----
-quarkus.datasource.jdbc.driver=io.opentracing.contrib.jdbc.TracingDriver
-----
-
 .An example for defining access to a database with no built-in support in JVM mode:
 
 [source,properties]