deploy: 1fa82dc

Author: gsmet

feed.xml

@@ -5,7 +5,7 @@
         <title>Quarkus</title>
         <link>https://quarkus.io</link>
         <description>Quarkus: Supersonic Subatomic Java</description>
-        <lastBuildDate>Thu, 26 Feb 2026 14:49:02 +0000</lastBuildDate>
+        <lastBuildDate>Fri, 27 Feb 2026 03:48:41 +0000</lastBuildDate>
 
 
         <item>

version/main/guides/all-builditems.html

@@ -1254,7 +1254,8 @@ <h2 id="core"><a class="anchor" href="#core"></a>Core</h2>
 <div id="conf-collapsible-desc-35" class="openblock description description-collapsed">
 <div class="content">
 <div class="paragraph">
-<p><em>No Javadoc found</em></p>
+<p>A <code>SimpleBuildItem</code> that loads an optional banner provider for the console formatter.
+Produced during compilation and obtained by the registry configuration to provide a banner at runtime by via <code>RuntimeValue</code> .</p>
 </div>
 </div>
 </div>
@@ -1265,7 +1266,7 @@ <h2 id="core"><a class="anchor" href="#core"></a>Core</h2>
 <p><code>io.quarkus.runtime.RuntimeValue&lt;Optional&lt;Supplier&lt;String&gt;&gt;&gt; bannerSupplier</code></p>
 </div>
 <div class="paragraph">
-<p><em>No Javadoc found</em></p>
+<p>A RuntimeValue that holds an Optional Supplier of String. The Supplier is used to generate the banner text when needed. The Optional allows for the possibility that no banner supplier is provided, in which case the banner will not be printed.</p>
 </div></div></td>
 </tr>
 <tr class="row-collapsible row-collapsed row-with-desc row-hidden">

version/main/guides/config-yaml.html

@@ -283,7 +283,8 @@ <h2 id="enable-yaml-configuration"><a class="anchor" href="#enable-yaml-configur
 </div>
 </div>
 <div class="paragraph">
-<p>After adding the extension or dependency, to avoid confusion, remove the <code>src/main/resources/application.properties</code> file and create a <code>src/main/resources/application.yaml</code> file.</p>
+<p>After adding the extension or dependency, to avoid confusion, remove the <code>src/main/resources/application.properties</code>
+file and create a <code>src/main/resources/application.yaml</code> file.</p>
 </div>
 <div class="admonitionblock note">
 <table>
@@ -304,7 +305,8 @@ <h2 id="enable-yaml-configuration"><a class="anchor" href="#enable-yaml-configur
 <i class="fa icon-tip" title="Tip"></i>
 </td>
 <td class="content">
-Quarkus recognizes both <code>.yml</code> and <code>.yaml</code> file extensions.
+Quarkus recognizes both <code>.yaml</code> and <code>.yml</code> file extensions. If both files are available, Quarkus
+gives precedence to the <code>.yaml</code> file and then the <code>.yml</code> file.
 </td>
 </tr>
 </table>
@@ -376,6 +378,21 @@ <h3 id="example-yaml-configurations"><a class="anchor" href="#example-yaml-confi
               plain-text: true</code></pre>
 </div>
 </div>
+<div class="admonitionblock tip">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-tip" title="Tip"></i>
+</td>
+<td class="content">
+<div class="paragraph">
+<p>You can also use JSON in the YAML file to describe the configuration. Use a single format per file. The file extension
+is either <code>yaml</code> or <code>yml</code>.</p>
+</div>
+</td>
+</tr>
+</table>
+</div>
 </div>
 </div>
 </div>
@@ -443,7 +460,7 @@ <h2 id="profiles"><a class="anchor" href="#profiles"></a>Profiles</h2>
 <div class="paragraph">
 <p>An <code>application.yaml</code> file must exist (even if empty) in the exact location of the profile-aware
 (<code>application-{profile}.yaml</code>) file to be included in the configuration to ensure a consistent order when
-loading the files.</p>
+loading the files. All profile files must match the same extension of the main file.</p>
 </div>
 </td>
 </tr>
@@ -518,61 +535,6 @@ <h2 id="configuration-property-conflicts"><a class="anchor" href="#configuration
 <div class="paragraph">
 <p>YAML <code>null</code> keys are not included in the assembly of the configuration property name, allowing them to be used at any level for disambiguating configuration properties.</p>
 </div>
-<div class="paragraph">
-<p>Although Quarkus primarily uses <code>.properties</code> file extension for configuration, the snakeyaml library, which is used for parsing YAML in Quarkus, can also parse JSON structures. This means you can use YAML files with JSON content inside.</p>
-</div>
-<div class="paragraph">
-<p>YAML and JSON structures can be read in an application.yaml file.</p>
-</div>
-<div class="paragraph">
-<p>Certainly, here&#8217;s a step-by-step guide on how to use complex configuration structures with Quarkus:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>Define Your Configuration Interface.</p>
-</li>
-</ul>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@ConfigMapping(prefix = "server")
-public interface ServiceConfig {
-
-  List&lt;Environment&gt; environments();
-
-  interface Environment {
-    String name();
-    String services();
-  }
-}</code></pre>
-</div>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>Create the appropriate JSON structure and store it in a YAML file.</p>
-</li>
-</ul>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code class="language-yaml hljs" data-lang="yaml">{
-  "server": {
-    "environments": [
-      {
-        "name": "dev",
-        "services": "bookstore"
-      },
-      {
-        "name": "batch",
-        "services": "warehouse"
-      }
-    ]
-  }
-}</code></pre>
-</div>
-</div>
 </div>
 </div>
     </div>

working-groups/index.html

@@ -210,67 +210,64 @@ <h2>Active working groups</h2>
     <div class="grid-wrapper working-groups-cards">
 
 
-    
-    
     <div class="card">
         <div class="card-header">
-            <p class="card-title">AOT Support</p>
+            <p class="card-title">Quarkus 4</p>
         </div>
         <div class="card-body">
             <p class="card-text"><span class="key">Status:</span>&nbsp;<span
                     class="status on-track">on track</span></p>
-            <p class="card-text"><span class="key">Description:</span>&nbsp;<span class="short-description">The main objective of this working group is to consolidate, enhance, and modernize Quarkus's Ahead-of-Time (AOT) and runtime efficiency (in JVM mode) capabilities. We aim to leverage OpenJDK's Project Leyden, IBM Semeru's advanced features, and JLink to provide a unified, "native-like" startup exper
+            <p class="card-text"><span class="key">Description:</span>&nbsp;<span class="short-description">The Quarkus 4 working group aims to coordinate and track all Quarkus 4-related development in a long-running effort.
 </span>
             </p>
-            <p class="card-text"><span class="key">Last Activity:</span>&nbsp;<span class="last-activity">February 24, 2026 </span>
-            </p>
-            
-            <p class="card-text"><span class="key">Point of Contact:</span>&nbsp;<span class="point-of-contact">Guillaume Smet (@gmset) / Georgios Andrianakis (@geoand)</span>
+            <p class="card-text"><span class="key">Last Activity:</span>&nbsp;<span class="last-activity">February 26, 2026 </span>
             </p>
 
         </div>
         <div class="card-footer">
             <div class="icons">
 
-                <a href="https://github.com/quarkusio/quarkus/discussions/52017" title="See the working group proposal"><i
-                        class="icon fa-regular fa-file-lines"></i></a>&nbsp;
-                
-                <a href="https://github.com/orgs/quarkusio/projects/68" title="View the working group board"><i
+                <a href="https://github.com/orgs/quarkusio/projects/51" title="View the working group board"><i
                         class="icon fa-brands fa-square-github"></i></a>&nbsp;
 
-                <a href="https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/AOT.20cache.20-.20Global.20thread/with/568847190" title="Discuss about the working group"><i
-                        class="icon fa-solid fa-comments"></i></a>&nbsp;
+                <a href="https://quarkusio.zulipchat.com/#narrow/stream/187038-dev"
+                   title="Discuss about the working group"><i class="icon fa-solid fa-comments"></i></a>
 
             </div>
         </div>
     </div>
 
 
 
+    
+    
     <div class="card">
         <div class="card-header">
-            <p class="card-title">Agentic Foundation and LangChain4j Next</p>
+            <p class="card-title">AOT Support</p>
         </div>
         <div class="card-body">
             <p class="card-text"><span class="key">Status:</span>&nbsp;<span
                     class="status on-track">on track</span></p>
-            <p class="card-text"><span class="key">Description:</span>&nbsp;<span class="short-description">This working group will explore and define the foundation of the next generation of AI-Infused and Agentic applications built with LangChain4j and Quarkus LangChain4j. The group will investigate core changes to the current programming model, improve dev exp, build stronger interoperability.
+            <p class="card-text"><span class="key">Description:</span>&nbsp;<span class="short-description">The main objective of this working group is to consolidate, enhance, and modernize Quarkus's Ahead-of-Time (AOT) and runtime efficiency (in JVM mode) capabilities. We aim to leverage OpenJDK's Project Leyden, IBM Semeru's advanced features, and JLink to provide a unified, "native-like" startup exper
 </span>
             </p>
             <p class="card-text"><span class="key">Last Activity:</span>&nbsp;<span class="last-activity">February 24, 2026 </span>
             </p>
 
+            <p class="card-text"><span class="key">Point of Contact:</span>&nbsp;<span class="point-of-contact">Guillaume Smet (@gmset) / Georgios Andrianakis (@geoand)</span>
+            </p>
+            
         </div>
         <div class="card-footer">
             <div class="icons">
 
-                <a href="https://github.com/quarkusio/quarkus/discussions/50582" title="See the working group proposal"><i
+                <a href="https://github.com/quarkusio/quarkus/discussions/52017" title="See the working group proposal"><i
                         class="icon fa-regular fa-file-lines"></i></a>&nbsp;
 
-                <a href="https://github.com/orgs/quarkiverse/projects/9" title="View the working group board"><i
+                <a href="https://github.com/orgs/quarkusio/projects/68" title="View the working group board"><i
                         class="icon fa-brands fa-square-github"></i></a>&nbsp;
 
-                <a href="https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/WG.20-.20Agentic.20Foundation.20and.20LangChain4j.20Next/with/547443137" title="Discuss about the working group"><i
+                <a href="https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/AOT.20cache.20-.20Global.20thread/with/568847190" title="Discuss about the working group"><i
                         class="icon fa-solid fa-comments"></i></a>&nbsp;
 
             </div>
@@ -281,12 +278,12 @@ <h2>Active working groups</h2>
 
     <div class="card">
         <div class="card-header">
-            <p class="card-title">Quarkus 4</p>
+            <p class="card-title">Agentic Foundation and LangChain4j Next</p>
         </div>
         <div class="card-body">
             <p class="card-text"><span class="key">Status:</span>&nbsp;<span
                     class="status on-track">on track</span></p>
-            <p class="card-text"><span class="key">Description:</span>&nbsp;<span class="short-description">The Quarkus 4 working group aims to coordinate and track all Quarkus 4-related development in a long-running effort.
+            <p class="card-text"><span class="key">Description:</span>&nbsp;<span class="short-description">This working group will explore and define the foundation of the next generation of AI-Infused and Agentic applications built with LangChain4j and Quarkus LangChain4j. The group will investigate core changes to the current programming model, improve dev exp, build stronger interoperability.
 </span>
             </p>
             <p class="card-text"><span class="key">Last Activity:</span>&nbsp;<span class="last-activity">February 24, 2026 </span>
@@ -296,11 +293,14 @@ <h2>Active working groups</h2>
         <div class="card-footer">
             <div class="icons">
 
-                <a href="https://github.com/orgs/quarkusio/projects/51" title="View the working group board"><i
+                <a href="https://github.com/quarkusio/quarkus/discussions/50582" title="See the working group proposal"><i
+                        class="icon fa-regular fa-file-lines"></i></a>&nbsp;
+                
+                <a href="https://github.com/orgs/quarkiverse/projects/9" title="View the working group board"><i
                         class="icon fa-brands fa-square-github"></i></a>&nbsp;
 
-                <a href="https://quarkusio.zulipchat.com/#narrow/stream/187038-dev"
-                   title="Discuss about the working group"><i class="icon fa-solid fa-comments"></i></a>
+                <a href="https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/WG.20-.20Agentic.20Foundation.20and.20LangChain4j.20Next/with/547443137" title="Discuss about the working group"><i
+                        class="icon fa-solid fa-comments"></i></a>&nbsp;
 
             </div>
         </div>
@@ -737,6 +737,8 @@ <h2>LTS versions</h2>
 
 
 
+        
+        
         <div class="card">
             <div class="card-header">
                 <p class="card-title">Quarkus 3.33 LTS</p>
@@ -789,8 +791,6 @@ <h2>LTS versions</h2>
 
 
 
-        
-        
 
 
 
@@ -877,6 +877,8 @@ <h2>Paused working groups</h2>
     <div class="grid-wrapper working-groups-cards">
 
 
+        
+        
         <div class="card">
             <div class="card-header">
                 <p class="card-title">Quarkus 3.33 LTS</p>
@@ -937,8 +939,6 @@ <h2>Paused working groups</h2>
 
 
 
-        
-