Merge branch 'main' into patch-1

_data/1kcontributor-list.yaml

@@ -1879,6 +1879,10 @@ links:
     url: https://github.com/teruik
     name: Kenji Terui
     avatar: "https://avatars.githubusercontent.com/u/64245877?u=6e1b9fbcb36ec517fab201880666f4acc1a762c0&v=4"
+  - login: bogedal
+    url: https://github.com/bogedal
+    name: Kenneth Bøgedal
+    avatar: "https://avatars.githubusercontent.com/u/42640385?u=79bf0d6cca6dabe9f805aaff98e15541db325d80&v=4"
   - login: kdubois
     url: https://github.com/kdubois
     name: Kevin Dubois

_data/wg.yaml

@@ -1,5 +1,63 @@
 ---
 working-groups:
+    - title: "Roq :: Quarkus SSG"
+      board-url: "https://github.com/orgs/quarkiverse/projects/6"
+      short-description: Allow Static Site Generation with Quarkus.
+      readme: |
+        <p>New initiative to allow Static Site Generation with Quarkus.</p>
+        <p>Quarkus already provides most of the pieces to create great web applications (https://quarkus.io/guides/web).</p>
+        <p>I recently added https://github.com/quarkiverse/quarkus-roq. It will allow generating a static website out of any Quarkus application (it starts the app, fetch all the configured pages and assets, generate a static website and stop), it already works but it is still very alpha.</p>
+        <p>What's missing? we now need to incrementally add the toolkit to ease the process of creating static content through Quarkus:</p>
+        <ul>
+        <li>Static Data</li>
+        <li>Markdown/Asciidoc and frontmatter</li>
+        <li>SEO</li>
+        <li>Image processing</li>
+        <li>Easy to configure routing</li>
+        </ul>
+        <p>This will allow to develop the content using Quarkus dev-mode, and then generate for Github Pages or similar when it's ready.</p>
+        <p>Bonus, everything added will benefit any &quot;non-static&quot; Quarkus app and any Static Quarkus app could also become non static.</p>
+        <p>This effort is now tracked using a &quot;Working Group&quot; project: https://github.com/orgs/quarkiverse/projects/6</p>
+        <p>This is a great opportunity to participate in fun effort and be involved with the Quarkus community, if anyone is interested in being a part of this, please reach out to me 🚀</p>
+      status: on track
+      completed: false
+      last-activity: 2024-10-11
+      last-update: |
+        0.0.3 has been released, it is the MVP version and allowed to publish the Roq blog: https://quarkiverse.io/quarkus-roq/posts/2024-08-29-welcome-to-roq/
+        
+        From now on, we start adding features incrementally, documenting.
+        
+        The target is to have 1.0.0 the 1 October 2024.
+        
+        For 1.0 we need pagination, tags and SEO.
+    - title: "WebSocket Next"
+      board-url: "https://github.com/orgs/quarkusio/projects/26"
+      short-description: WebSocket-Next related tasks
+      readme: |
+        <p>The WebSocket Next <em>focus group</em> aims to improve our WebSocket experience.</p>
+        <p>Recently, we delivered a new approach to dealing with WebSocket (both for the server and client). This was the first step. There are still a few areas to improve, such as documentation, security, observability, and testability. The goal of this focus group is to track these efforts.</p>
+        <p>Point of contact: @mkouba (@<strong>Martin Kouba</strong>  on Zulip)</p>
+      status: on track
+      completed: false
+      last-activity: 2024-10-11
+      last-update: |
+        The last outstanding issue is OTel integration. @michalvavrik is working on a [pull request](https://github.com/quarkusio/quarkus/pull/41956). I will meet with Michal and Bruno in the coming weeks. The PR is quite massive and we need to review it carefully.
+    - title: "Test classloading"
+      board-url: "https://github.com/orgs/quarkusio/projects/30"
+      short-description: The goal of this working group is to rewrite Quarkus's test classloading, so that tests are run in the same classloader as the application under tests, and Quarkus extensions can do "Quarkus-y" manipulations of test classes.
+      readme: |
+        <p>At the moment, Quarkus tests are invoked using one classloader, and then executed in a different classloader. This mostly works well, but means some use cases don't work: extensions cannot manipulate test classes in the same way that they do normal application classes. For example, anything run via a JUnit @TestTemplate test case will see the un-transformed class.</p>
+        <p>It also means we have extra user-facing complexity, such as the QuarkusTest*Callbacks](https://quarkus.io/guides/getting-started-testing#enrichment-via-quarkustestcallback):</p>
+        <blockquote>
+        <p>While it is possible to use JUnit Jupiter callback interfaces like BeforeEachCallback, you might run into classloading issues because Quarkus has to run tests in a custom classloader which JUnit is not aware of.</p>
+        </blockquote>
+        <p>A final benefit is a reduction in the internal complexity of our code. Hopping between classloaders during test execution takes a lot of work, and adds a lot of code! It also is brittle in places. For example, because the hop between classloaders relies on serialization in some cases, it's becoming harder to do as the JVM tightens up security restrictions. We used to rely on xstream, but that stopped working in Java 17. In https://github.com/quarkusio/quarkus/pull/40601, @dmlloyd moved us to use the JBoss Serializer, which works better, but might still be affected by future restrictions on class access.</p>
+        <p>The goal of this working group is to allow test classes to fully participate in the 'quarkification' of classes. The mechanism for this is probably just to load the test classes with the classloader we intend to run them with, so that JUnit sees the 'correct' version of the class.</p>
+      status: on track
+      completed: false
+      last-activity: 2024-10-04
+      last-update: |
+        Progress continues. In the CI runs, the number of failing jobs is now 10. Most significantly, a bug which meant almost nothing worked on windows has now been fixed.
     - title: "Quarkus Config and IDEs"
       board-url: "https://github.com/orgs/quarkusio/projects/32"
       short-description: Let's define a format for the files containing the config model we will include in the jars for IDE consumption.
@@ -37,36 +95,6 @@ working-groups:
         
         With more features to be added in future pull requests.
         The pull request is on hold due to some concerns raised by @ia3andy. A meeting has been scheduled to discuss those concerns.
-    - title: "Roq :: Quarkus SSG"
-      board-url: "https://github.com/orgs/quarkiverse/projects/6"
-      short-description: Allow Static Site Generation with Quarkus.
-      readme: |
-        <p>New initiative to allow Static Site Generation with Quarkus.</p>
-        <p>Quarkus already provides most of the pieces to create great web applications (https://quarkus.io/guides/web).</p>
-        <p>I recently added https://github.com/quarkiverse/quarkus-roq. It will allow generating a static website out of any Quarkus application (it starts the app, fetch all the configured pages and assets, generate a static website and stop), it already works but it is still very alpha.</p>
-        <p>What's missing? we now need to incrementally add the toolkit to ease the process of creating static content through Quarkus:</p>
-        <ul>
-        <li>Static Data</li>
-        <li>Markdown/Asciidoc and frontmatter</li>
-        <li>SEO</li>
-        <li>Image processing</li>
-        <li>Easy to configure routing</li>
-        </ul>
-        <p>This will allow to develop the content using Quarkus dev-mode, and then generate for Github Pages or similar when it's ready.</p>
-        <p>Bonus, everything added will benefit any &quot;non-static&quot; Quarkus app and any Static Quarkus app could also become non static.</p>
-        <p>This effort is now tracked using a &quot;Working Group&quot; project: https://github.com/orgs/quarkiverse/projects/6</p>
-        <p>This is a great opportunity to participate in fun effort and be involved with the Quarkus community, if anyone is interested in being a part of this, please reach out to me 🚀</p>
-      status: on track
-      completed: false
-      last-activity: 2024-10-03
-      last-update: |
-        0.0.3 has been released, it is the MVP version and allowed to publish the Roq blog: https://quarkiverse.io/quarkus-roq/posts/2024-08-29-welcome-to-roq/
-        
-        From now on, we start adding features incrementally, documenting.
-        
-        The target is to have 1.0.0 the 1 October 2024.
-        
-        For 1.0 we need pagination, tags and SEO.
     - title: "Quarkus 3.15 LTS"
       board-url: "https://github.com/orgs/quarkusio/projects/28"
       short-description: This WG focuses on defining the issues we would like to have in the next-to-be LTS (Quarkus 3.14/3.15)
@@ -132,33 +160,3 @@ working-groups:
       last-activity: 2024-09-29
       last-update: |
         Just got started.
-    - title: "Test classloading"
-      board-url: "https://github.com/orgs/quarkusio/projects/30"
-      short-description: The goal of this working group is to rewrite Quarkus's test classloading, so that tests are run in the same classloader as the application under tests, and Quarkus extensions can do "Quarkus-y" manipulations of test classes.
-      readme: |
-        <p>At the moment, Quarkus tests are invoked using one classloader, and then executed in a different classloader. This mostly works well, but means some use cases don't work: extensions cannot manipulate test classes in the same way that they do normal application classes. For example, anything run via a JUnit @TestTemplate test case will see the un-transformed class.</p>
-        <p>It also means we have extra user-facing complexity, such as the QuarkusTest*Callbacks](https://quarkus.io/guides/getting-started-testing#enrichment-via-quarkustestcallback):</p>
-        <blockquote>
-        <p>While it is possible to use JUnit Jupiter callback interfaces like BeforeEachCallback, you might run into classloading issues because Quarkus has to run tests in a custom classloader which JUnit is not aware of.</p>
-        </blockquote>
-        <p>A final benefit is a reduction in the internal complexity of our code. Hopping between classloaders during test execution takes a lot of work, and adds a lot of code! It also is brittle in places. For example, because the hop between classloaders relies on serialization in some cases, it's becoming harder to do as the JVM tightens up security restrictions. We used to rely on xstream, but that stopped working in Java 17. In https://github.com/quarkusio/quarkus/pull/40601, @dmlloyd moved us to use the JBoss Serializer, which works better, but might still be affected by future restrictions on class access.</p>
-        <p>The goal of this working group is to allow test classes to fully participate in the 'quarkification' of classes. The mechanism for this is probably just to load the test classes with the classloader we intend to run them with, so that JUnit sees the 'correct' version of the class.</p>
-      status: on track
-      completed: false
-      last-activity: 2024-09-24
-      last-update: |
-        Since we don't have a target date, and progress is being made, I can declare this on track, with only a slightly murky conscience. 
-        
-        This is a big change, and one which doesn't lend itself well to dividing into smaller chunks. I'm keeping a spreadsheet of build results. In the CI runs, the number of failing jobs was 31 at the last update, and it is now 25. A number of suites, such as `integration-tests/devtools` were failing, and are now passing.
-    - title: "WebSocket Next"
-      board-url: "https://github.com/orgs/quarkusio/projects/26"
-      short-description: WebSocket-Next related tasks
-      readme: |
-        <p>The WebSocket Next <em>focus group</em> aims to improve our WebSocket experience.</p>
-        <p>Recently, we delivered a new approach to dealing with WebSocket (both for the server and client). This was the first step. There are still a few areas to improve, such as documentation, security, observability, and testability. The goal of this focus group is to track these efforts.</p>
-        <p>Point of contact: @mkouba (@<strong>Martin Kouba</strong>  on Zulip)</p>
-      status: on track
-      completed: false
-      last-activity: 2024-09-05
-      last-update: |
-        The last outstanding issue is OTel integration. @michalvavrik is working on a [pull request](https://github.com/quarkusio/quarkus/pull/41956). I will meet with Michal and Bruno in the coming weeks. The PR is quite massive and we need to review it carefully.

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

@@ -19455,6 +19455,29 @@ endif::add-copy-button-to-env-var[]
 |string
 |
 
+a| [[quarkus-hibernate-orm_quarkus-hibernate-orm-database-version-check-enabled]] [.property-path]##link:#quarkus-hibernate-orm_quarkus-hibernate-orm-database-version-check-enabled[`quarkus.hibernate-orm.database.version-check.enabled`]##
+
+`quarkus.hibernate-orm."persistence-unit-name".database.version-check.enabled`
+
+[.description]
+--
+Whether Hibernate ORM should check on startup
+that the version of the database matches the version configured on the dialect
+(either the default version, or the one set through `quarkus.datasource.db-version`).
+
+This should be set to `false` if the database is not available on startup.
+
+
+ifdef::add-copy-button-to-env-var[]
+Environment variable: env_var_with_copy_button:+++QUARKUS_HIBERNATE_ORM_DATABASE_VERSION_CHECK_ENABLED+++[]
+endif::add-copy-button-to-env-var[]
+ifndef::add-copy-button-to-env-var[]
+Environment variable: `+++QUARKUS_HIBERNATE_ORM_DATABASE_VERSION_CHECK_ENABLED+++`
+endif::add-copy-button-to-env-var[]
+--
+|boolean
+|``true` if the dialect was set automatically by Quarkus, `false` if it was set explicitly`
+
 
 h|[[quarkus-hibernate-orm_section_quarkus-hibernate-orm-dialect]] [.section-name.section-level0]##link:#quarkus-hibernate-orm_section_quarkus-hibernate-orm-dialect[Dialect related configuration]##
 h|Type
@@ -64654,6 +64677,48 @@ endif::add-copy-button-to-env-var[]
 a|`discover`, `static`
 |`discover`
 
+a| [[quarkus-redis-client_quarkus-redis-client-name]] [.property-path]##link:#quarkus-redis-client_quarkus-redis-client-name[`quarkus.redis.client-name`]##
+
+[.description]
+--
+The client name used to identify the connection.
+
+If the `RedisClientConfig++#++configureClientName()` is enabled, and this property is not set it will attempt to extract the value from the `RedisClientName++#++value()` annotation.
+
+If the `RedisClientConfig++#++configureClientName()` is enabled, both this property and the `RedisClientName++#++value()` must adhere to the pattern '++[++a-zA-Z0-9++\\++-_.~++]*++'; if not, this may result in an incorrect client name after URI encoding.
+
+
+ifdef::add-copy-button-to-env-var[]
+Environment variable: env_var_with_copy_button:+++QUARKUS_REDIS_CLIENT_NAME+++[]
+endif::add-copy-button-to-env-var[]
+ifndef::add-copy-button-to-env-var[]
+Environment variable: `+++QUARKUS_REDIS_CLIENT_NAME+++`
+endif::add-copy-button-to-env-var[]
+--
+|string
+|
+
+a| [[quarkus-redis-client_quarkus-redis-configure-client-name]] [.property-path]##link:#quarkus-redis-client_quarkus-redis-configure-client-name[`quarkus.redis.configure-client-name`]##
+
+[.description]
+--
+Whether it should set the client name while connecting with Redis.
+
+This is necessary because Redis only accepts `client=my-client-name` query parameter in version 6{plus}.
+
+This property can be used with `RedisClientConfig++#++clientName()` configuration.
+
+
+ifdef::add-copy-button-to-env-var[]
+Environment variable: env_var_with_copy_button:+++QUARKUS_REDIS_CONFIGURE_CLIENT_NAME+++[]
+endif::add-copy-button-to-env-var[]
+ifndef::add-copy-button-to-env-var[]
+Environment variable: `+++QUARKUS_REDIS_CONFIGURE_CLIENT_NAME+++`
+endif::add-copy-button-to-env-var[]
+--
+|boolean
+|`false`
+
 a| [[quarkus-redis-client_quarkus-redis-tls-configuration-name]] [.property-path]##link:#quarkus-redis-client_quarkus-redis-tls-configuration-name[`quarkus.redis.tls-configuration-name`]##
 
 [.description]
@@ -65109,6 +65174,48 @@ endif::add-copy-button-to-env-var[]
 a|`discover`, `static`
 |`discover`
 
+a| [[quarkus-redis-client_quarkus-redis-redis-client-name-client-name]] [.property-path]##link:#quarkus-redis-client_quarkus-redis-redis-client-name-client-name[`quarkus.redis."redis-client-name".client-name`]##
+
+[.description]
+--
+The client name used to identify the connection.
+
+If the `RedisClientConfig++#++configureClientName()` is enabled, and this property is not set it will attempt to extract the value from the `RedisClientName++#++value()` annotation.
+
+If the `RedisClientConfig++#++configureClientName()` is enabled, both this property and the `RedisClientName++#++value()` must adhere to the pattern '++[++a-zA-Z0-9++\\++-_.~++]*++'; if not, this may result in an incorrect client name after URI encoding.
+
+
+ifdef::add-copy-button-to-env-var[]
+Environment variable: env_var_with_copy_button:+++QUARKUS_REDIS__REDIS_CLIENT_NAME__CLIENT_NAME+++[]
+endif::add-copy-button-to-env-var[]
+ifndef::add-copy-button-to-env-var[]
+Environment variable: `+++QUARKUS_REDIS__REDIS_CLIENT_NAME__CLIENT_NAME+++`
+endif::add-copy-button-to-env-var[]
+--
+|string
+|
+
+a| [[quarkus-redis-client_quarkus-redis-redis-client-name-configure-client-name]] [.property-path]##link:#quarkus-redis-client_quarkus-redis-redis-client-name-configure-client-name[`quarkus.redis."redis-client-name".configure-client-name`]##
+
+[.description]
+--
+Whether it should set the client name while connecting with Redis.
+
+This is necessary because Redis only accepts `client=my-client-name` query parameter in version 6{plus}.
+
+This property can be used with `RedisClientConfig++#++clientName()` configuration.
+
+
+ifdef::add-copy-button-to-env-var[]
+Environment variable: env_var_with_copy_button:+++QUARKUS_REDIS__REDIS_CLIENT_NAME__CONFIGURE_CLIENT_NAME+++[]
+endif::add-copy-button-to-env-var[]
+ifndef::add-copy-button-to-env-var[]
+Environment variable: `+++QUARKUS_REDIS__REDIS_CLIENT_NAME__CONFIGURE_CLIENT_NAME+++`
+endif::add-copy-button-to-env-var[]
+--
+|boolean
+|`false`
+
 a| [[quarkus-redis-client_quarkus-redis-redis-client-name-tls-configuration-name]] [.property-path]##link:#quarkus-redis-client_quarkus-redis-redis-client-name-tls-configuration-name[`quarkus.redis."redis-client-name".tls-configuration-name`]##
 
 [.description]
@@ -67263,6 +67370,25 @@ h|[.extension-name]##REST Client##
 h|Type
 h|Default
 
+a|icon:lock[title=Fixed at build time] [[quarkus-rest-client_quarkus-rest-client-disable-smart-produces]] [.property-path]##link:#quarkus-rest-client_quarkus-rest-client-disable-smart-produces[`quarkus.rest-client.disable-smart-produces`]##
+
+[.description]
+--
+By default, RESTEasy Reactive uses text/plain content type for String values and application/json for everything else.
+
+MicroProfile Rest Client spec requires the implementations to always default to application/json. This build item disables the "smart" behavior of RESTEasy Reactive to comply to the spec
+
+
+ifdef::add-copy-button-to-env-var[]
+Environment variable: env_var_with_copy_button:+++QUARKUS_REST_CLIENT_DISABLE_SMART_PRODUCES+++[]
+endif::add-copy-button-to-env-var[]
+ifndef::add-copy-button-to-env-var[]
+Environment variable: `+++QUARKUS_REST_CLIENT_DISABLE_SMART_PRODUCES+++`
+endif::add-copy-button-to-env-var[]
+--
+|boolean
+|`false`
+
 a|icon:lock[title=Fixed at build time] [[quarkus-rest-client_quarkus-rest-client-provider-autodiscovery]] [.property-path]##link:#quarkus-rest-client_quarkus-rest-client-provider-autodiscovery[`quarkus.rest-client.provider-autodiscovery`]##
 
 [.description]