Sync documentation of main branch

Author: actions-user

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

@@ -10553,27 +10553,6 @@ endif::add-copy-button-to-env-var[]
 |boolean
 |`false`
 
-a|icon:lock[title=Fixed at build time] [[quarkus-core_quarkus-test-native-image-profile]] [.property-path]##link:#quarkus-core_quarkus-test-native-image-profile[`quarkus.test.native-image-profile`]##
-ifdef::add-copy-button-to-config-props[]
-config_property_copy_button:+++quarkus.test.native-image-profile+++[]
-endif::add-copy-button-to-config-props[]
-
-
-[.description]
---
-The profile to use when testing the native image
-
-
-ifdef::add-copy-button-to-env-var[]
-Environment variable: env_var_with_copy_button:+++QUARKUS_TEST_NATIVE_IMAGE_PROFILE+++[]
-endif::add-copy-button-to-env-var[]
-ifndef::add-copy-button-to-env-var[]
-Environment variable: `+++QUARKUS_TEST_NATIVE_IMAGE_PROFILE+++`
-endif::add-copy-button-to-env-var[]
---
-|string
-|`prod`
-
 a|icon:lock[title=Fixed at build time] [[quarkus-core_quarkus-test-integration-test-profile]] [.property-path]##link:#quarkus-core_quarkus-test-integration-test-profile[`quarkus.test.integration-test-profile`]##
 ifdef::add-copy-button-to-config-props[]
 config_property_copy_button:+++quarkus.test.integration-test-profile+++[]
@@ -10593,7 +10572,7 @@ Environment variable: `+++QUARKUS_TEST_INTEGRATION_TEST_PROFILE+++`
 endif::add-copy-button-to-env-var[]
 --
 |string
-|`prod`
+|`${quarkus.profile:prod}`
 
 a|icon:lock[title=Fixed at build time] [[quarkus-core_quarkus-test-profile]] [.property-path]##link:#quarkus-core_quarkus-test-profile[`quarkus.test.profile`]##
 ifdef::add-copy-button-to-config-props[]

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

@@ -237,27 +237,6 @@ endif::add-copy-button-to-env-var[]
 |boolean
 |`false`
 
-a|icon:lock[title=Fixed at build time] [[quarkus-core_quarkus-test-native-image-profile]] [.property-path]##link:#quarkus-core_quarkus-test-native-image-profile[`quarkus.test.native-image-profile`]##
-ifdef::add-copy-button-to-config-props[]
-config_property_copy_button:+++quarkus.test.native-image-profile+++[]
-endif::add-copy-button-to-config-props[]
-
-
-[.description]
---
-The profile to use when testing the native image
-
-
-ifdef::add-copy-button-to-env-var[]
-Environment variable: env_var_with_copy_button:+++QUARKUS_TEST_NATIVE_IMAGE_PROFILE+++[]
-endif::add-copy-button-to-env-var[]
-ifndef::add-copy-button-to-env-var[]
-Environment variable: `+++QUARKUS_TEST_NATIVE_IMAGE_PROFILE+++`
-endif::add-copy-button-to-env-var[]
---
-|string
-|`prod`
-
 a|icon:lock[title=Fixed at build time] [[quarkus-core_quarkus-test-integration-test-profile]] [.property-path]##link:#quarkus-core_quarkus-test-integration-test-profile[`quarkus.test.integration-test-profile`]##
 ifdef::add-copy-button-to-config-props[]
 config_property_copy_button:+++quarkus.test.integration-test-profile+++[]
@@ -277,7 +256,7 @@ Environment variable: `+++QUARKUS_TEST_INTEGRATION_TEST_PROFILE+++`
 endif::add-copy-button-to-env-var[]
 --
 |string
-|`prod`
+|`${quarkus.profile:prod}`
 
 a|icon:lock[title=Fixed at build time] [[quarkus-core_quarkus-test-profile]] [.property-path]##link:#quarkus-core_quarkus-test-profile[`quarkus.test.profile`]##
 ifdef::add-copy-button-to-config-props[]

_versions/main/guides/_attributes.adoc

@@ -19,7 +19,7 @@
 :logstash-image: docker.io/elastic/logstash:8.15.0
 :kibana-image: docker.io/elastic/kibana:8.15.0
 :keycloak-docker-image: quay.io/keycloak/keycloak:26.2.0
-:jandex-version: 3.3.0
+:jandex-version: 3.3.1
 :jandex-gradle-plugin-version: 1.0.0
 :kotlin-version: 2.1.20
 :grpc-version: 1.69.1

_versions/main/guides/qute-reference.adoc

@@ -2061,9 +2061,13 @@ public class ItemResource {
 [[type_safe_fragments]]
 ==== Type-safe Fragments
 
-You can also define a type-safe <<fragments,fragment>> in your Java code.
-A _native static_ method with the name that contains a dollar sign `$` denotes a method that represents a fragment of a type-safe template.
-The name of the fragment is derived from the annotated method name.
+You can also define a type-safe <<fragments,fragment>> of a type-safe template in your Java code.
+There are two ways to define a type-safe fragment:
+
+1. A _native static_ method annotated with `@CheckedTemplate`, with a name that contains a dollar sign `$`.
+2. A Java record that implements `io.quarkus.qute.TemplateInstance` and its name contains a dollar sign `$`.
+
+The name of the fragment is derived from the annotated member name.
 The part before the last occurrence of a dollar sign `$` is the method name of the related type-safe template.
 The part after the last occurrence of a dollar sign is the fragment identifier.
 The strategy defined by the relevant `CheckedTemplate#defaultName()` is honored when constructing the defaulted names.
@@ -2082,6 +2086,9 @@ class Templates {
 
   // defines a fragment of Templates#items() with identifier "item"
   static native TemplateInstance items$item(Item item); <1>
+  
+  // type-safe fragment as a Java record - functionally equivalent to the items$item() method above
+  record items$item(Item item) implements TemplateInstance {}
 }
 ----
 <1> Quarkus validates at build time that each template that corresponds to the `Templates#items()` contains a fragment with identifier `item`. Moreover, the parameters of the fragment method are validated too. In general, all type-safe expressions that are found in the fragment and that reference some data from the original/outer template require a specific parameter to be present.