Sync documentation of main branch

Author: actions-user

_versions/main/guides/datasource.adoc

@@ -678,9 +678,15 @@ You can override this by setting the `transactions` configuration property:
 * `quarkus.datasource.jdbc.transactions` for default unnamed datasource
 * `quarkus.datasource._<datasource-name>_.jdbc.transactions` for named datasource
 
-When a datasource is enabled for XA (by setting `quarkus.datasource[.optional name].jdbc.transactions` to `xa`) and the transaction recovery system is enabled (by setting the property `quarkus.transaction-manager.enable-recovery` to `true`), then the datasource is automatically registered for recovery.
-This is a safe default, but you can override this behaviour on a per-datasource basis by setting `quarkus.datasource.jdbc.enable-recovery` or `quarkus.datasource."datasource-name".jdbc.enable-recovery` to `false`.
-Use only for advanced use cases and if you know recovery will not be necessary; otherwise it can result in data loss, data unavailability, or both, because resources can become locked indefinitely.
+When a datasource is configured for XA transactions by setting `quarkus.datasource[.optional name].jdbc.transactions=xa` and the transaction recovery system is enabled by using `quarkus.transaction-manager.enable-recovery=true`, the datasource is automatically registered for recovery.
+This is the preferred and safe default.
+You can override this behavior for individual datasources by setting `quarkus.datasource.jdbc.enable-recovery=false` or `quarkus.datasource."datasource-name".jdbc.enable-recovery=false`.
+
+[IMPORTANT]
+====
+Change this setting only in advanced use cases and only if you are certain recovery is not required.
+Incorrect configuration can lead to data loss, data unavailability, or both, due to resources remaining locked indefinitely.
+====
 
 For more information, see the <<configuration-reference,Configuration reference>> section below.
 To facilitate the storage of transaction logs in a database by using JDBC, see the xref:transaction.adoc#jdbcstore[Configuring transaction logs to be stored in a datasource] section of the xref:transaction.adoc[Using transactions in Quarkus] guide.

_versions/main/guides/maven-tooling.adoc

@@ -326,6 +326,16 @@ With this configuration the logs will look like
 [DEBUG] Launching JVM with command line: /home/<username>/jdk/bin/java -Dquarkus-internal.serialized-app-model.path=/home/<username>/app/target/quarkus/bootstrap/dev-app-model.dat -javaagent:/home/<username>/.m2/repository/io/quarkus/quarkus-class-change-agent/{quarkus-version}/quarkus-class-change-agent-{quarkus-version}.jar -XX:TieredStopAtLevel=1 -agentlib:jdwp=transport=dt_socket,address=localhost:5005,server=y,suspend=n --enable-native-access=ALL-UNNAMED --add-modules=jdk.incubator.vector --enable-preview -Djava.util.logging.manager=org.jboss.logmanager.LogManager -jar /home/<username>/app/target/acme-app-dev.jar
 ----
 
+=== Hot Reload of the Maven process
+
+Sometimes you may want to reload the whole Maven process in order to pick up changes in the `pom.xml` file or to add/remove extensions. Quarkus automatically detects changes in the `pom.xml` file and restarts the Maven process if needed.
+
+You can also additionally set the `watchedFiles` parameter to the set of files that are also monitored for changes. This is particularly useful if you are developing a Quarkus extension or any other library that is being used as a dependency in your testing Quarkus application. You can set the `watchedFiles` to the installed Maven artifact in your local repository that will trigger automatic testing application reload when the extension or the library is installed:
+
+:dev-additional-parameters: -DwatchedFiles=~/.m2/repository/io/quarkus/quarkus-smallrye-health/999-SNAPSHOT/quarkus-smallrye-health-999-SNAPSHOT.jar
+include::{includes}/devtools/dev-parameters.adoc[]
+:!dev-additional-parameters:
+
 == Debugging
 
 In development mode, Quarkus starts by default with debug mode enabled, listening to port `5005` without suspending the JVM.

_versions/main/guides/platform.adoc

@@ -20,6 +20,7 @@ Each organization creating their Quarkus platform may establish their own criter
 
 == How does the Quarkus Platform help?
 When multiple extensions are used in the same project, a Quarkus platform BOM ensures:
+
 * version compatibility between the dependencies;
 * simplified dependency management;
 * easier upgrades.