chore(docs): modify documentation following version bump for quarkus …

…3.15

Related to camunda/camunda-bpm-platform#4580

content/update/minor/721-to-722/_index.md

@@ -268,12 +268,12 @@ This behaviour can be disabled by setting the `skipIsolationLevelCheck` flag to
 
 # Quarkus 3.14 Extension Update
 
-The Camunda Quarkus Extension has been updated to use Quarkus `3.14`. This version brings its own features and changes.
+The Camunda Quarkus Extension has been updated to use Quarkus `3.15`. This version brings its own features and changes.
 For a complete list, see the [Quarkus 3.14.2 Release](https://quarkus.io/blog/quarkus-3-14-2-released) blog post.
 
 ## Breaking Changes
 
-`Quarkus 3.14` extensions introduce **breaking changes** in the way the Quarkus runtime treats configuration.
+`Quarkus 3.15` extensions introduce **breaking changes** in the way the Quarkus runtime treats configuration.
 
 A config migration is required to remain consistent with the new behavior of the framework (see [property examples](#property-examples) below).
 
@@ -286,7 +286,9 @@ This requires using the new namespace `generic-config`.
 
 - `quarkus.camunda.enforce-history-time-to-live` **becomes** `quarkus.camunda.generic-config.enforce-history-time-to-live`
 
-- `quarkus.camunda.job-executor.thread-pool.max-pool-size` **becomes** `quarkus.camunda.job-executor.generic-config.thread-pool.max-pool-size`
+- `quarkus.camunda.job-executor.max-wait` **becomes** `quarkus.camunda.job-executor.generic-config.max-wait`
+
+Non-generic properties, such as `quarkus.camunda.job-executor.thread-pool.max-pool-size` and `quarkus.camunda.job-executor.thread-pool.queue-size`, remain unchanged.
 
 For a detailed guide on the new Quarkus properties, visit the updated [Quarkus Configuration]({{< ref "/user-guide/quarkus-integration/configuration.md" >}}) page.
 

content/user-guide/quarkus-integration/configuration.md

@@ -177,7 +177,7 @@ the Quarkus-specific properties in the following table:
   <tr><td colspan="4"><b>Job Executor</b></td></tr>
 
   <tr>
-    <td rowspan="2"><code>quarkus.camunda.job-executor.generic-config.thread-pool</code></td>
+    <td rowspan="2"><code>quarkus.camunda.job-executor.thread-pool</code></td>
     <td><code>.max-pool-size</code></td>
     <td>Sets the maximum number of threads that can be present in the thread pool.</td>
     <td><code>10</code></td>
@@ -223,8 +223,8 @@ quarkus.camunda.generic-config.dmn-enabled=false
 quarkus.camunda.generic-config.history=none
 
 # job executor configuration
-quarkus.camunda.job-executor.generic-config.thread-pool.max-pool-size=12
-quarkus.camunda.job-executor.generic-config.thread-pool.queue-size=5
+quarkus.camunda.job-executor.thread-pool.max-pool-size=12
+quarkus.camunda.job-executor.thread-pool.queue-size=5
 quarkus.camunda.job-executor.generic-config.max-jobs-per-acquisition=5
 quarkus.camunda.job-executor.generic-config.lock-time-in-millis=500000
 quarkus.camunda.job-executor.generic-config.wait-time-in-millis=7000

content/user-guide/quarkus-integration/version-compatibility.md

@@ -39,6 +39,10 @@ Only these default combinations are recommended (and supported) by Camunda.
     <td>7.21.x</td>
     <td>3.8.x</td>
   </tr>
+  <tr>
+    <td>7.22.x</td>
+    <td>3.15.x</td>
+  </tr>
 </table>
 
 In case a certain Quarkus version has a bug, you can override the existing Quarkus version by adding the following