Sync documentation of main branch

Author: actions-user

_data/versioned/main/index/quarkus.yaml

@@ -18,7 +18,7 @@ types:
   - title: Command Mode Applications
     filename: command-mode-reference.adoc
     summary: This reference guide explains how to develop command line applications with Quarkus.
-    categories: "core, command-line"
+    categories: "command-line, core"
     type: reference
     url: /guides/command-mode-reference
   - title: Configuration Reference Guide
@@ -230,7 +230,7 @@ types:
   - title: Building a Native Executable
     filename: building-native-image.adoc
     summary: Build native executables with GraalVM or Mandrel.
-    categories: "getting-started, native"
+    categories: "native, getting-started"
     type: tutorial
     url: /guides/building-native-image
   - title: Collect metrics using Micrometer
@@ -243,7 +243,7 @@ types:
   - title: Configure data sources in Quarkus
     filename: datasource.adoc
     summary: Use a unified configuration model to define datasources for Java Database Connectivity (JDBC) and Reactive drivers.
-    categories: "getting-started, data"
+    categories: "data, getting-started"
     id: datasources
     type: tutorial
     url: /guides/datasource
@@ -289,7 +289,7 @@ types:
   - title: Secure a Quarkus application with Basic authentication and Jakarta Persistence
     filename: security-basic-authentication-tutorial.adoc
     summary: Secure your Quarkus application endpoints by combining the built-in Quarkus Basic authentication with the Jakarta Persistence identity provider to enable role-based access control (RBAC).
-    categories: "getting-started, security"
+    categories: "security, getting-started"
     id: security-basic-authentication-tutorial
     type: tutorial
     url: /guides/security-basic-authentication-tutorial
@@ -345,7 +345,7 @@ types:
   - title: AppCDS
     filename: appcds.adoc
     summary: This reference guide explains how to enable AppCDS with Quarkus.
-    categories: "core, cloud"
+    categories: "cloud, core"
     type: guide
     url: /guides/appcds
   - title: Application Data Caching
@@ -539,7 +539,7 @@ types:
   - title: Dev Services for Databases
     filename: databases-dev-services.adoc
     summary: "When testing or running in dev mode Quarkus can provide you with a zero-config database out of the box, a feature we refer to as Dev Services."
-    categories: "tooling, data"
+    categories: "data, tooling"
     type: guide
     url: /guides/databases-dev-services
   - title: Dev Services for Elasticsearch
@@ -1022,7 +1022,7 @@ types:
   - title: Tips for writing native applications
     filename: writing-native-applications-tips.adoc
     summary: This guide is a collection of tips to help you solve the problems you encounter when compiling applications to native executable.
-    categories: "writing-extensions, core, native"
+    categories: "core, native, writing-extensions"
     type: guide
     url: /guides/writing-native-applications-tips
   - title: Update projects to the latest version of Quarkus
@@ -1158,7 +1158,7 @@ types:
   - title: Using SSL With Native Executables
     filename: native-and-ssl.adoc
     summary: "In this guide, we will discuss how you can get your native images to support SSL, as native images don't support it out of the box."
-    categories: "core, security, native"
+    categories: "security, core, native"
     type: guide
     url: /guides/native-and-ssl
   - title: Using Security with .properties File

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

@@ -1015,6 +1015,7 @@ a| `boolean shouldGenerateOne` :: +++<i>No Javadoc found</i>+++
 a| https://github.com/quarkusio/quarkus/blob/main/extensions/hibernate-orm/deployment/src/main/java/io/quarkus/hibernate/orm/deployment/JpaModelBuildItem.java[`io.quarkus.hibernate.orm.deployment.JpaModelBuildItem`, window="_blank"] :: +++Internal model to represent which objects are likely needing enhancement via HibernateEntityEnhancer.+++
 a| `Set allModelPackageNames` :: +++<i>No Javadoc found</i>+++
 `Set entityClassNames` :: +++<i>No Javadoc found</i>+++
+`Set managedClassNames` :: +++<i>No Javadoc found</i>+++
 `Set potentialCdiBeanClassNames` :: +++<i>No Javadoc found</i>+++
 `Set allModelClassNames` :: +++<i>No Javadoc found</i>+++
 `Map xmlMappingsByPU` :: +++<i>No Javadoc found</i>+++
@@ -1546,7 +1547,7 @@ a| https://github.com/quarkusio/quarkus/blob/main/extensions/panache/panache-hib
 a| `MetamodelInfo metamodelInfo` :: +++<i>No Javadoc found</i>+++
 
 a| https://github.com/quarkusio/quarkus/blob/main/extensions/panache/panache-hibernate-common/deployment/src/main/java/io/quarkus/panache/common/deployment/HibernateModelClassCandidatesForFieldAccessBuildItem.java[`io.quarkus.panache.common.deployment.HibernateModelClassCandidatesForFieldAccessBuildItem`, window="_blank"] :: +++<i>No Javadoc found</i>+++
-a| `Set allModelClassNames` :: +++<i>No Javadoc found</i>+++
+a| `Set managedClassNames` :: +++<i>No Javadoc found</i>+++
 
 |===
 == Qute

_versions/main/guides/_attributes.adoc

@@ -20,7 +20,7 @@
 :keycloak-docker-image: quay.io/keycloak/keycloak:21.0.2
 :jandex-version: 3.1.2
 :jandex-gradle-plugin.version: 1.0.0
-:kotlin-version: 1.8.21
+:kotlin-version: 1.8.22
 :grpc-version: 1.55.1
 :protoc-version: 3.22.0
 :gcf-invoker-version: 1.1.1

_versions/main/guides/deploying-to-openshift.adoc

@@ -117,14 +117,14 @@ So unless you've used the `quarkus.openshift.route.expose` config property to ex
 ----
 oc expose svc/greeting <1>
 oc get routes <2>
-curl http://<route>/greeting <3>
+curl http://<route>/hello <3>
 ----
 <1> Expose the service.
 <2> Get the list of exposed routes.
 <3> Access your application.
 
 [[control_application_config]]
-=== Configure the OpenShift Application Manually 
+=== Configure the OpenShift Application Manually
 
 If you need more control over the deployment configuration you can build the container image first and then configure the OpenShift application manually.
 
@@ -147,7 +147,7 @@ During the build you may find the `Caused by: javax.net.ssl.SSLHandshakeExceptio
 quarkus.kubernetes-client.trust-certs=true
 ----
 
-For more information, see link:https://quarkus.io/guides/deploying-to-kubernetes#client-connection-configuration[deploying to kubernetes].
+For more information, see link:https://quarkus.io/guides/deploying-to-kubernetes#client-connection-configuration[deploying to Kubernetes].
 ====
 
 Once the build is done we can create a new application from the relevant `ImageStream`.
@@ -159,7 +159,7 @@ oc new-app --name=greeting <project>/openshift-quickstart:1.0.0-SNAPSHOT <2>
 oc get svc
 oc expose svc/greeting <3>
 oc get routes <4>
-curl http://<route>/greeting <5>
+curl http://<route>/hello <5>
 ----
 <1> Lists the image streams created. The image stream of our application should be tagged as <project>/openshift-quickstart:1.0.0-SNAPSHOT.
 <2> Create a new application from the image source.
@@ -177,7 +177,7 @@ Out of the box the OpenShift extension is configured to use xref:container-image
 - xref:container-image.adoc#docker[container-image-docker]
 - xref:container-image.adoc#jib[container-image-jib]
 
-When a non-s2i container image extension is used, an `ImageStream` is created that is pointing to an external `dockerImageRepository`. The image is built and pushed to the registry and the `ImageStream` populates the tags that are available in the `dockerImageRepository`. 
+When a non-s2i container image extension is used, an `ImageStream` is created that is pointing to an external `dockerImageRepository`. The image is built and pushed to the registry and the `ImageStream` populates the tags that are available in the `dockerImageRepository`.
 
 To select which extension will be used for building the image:
 

_versions/main/guides/qute-reference.adoc

@@ -1538,20 +1538,36 @@ public class CustomSectionFactory implements SectionHelperFactory<CustomSectionF
     public List<String> getDefaultAliases() {
         return List.of("custom");
     }
+    
+    @Override
+    public ParametersInfo getParameters() {
+        // Param "foo" is required
+        return ParametersInfo.builder().addParameter("foo").build(); <3>
+    }
+    
+    @Override
+    public Scope initializeBlock(Scope outerScope, BlockInfo block) {
+        block.addExpression("foo", block.getParameter("foo"));
+        return outerScope;
+    }
+    
 
     @Override
     public CustomSectionHelper initialize(SectionInitContext context) {
-        if (context.getParameter("foo") == null) {
-            throw new IllegalStateException("Foo param not found"); <3>
-        }
         return new CustomSectionHelper();
     }
 
     class CustomSectionHelper implements SectionHelper {
+    
+        private final Expression foo;
+
+        public CustomSectionHelper(Expression foo) {
+            this.foo = foo;
+        }
 
         @Override
         public CompletionStage<ResultNode> resolve(SectionResolutionContext context) {
-            return CompletableFuture.completedStage(new SingleResultNode(service.getValue())); <4>
+            return context.evaluate(foo).thenApply(fooVal -> new SingleResultNode(service.getValueForFoo(fooVal))); <4>
         }
     }
 }

_versions/main/guides/security-oidc-code-flow-authentication-concept.adoc

@@ -529,7 +529,6 @@ An access token is only required if the endpoint needs to:
 
 In such cases, use the `quarkus.oidc.token-state-manager.strategy` property to configure the token state strategy as follows:
 
-[Attributes]
 |===
 |To... |Set the property to ...