Sync web site with Quarkus documentation

quarkusbot · quarkusbot · commit b21f15c9a27a · 2025-03-18T10:52:14.000Z
diff --git a/_generated-doc/3.15/infra/quarkus-all-build-items.adoc b/_generated-doc/3.15/infra/quarkus-all-build-items.adoc
@@ -8812,6 +8812,10 @@ _No Javadoc found_
 
 _No Javadoc found_
 
+`java.lang.String absolutePath` 
+
+_No Javadoc found_
+
 `io.quarkus.vertx.http.deployment.devmode.ConfiguredPathInfo configuredPathInfo` 
 
 _No Javadoc found_
@@ -9067,7 +9071,7 @@ a| https://github.com/quarkusio/quarkus/blob/main/extensions/vertx-http/deployme
 [.description]
 --
 _No Javadoc found_
--- a|`java.util.List<String> endpoints` 
+-- a|`java.util.Set<String> endpoints` 
 
 _No Javadoc found_
 
diff --git a/_versions/3.15/guides/_attributes.adoc b/_versions/3.15/guides/_attributes.adoc
@@ -1,7 +1,7 @@
 // Common attributes.
 // --> No blank lines (it ends the document header)
 :project-name: Quarkus
-:quarkus-version: 3.15.3.1
+:quarkus-version: 3.15.4
 :quarkus-platform-groupid: io.quarkus.platform
 // .
 :maven-version: 3.9.8
diff --git a/_versions/3.15/guides/building-native-image.adoc b/_versions/3.15/guides/building-native-image.adoc
@@ -495,10 +495,15 @@ The project generation has provided a `Dockerfile.native-micro` in the `src/main
 ----
 FROM quay.io/quarkus/quarkus-micro-image:2.0
 WORKDIR /work/
-COPY target/*-runner /work/application
-RUN chmod 775 /work
+RUN chown 1001 /work \
+    && chmod "g+rwX" /work \
+    && chown 1001:root /work
+COPY --chown=1001:root --chmod=755 target/*-runner /work/application
+
 EXPOSE 8080
-CMD ["./application", "-Dquarkus.http.host=0.0.0.0"]
+USER 1001
+
+ENTRYPOINT ["./application", "-Dquarkus.http.host=0.0.0.0"]
 ----
 
 [NOTE]
@@ -543,7 +548,7 @@ WORKDIR /work/
 RUN chown 1001 /work \
     && chmod "g+rwX" /work \
     && chown 1001:root /work
-COPY --chown=1001:root target/*-runner /work/application
+COPY --chown=1001:root --chmod=0755 target/*-runner /work/application
 
 EXPOSE 8080
 USER 1001
diff --git a/_versions/3.15/guides/databases-dev-services.adoc b/_versions/3.15/guides/databases-dev-services.adoc
@@ -202,9 +202,9 @@ Login credentials are the same for most databases, except when the database requ
 |Database |Username |Password |Database name
 
 |PostgreSQL, MariaDB, MySQL, IBM Db2, H2
-|`quarkus` for the default datasource or name of the datasource
 |`quarkus`
 |`quarkus`
+|`quarkus` for the default datasource or name of the datasource
 
 |Microsoft SQL Server
 |`SA`
diff --git a/_versions/3.15/guides/native-reference.adoc b/_versions/3.15/guides/native-reference.adoc
@@ -2293,14 +2293,29 @@ One can see which Mandrel version was used to generate a binary by inspecting th
 
 [source,bash]
 ----
-$ strings target/debugging-native-1.0.0-SNAPSHOT-runner | grep GraalVM
-com.oracle.svm.core.VM=GraalVM 22.0.0.2-Final Java 11 Mandrel Distribution
+$ strings target/debugging-native-1.0.0-SNAPSHOT-runner | \
+  grep -e 'com.oracle.svm.core.VM=' -e 'com.oracle.svm.core.VM.Java.Version' -F
+com.oracle.svm.core.VM.Java.Version=21.0.5
+com.oracle.svm.core.VM=Mandrel-23.1.5.0-Final
 ----
 
 === How do I enable GC logging in native executables?
 
 See <<gc-logging,Native Memory Management GC Logging section>> for details.
 
+=== Can I get a thread dump of a native executable?
+
+Yes, Quarkus sets up a signal handler for the `SIGQUIT` signal (or `SIGBREAK` on windows) that will result in a thread
+dump being printed when receiving the `SIGQUIT/SIGBREAK` signal.
+You may use `kill -SIGQUIT <pid>` to trigger a thread dump.
+
+[NOTE]
+====
+Quarkus uses its own signal handler, to use GraalVM's default signal handler instead you will need to:
+1. Add `-H:+DumpThreadStacksOnSignal` to `quarkus.native.additional-build-args` and rebuild the application.
+2. Set the environment variable `DISABLE_SIGNAL_HANDLERS` before running the app.
+====
+
 [[heap-dumps]]
 === Can I get a heap dump of a native executable? e.g. if it runs out of memory
 
diff --git a/_versions/3.15/guides/quarkus-runtime-base-image.adoc b/_versions/3.15/guides/quarkus-runtime-base-image.adoc
@@ -24,8 +24,7 @@ In your `Dockerfile`, just use:
 ----
 FROM quay.io/quarkus/quarkus-micro-image:2.0
 WORKDIR /work/
-COPY target/*-runner /work/application
-RUN chmod 775 /work
+COPY --chmod=0755 target/*-runner /work/application
 EXPOSE 8080
 CMD ["./application", "-Dquarkus.http.host=0.0.0.0"]
 ----
@@ -51,8 +50,7 @@ COPY --from=BUILD \
    /lib64/
 
 WORKDIR /work/
-COPY target/*-runner /work/application
-RUN chmod 775 /work
+COPY --chmod=0755 target/*-runner /work/application
 EXPOSE 8080
 CMD ["./application", "-Dquarkus.http.host=0.0.0.0"]
 ----
@@ -95,8 +93,7 @@ COPY --from=BUILD \
      /etc/fonts /etc/fonts
 
 WORKDIR /work/
-COPY target/*-runner /work/application
-RUN chmod 775 /work
+COPY --chmod=0755 target/*-runner /work/application
 EXPOSE 8080
 CMD ["./application", "-Dquarkus.http.host=0.0.0.0"]
 ----
@@ -117,7 +114,7 @@ WORKDIR /work/
 RUN chown 1001 /work \
     && chmod "g+rwX" /work \
     && chown 1001:root /work
-COPY --chown=1001:root target/*-runner /work/application
+COPY --chown=1001:root --chmod=0755 target/*-runner /work/application
 
 EXPOSE 8080
 USER 1001
diff --git a/_versions/3.15/guides/qute-reference.adoc b/_versions/3.15/guides/qute-reference.adoc
@@ -2955,10 +2955,9 @@ If there is a message bundle method that accepts a single parameter of an enum t
 @Message <1>
 String methodName(MyEnum enum);
 ----
-<1> The value is intentionally not provided. There's also no key for the method in a localized file.
-
-Then it receives a generated template:
+<1> The value is intentionally not provided. There's also no key/value pair for this method in a localized file.
 
+Then it receives a generated template like:
 [source,html]
 ----
 {#when enumParamName}
@@ -2967,15 +2966,27 @@ Then it receives a generated template:
 {/when}
 ----
 
-Furthermore, a special message method is generated for each enum constant. Finally, each localized file must contain keys and values for all constant message keys:
+Furthermore, a special message method is generated for each enum constant. 
+Finally, each localized file must contain keys and values for all enum constants:
 
 [source,poperties]
 ----
 methodName_CONSTANT1=Value 1
 methodName_CONSTANT2=Value 2
 ----
 
-In a template, an enum constant can be localized with a message bundle method like `{msg:methodName(enumConstant)}`.
+// We need to escape the first underscore 
+// See https://docs.asciidoctor.org/asciidoc/latest/subs/prevent/
+[IMPORTANT] 
+.Message keys for enum constants
+==== 
+By default, the message key consists of the method name followed by the `\_` separator and the constant name.
+If any constant name of a particular enum contains the `_` or the `$` character then the `\_$` separator must be used for all message keys for this enum instead.
+For example, `methodName_$CONSTANT_1=Value 1` or `methodName_$CONSTANT$1=Value 1`.
+A constant of a localized enum may not contain the `_$` separator.
+====
+
+In a template, the localized message for an enum constant can be obtained with a message bundle method like `{msg:methodName(enumConstant)}`.
 
 TIP: There is also <<convenient-annotation-for-enums,`@TemplateEnum`>> - a convenient annotation to access enum constants in a template.
 
diff --git a/_versions/3.15/guides/security-ldap.adoc b/_versions/3.15/guides/security-ldap.adoc
@@ -177,6 +177,18 @@ quarkus.security.ldap.identity-mapping.attribute-mappings."0".filter-base-dn=ou=
 
 The `elytron-security-ldap` extension requires a dir-context and an identity-mapping with at least one attribute-mapping to authenticate the user and its identity.
 
+=== Map LDAP groups to `SecurityIdentity` roles
+
+Previously described application configuration showed how to map `CN` attribute of the LDAP Distinguished Name group to a Quarkus `SecurityIdentity` role.
+More specifically, the `standardRole` CN was mapped to a `SecurityIdentity` role and thus allowed access to the `UserResource#me` endpoint.
+However, required `SecurityIdentity` roles may differ between applications and you may need to map LDAP groups to local `SecurityIdentity` roles like in the example below:
+
+[source,properties]
+----
+quarkus.http.auth.roles-mapping."standardRole"=user <1>
+----
+<1> Map the `standardRole` role to the application-specific `SecurityIdentity` role `user`.
+
 == Testing the Application
 
 The application is now protected and the identities are provided by our LDAP server.
diff --git a/_versions/3.15/guides/smallrye-fault-tolerance.adoc b/_versions/3.15/guides/smallrye-fault-tolerance.adoc
@@ -573,7 +573,7 @@ implementation("io.quarkus:quarkus-smallrye-fault-tolerance")
 == Additional resources
 
 SmallRye Fault Tolerance has more features than shown here.
-Please check the link:https://smallrye.io/docs/smallrye-fault-tolerance/6.3.0/index.html[SmallRye Fault Tolerance documentation] to learn about them.
+Please check the link:https://smallrye.io/docs/smallrye-fault-tolerance/6.4.2/index.html[SmallRye Fault Tolerance documentation] to learn about them.
 
 In Quarkus, you can use the SmallRye Fault Tolerance optional features out of the box.
 
@@ -605,7 +605,7 @@ smallrye.faulttolerance.mp-compatibility=true
 ----
 ====
 
-The link:https://smallrye.io/docs/smallrye-fault-tolerance/6.3.0/reference/programmatic-api.html[programmatic API] is present, including Mutiny support, and integrated with the declarative, annotation-based API.
+The link:https://smallrye.io/docs/smallrye-fault-tolerance/6.4.2/reference/programmatic-api.html[programmatic API] is present, including Mutiny support, and integrated with the declarative, annotation-based API.
 You can use the `FaultTolerance` and `MutinyFaultTolerance` APIs out of the box.
 
 Support for Kotlin is present (assuming you use the Quarkus extension for Kotlin), so you can guard your `suspend` functions with fault tolerance annotations.
diff --git a/_versions/3.15/guides/smallrye-graphql-client.adoc b/_versions/3.15/guides/smallrye-graphql-client.adoc
@@ -222,7 +222,7 @@ specify that within the `@GraphQLClientApi` annotation (by setting the `endpoint
 or move this over to the configuration file, `application.properties`:
 
 ----
-quarkus.smallrye-graphql-client.star-wars-typesafe.url=https://swapi-graphql.netlify.app/.netlify/functions/index
+quarkus.smallrye-graphql-client.star-wars-typesafe.url=https://swapi-graphql.netlify.app/graphql
 ----
 
 NOTE: During *tests only*, the URL is an optional property, and if it's not specified, Quarkus will assume
@@ -278,7 +278,7 @@ representations of the GraphQL types and documents. The client API interface is
 
 We still need to configure the URL for the client, so let's put this into `application.properties`:
 ----
-quarkus.smallrye-graphql-client.star-wars-dynamic.url=https://swapi-graphql.netlify.app/.netlify/functions/index
+quarkus.smallrye-graphql-client.star-wars-dynamic.url=https://swapi-graphql.netlify.app/graphql
 ----
 
 We decided to name the client `star-wars-dynamic`. We will use this name when injecting a dynamic client
diff --git a/_versions/3.15/guides/tls-registry-reference.adoc b/_versions/3.15/guides/tls-registry-reference.adoc
@@ -1076,7 +1076,7 @@ Note that the generated CA is only valid for development purposes and can only b
 To generate a development CA:
 [source,shell]
 ----
-quarkus tls generate-ca-certificate --install \   <1>
+quarkus tls generate-quarkus-ca --install \   <1>
      --renew \     <2>
      --truststore  <3>
 ----
