From 7782d6902562a920abf745525fc37054febbb6a4 Mon Sep 17 00:00:00 2001
From: Matej Novotny <manovotn@redhat.com>
Date: Thu, 26 Oct 2023 09:57:56 +0000
Subject: [PATCH] Published master to GitHub pages.

---
 dist/index.html                           |  25 +
 documentation/index.html                  |  13 +-
 download/index.html                       |  50 +-
 index.html                                |  30 +-
 news.atom                                 | 589 +++++++---------------
 news/2023/10/26/weld-600Alpha1/index.html | 304 +++++++++++
 news/index.html                           | 202 ++++----
 news/page/10.html                         | 393 ++++-----------
 news/page/11.html                         | 342 +++++++++++--
 news/page/12.html                         | 141 ++----
 news/page/13.html                         | 166 +++---
 news/page/14.html                         | 129 ++---
 news/page/15.html                         | 198 +++-----
 news/page/16.html                         | 294 +++++------
 news/page/17.html                         | 177 ++++++-
 news/page/18.html                         |  18 +
 news/page/2.html                          | 124 +++--
 news/page/3.html                          |  97 ++--
 news/page/4.html                          | 159 +++---
 news/page/5.html                          | 225 ++++-----
 news/page/6.html                          | 168 ++++--
 news/page/7.html                          | 171 ++-----
 news/page/8.html                          | 248 ++++-----
 news/page/9.html                          | 210 ++++----
 news/tags/release/index.html              | 150 ++++--
 news/tags/release/page/2.html             | 134 ++---
 news/tags/release/page/3.html             | 291 ++++-------
 news/tags/release/page/4.html             | 299 +++++++----
 news/tags/release/page/5.html             | 188 ++++---
 news/tags/release/page/6.html             |  82 +++
 sitemap.xml                               |  20 +-
 31 files changed, 2999 insertions(+), 2638 deletions(-)
 create mode 100644 news/2023/10/26/weld-600Alpha1/index.html

diff --git a/dist/index.html b/dist/index.html
index 9cfd1207..da4f67db 100644
--- a/dist/index.html
+++ b/dist/index.html
@@ -157,6 +157,31 @@ <h1>Download - binary distribution archive</h1>
                     Download
                   </th>
                 </tr>
+                <tr>
+                  <td class="version">
+                    6.0.0.Alpha1
+                  </td>
+                  <td>
+                    <strong>
+                      Experimental
+                    </strong>
+                  </td>
+                  <td>
+                  </td>
+                  <td>
+                    26.10.2023
+                  </td>
+                  <td>
+                    <a href="https://issues.redhat.com/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12413485">
+                      Changelog
+                    </a>
+                  </td>
+                  <td>
+                    <a href="http://download.jboss.org/weld/6.0.0.Alpha1">
+                      Download
+                    </a>
+                  </td>
+                </tr>
                 <tr>
                   <td class="version">
                     5.1.2.Final
diff --git a/documentation/index.html b/documentation/index.html
index 84696236..c30b1628 100644
--- a/documentation/index.html
+++ b/documentation/index.html
@@ -139,7 +139,7 @@ <h1>Documentation</h1>
               <p>Weld reference documentation can be viewed online or downloaded as a PDF.</p>
               <ul>
                 <li>
-                  The latest Weld 5 version:
+                  The latest Weld 6 version:
                   <ul>
                     <li>
                       <a href="http://docs.jboss.org/weld/reference/latest/en-US/html_single/" target="_blank">HTML (Single page)</a>
@@ -149,6 +149,17 @@ <h1>Documentation</h1>
                     </li>
                   </ul>
                 </li>
+                <li>
+                  The latest Weld 5 version:
+                  <ul>
+                    <li>
+                      <a href="http://docs.jboss.org/weld/reference/latest-5.1/en-US/html_single/" target="_blank">HTML (Single page)</a>
+                    </li>
+                    <li>
+                      <a href="http://docs.jboss.org/weld/reference/latest-5.1/en-US/pdf/weld-reference.pdf" target="_blank">PDF</a>
+                    </li>
+                  </ul>
+                </li>
                 <li>
                   The latest Weld 4 version:
                   <ul>
diff --git a/download/index.html b/download/index.html
index c4e3828c..fbb0cf6c 100644
--- a/download/index.html
+++ b/download/index.html
@@ -207,6 +207,32 @@ <h2>Binary distribution</h2>
                     Download
                   </th>
                 </tr>
+                <tr>
+                  <td class="version">
+                    6.0.0.Alpha1
+                  </td>
+                  <td>
+                    <strong>
+                      Experimental
+                    </strong>
+                  </td>
+                  <td>
+                    4.1
+                  </td>
+                  <td>
+                    26.10.2023
+                  </td>
+                  <td>
+                    <a href="https://issues.redhat.com/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12413485">
+                      Changelog
+                    </a>
+                  </td>
+                  <td>
+                    <a href="https://download.jboss.org/weld/6.0.0.Alpha1">
+                      Download
+                    </a>
+                  </td>
+                </tr>
                 <tr>
                   <td class="version">
                     5.1.2.Final
@@ -423,30 +449,6 @@ <h2>Binary distribution</h2>
                     </a>
                   </td>
                 </tr>
-                <tr>
-                  <td class="version">
-                    5.0.0.CR2
-                  </td>
-                  <td>
-                    Preview
-                  </td>
-                  <td>
-                    4.0
-                  </td>
-                  <td>
-                    23.03.2022
-                  </td>
-                  <td>
-                    <a href="https://issues.redhat.com/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12382781">
-                      Changelog
-                    </a>
-                  </td>
-                  <td>
-                    <a href="https://download.jboss.org/weld/5.0.0.CR2">
-                      Download
-                    </a>
-                  </td>
-                </tr>
               </table>
               <p></p>
               <a href="/dist">
diff --git a/index.html b/index.html
index 9661e7ce..5e2a2fdc 100644
--- a/index.html
+++ b/index.html
@@ -549,10 +549,10 @@ <h2>
                     <ul class="newsColumn">
                       <li>
                         <h3>
-                          <a href="/news/2023/10/05/weld-512Final/">Weld 5.1.2.Final</a>
+                          <a href="/news/2023/10/26/weld-600Alpha1/">Weld 6.0.0.Alpha1</a>
                         </h3>
                         <div class="news-date news-boxed">
-                          2023-10-5
+                          2023-10-26
                           &nbsp;
                           <span class="tags">
                             <i class="fa fa-tags"></i>
@@ -560,16 +560,16 @@ <h3>
                           </span>
                         </div>
                         <p>
-                          Weld 5.1.2.Final is now available
+                          Weld 6.0.0.Alpha1 is now available
                         </p>
                         <hr>
                       </li>
                       <li>
                         <h3>
-                          <a href="/news/2023/08/09/weld-511SP2/">Weld 5.1.1.SP2</a>
+                          <a href="/news/2023/10/05/weld-512Final/">Weld 5.1.2.Final</a>
                         </h3>
                         <div class="news-date news-boxed">
-                          2023-8-9
+                          2023-10-5
                           &nbsp;
                           <span class="tags">
                             <i class="fa fa-tags"></i>
@@ -577,16 +577,16 @@ <h3>
                           </span>
                         </div>
                         <p>
-                          Weld 5.1.1.SP2 available
+                          Weld 5.1.2.Final is now available
                         </p>
                         <hr>
                       </li>
                       <li>
                         <h3>
-                          <a href="/news/2023/07/11/weld-511SP1/">Weld 5.1.1.SP1</a>
+                          <a href="/news/2023/08/09/weld-511SP2/">Weld 5.1.1.SP2</a>
                         </h3>
                         <div class="news-date news-boxed">
-                          2023-7-11
+                          2023-8-9
                           &nbsp;
                           <span class="tags">
                             <i class="fa fa-tags"></i>
@@ -594,16 +594,16 @@ <h3>
                           </span>
                         </div>
                         <p>
-                          Weld 5.1.1.SP1 available
+                          Weld 5.1.1.SP2 available
                         </p>
                         <hr>
                       </li>
                       <li>
                         <h3>
-                          <a href="/news/2023/06/12/weld-511Final/">Weld 5.1.1.Final</a>
+                          <a href="/news/2023/07/11/weld-511SP1/">Weld 5.1.1.SP1</a>
                         </h3>
                         <div class="news-date news-boxed">
-                          2023-6-12
+                          2023-7-11
                           &nbsp;
                           <span class="tags">
                             <i class="fa fa-tags"></i>
@@ -611,16 +611,16 @@ <h3>
                           </span>
                         </div>
                         <p>
-                          Weld 5.1.1.Final released!
+                          Weld 5.1.1.SP1 available
                         </p>
                         <hr>
                       </li>
                       <li>
                         <h3>
-                          <a href="/news/2022/10/03/weld-510Final/">Weld 5.1.0.Final</a>
+                          <a href="/news/2023/06/12/weld-511Final/">Weld 5.1.1.Final</a>
                         </h3>
                         <div class="news-date news-boxed">
-                          2022-10-3
+                          2023-6-12
                           &nbsp;
                           <span class="tags">
                             <i class="fa fa-tags"></i>
@@ -628,7 +628,7 @@ <h3>
                           </span>
                         </div>
                         <p>
-                          Weld 5.1 and dropping Weld Probe
+                          Weld 5.1.1.Final released!
                         </p>
                         <hr>
                       </li>
diff --git a/news.atom b/news.atom
index 4034812a..d8f1228e 100644
--- a/news.atom
+++ b/news.atom
@@ -2,13 +2,150 @@
 <feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
   <id>https://weld.cdi-spec.org/</id>
   <title>Weld</title>
-  <updated>2023-10-05T20:22:24+00:00</updated>
+  <updated>2023-10-26T09:41:51+00:00</updated>
   <link href="https://weld.cdi-spec.org/news.atom" rel="self" type="application/atom+xml" />
   <link href="https://weld.cdi-spec.org/" rel="alternate" type="text/html" />
+  <entry>
+    <id>https://weld.cdi-spec.org/news/2023/10/26/weld-600Alpha1/</id>
+    <title>Weld 6.0.0.Alpha1</title>
+    <updated>2023-10-26T09:41:51+00:00</updated>
+    <published>2023-10-26T00:00:00+00:00</published>
+    <link href="https://weld.cdi-spec.org/news/2023/10/26/weld-600Alpha1/" rel="alternate" type="text/html" />
+    <author>
+      <name>Matej Novotny</name>
+    </author>
+    <category term="release"></category>
+    <summary>
+      Looking for a CDI 4.1 implementation? We&#8217;ve got you covered!
+      Weld Core 6.0.0.Alpha1 is now available and comes along with CDI API 4.1.0.Alpha1.
+      Note that this version also uses latest version (2.2.0-RC1) of the Jakarta Interceptors specification.
+      
+      
+      CDI/CDI TCK related additions:
+      
+      
+      
+      
+      Create first implementation of CDI method invokers using MethodHandles (WELD-2764)
+      
+      
+      
+      If you want to read up more about the original CDI API design and PR, take a look (here)
+      
+      
+      Note that this feature is still being improved on both, CDI side and (Weld side) but the general shape of it is already carved out
+      
+      
+      
+      
+      
+      Support standardized means of getting interceptor bindings from InvocationContext (WELD-2756)
+      
+      
+      
+      This was already...
+    </summary>
+    <content type="html">
+      &lt;div class=&quot;paragraph&quot;&gt;
+      &lt;p&gt;Looking for a CDI 4.1 implementation? We’ve got you covered!
+      Weld Core 6.0.0.Alpha1 is now available and comes along with CDI API 4.1.0.Alpha1.
+      Note that this version also uses latest version (2.2.0-RC1) of the Jakarta Interceptors specification.&lt;/p&gt;
+      &lt;/div&gt;
+      &lt;div class=&quot;paragraph&quot;&gt;
+      &lt;p&gt;CDI/CDI TCK related additions:&lt;/p&gt;
+      &lt;/div&gt;
+      &lt;div class=&quot;ulist&quot;&gt;
+      &lt;ul&gt;
+      &lt;li&gt;
+      &lt;p&gt;Create first implementation of CDI method invokers using &lt;code&gt;MethodHandles&lt;/code&gt; (&lt;a href=&quot;https://issues.redhat.com/browse/WELD-2764&quot;&gt;WELD-2764&lt;/a&gt;)&lt;/p&gt;
+      &lt;div class=&quot;ulist&quot;&gt;
+      &lt;ul&gt;
+      &lt;li&gt;
+      &lt;p&gt;If you want to read up more about the original CDI API design and PR, take a look (&lt;a href=&quot;https://github.com/jakartaee/cdi/pull/639&quot;&gt;here&lt;/a&gt;)&lt;/p&gt;
+      &lt;/li&gt;
+      &lt;li&gt;
+      &lt;p&gt;Note that this feature is still being improved on both, CDI side and (&lt;a href=&quot;https://issues.redhat.com/browse/WELD-2765&quot;&gt;Weld side&lt;/a&gt;) but the general shape of it is already carved out&lt;/p&gt;
+      &lt;/li&gt;
+      &lt;/ul&gt;
+      &lt;/div&gt;
+      &lt;/li&gt;
+      &lt;li&gt;
+      &lt;p&gt;Support standardized means of getting interceptor bindings from &lt;code&gt;InvocationContext&lt;/code&gt; (&lt;a href=&quot;https://issues.redhat.com/browse/WELD-2756&quot;&gt;WELD-2756&lt;/a&gt;)&lt;/p&gt;
+      &lt;div class=&quot;ulist&quot;&gt;
+      &lt;ul&gt;
+      &lt;li&gt;
+      &lt;p&gt;This was already possible via set of methods in &lt;code&gt;WeldInvocationContext&lt;/code&gt; as well as the &lt;code&gt;String&lt;/code&gt; key under which we stored these bindings in &lt;code&gt;InvocationContext&lt;/code&gt;&lt;/p&gt;
+      &lt;/li&gt;
+      &lt;li&gt;
+      &lt;p&gt;Both of the above are no deprecated (but still working) and users are expected to use the standardized approach&lt;/p&gt;
+      &lt;/li&gt;
+      &lt;/ul&gt;
+      &lt;/div&gt;
+      &lt;/li&gt;
+      &lt;li&gt;
+      &lt;p&gt;Support inspectable &lt;code&gt;CreationalContext&lt;/code&gt; and &lt;code&gt;Contextual&lt;/code&gt; in CDI TCK SPI (&lt;a href=&quot;https://issues.redhat.com/browse/WELD-2757&quot;&gt;WELD-2757&lt;/a&gt;)&lt;/p&gt;
+      &lt;/li&gt;
+      &lt;/ul&gt;
+      &lt;/div&gt;
+      &lt;div class=&quot;paragraph&quot;&gt;
+      &lt;p&gt;Other bugfixes and project QoL features:&lt;/p&gt;
+      &lt;/div&gt;
+      &lt;div class=&quot;ulist&quot;&gt;
+      &lt;ul&gt;
+      &lt;li&gt;
+      &lt;p&gt;Fix proxy creation for beans using &lt;code&gt;@Typed&lt;/code&gt; and having package-protected types split across packages (&lt;a href=&quot;https://issues.redhat.com/browse/WELD-2758&quot;&gt;WELD-2758&lt;/a&gt;)&lt;/p&gt;
+      &lt;/li&gt;
+      &lt;li&gt;
+      &lt;p&gt;Correct how we determine proxy package for beans with unassignable types in their bean type set (&lt;a href=&quot;https://issues.redhat.com/browse/WELD-2763&quot;&gt;WELD-2763&lt;/a&gt;)&lt;/p&gt;
+      &lt;div class=&quot;ulist&quot;&gt;
+      &lt;ul&gt;
+      &lt;li&gt;
+      &lt;p&gt;This  was only problematic in environments using &lt;code&gt;WeldDefaultProxyServices&lt;/code&gt; to define their proxies (such as Weld SE)&lt;/p&gt;
+      &lt;/li&gt;
+      &lt;/ul&gt;
+      &lt;/div&gt;
+      &lt;/li&gt;
+      &lt;li&gt;
+      &lt;p&gt;&lt;code&gt;WeldManager#getContexts&lt;/code&gt; now correctly returns an empty set when there are no contexts for given scope (&lt;a href=&quot;https://issues.redhat.com/browse/WELD-2761&quot;&gt;WELD-2761&lt;/a&gt;)&lt;/p&gt;
+      &lt;/li&gt;
+      &lt;li&gt;
+      &lt;p&gt;Fix possible memory leak with repetitive thread group creation (&lt;a href=&quot;https://issues.redhat.com/browse/WELD-2755&quot;&gt;WELD-2755&lt;/a&gt;)&lt;/p&gt;
+      &lt;/li&gt;
+      &lt;li&gt;
+      &lt;p&gt;&lt;code&gt;WeldInitialListener&lt;/code&gt; can no longer throw NPE is application fails to start (&lt;a href=&quot;https://issues.redhat.com/browse/WELD-2752&quot;&gt;WELD-2752&lt;/a&gt;)&lt;/p&gt;
+      &lt;div class=&quot;ulist&quot;&gt;
+      &lt;ul&gt;
+      &lt;li&gt;
+      &lt;p&gt;Only possible in some EE containers on repeated re-deployment of Weld applications&lt;/p&gt;
+      &lt;/li&gt;
+      &lt;/ul&gt;
+      &lt;/div&gt;
+      &lt;/li&gt;
+      &lt;li&gt;
+      &lt;p&gt;&lt;code&gt;LazySessionBeanStore&lt;/code&gt; no longer swallows exceptions happening when attempting to initiate HTTP session (&lt;a href=&quot;https://issues.redhat.com/browse/WELD-2762&quot;&gt;WELD-2762&lt;/a&gt;)&lt;/p&gt;
+      &lt;/li&gt;
+      &lt;li&gt;
+      &lt;p&gt;Weld Core and Weld API are now using formatter plugin and impsort instead of checkstyle (&lt;a href=&quot;https://issues.redhat.com/browse/WELD-2753&quot;&gt;WELD-2753&lt;/a&gt;)&lt;/p&gt;
+      &lt;/li&gt;
+      &lt;li&gt;
+      &lt;p&gt;Jandex version was bumped to 3.x across the project (&lt;a href=&quot;https://issues.redhat.com/browse/WELD-2754&quot;&gt;WELD-2754&lt;/a&gt;)&lt;/p&gt;
+      &lt;/li&gt;
+      &lt;/ul&gt;
+      &lt;/div&gt;
+      &lt;div class=&quot;paragraph&quot;&gt;
+      &lt;p&gt;As always, if you find further issues with Weld 6, let us know and we’ll try to help.&lt;/p&gt;
+      &lt;/div&gt;
+      &lt;div class=&quot;paragraph&quot;&gt;
+      &lt;p&gt;[ &lt;a href=&quot;https://weld.cdi-spec.org/download/&quot;&gt;Download&lt;/a&gt; ]
+      [ &lt;a href=&quot;http://docs.jboss.org/weld/reference/6.0.0.Alpha1/en-US/html_single/&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;Documentation&lt;/a&gt; ]
+      [ &lt;a href=&quot;https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;amp;version=12413485&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;Release notes&lt;/a&gt; ]&lt;/p&gt;
+      &lt;/div&gt;
+    </content>
+  </entry>
   <entry>
     <id>https://weld.cdi-spec.org/news/2023/10/05/weld-512Final/</id>
     <title>Weld 5.1.2.Final</title>
-    <updated>2023-10-05T20:22:24+00:00</updated>
+    <updated>2023-10-26T08:44:55+00:00</updated>
     <published>2023-10-05T00:00:00+00:00</published>
     <link href="https://weld.cdi-spec.org/news/2023/10/05/weld-512Final/" rel="alternate" type="text/html" />
     <author>
@@ -96,7 +233,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2023/08/09/weld-511SP2/</id>
     <title>Weld 5.1.1.SP2</title>
-    <updated>2023-08-09T09:01:51+00:00</updated>
+    <updated>2023-10-26T08:44:55+00:00</updated>
     <published>2023-08-09T00:00:00+00:00</published>
     <link href="https://weld.cdi-spec.org/news/2023/08/09/weld-511SP2/" rel="alternate" type="text/html" />
     <author>
@@ -139,7 +276,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2023/07/11/weld-511SP1/</id>
     <title>Weld 5.1.1.SP1</title>
-    <updated>2023-08-09T09:01:51+00:00</updated>
+    <updated>2023-10-26T08:44:55+00:00</updated>
     <published>2023-07-11T00:00:00+00:00</published>
     <link href="https://weld.cdi-spec.org/news/2023/07/11/weld-511SP1/" rel="alternate" type="text/html" />
     <author>
@@ -203,7 +340,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2023/06/12/weld-511Final/</id>
     <title>Weld 5.1.1.Final</title>
-    <updated>2023-08-09T09:01:51+00:00</updated>
+    <updated>2023-10-26T08:44:55+00:00</updated>
     <published>2023-06-12T00:00:00+00:00</published>
     <link href="https://weld.cdi-spec.org/news/2023/06/12/weld-511Final/" rel="alternate" type="text/html" />
     <author>
@@ -292,7 +429,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2022/10/03/weld-510Final/</id>
     <title>Weld 5.1.0.Final</title>
-    <updated>2023-08-09T09:01:51+00:00</updated>
+    <updated>2023-10-26T08:44:55+00:00</updated>
     <published>2022-10-03T00:00:00+00:00</published>
     <link href="https://weld.cdi-spec.org/news/2022/10/03/weld-510Final/" rel="alternate" type="text/html" />
     <author>
@@ -384,7 +521,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2022/06/24/weld-501Final/</id>
     <title>Weld 5.0.1.Final</title>
-    <updated>2023-08-09T09:01:51+00:00</updated>
+    <updated>2023-10-26T08:44:55+00:00</updated>
     <published>2022-06-24T00:00:00+00:00</published>
     <link href="https://weld.cdi-spec.org/news/2022/06/24/weld-501Final/" rel="alternate" type="text/html" />
     <author>
@@ -459,7 +596,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2022/06/08/weld-500SP2/</id>
     <title>Weld 5.0.0.SP2</title>
-    <updated>2023-08-09T09:01:51+00:00</updated>
+    <updated>2023-10-26T08:44:55+00:00</updated>
     <published>2022-06-08T00:00:00+00:00</published>
     <link href="https://weld.cdi-spec.org/news/2022/06/08/weld-500SP2/" rel="alternate" type="text/html" />
     <author>
@@ -504,7 +641,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2022/05/04/weld-500SP1/</id>
     <title>Weld 5.0.0.SP1</title>
-    <updated>2023-08-09T09:01:51+00:00</updated>
+    <updated>2023-10-26T08:44:55+00:00</updated>
     <published>2022-05-04T00:00:00+00:00</published>
     <link href="https://weld.cdi-spec.org/news/2022/05/04/weld-500SP1/" rel="alternate" type="text/html" />
     <author>
@@ -549,7 +686,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2022/04/29/weld-500Final/</id>
     <title>Weld 5.0.0.Final</title>
-    <updated>2023-08-09T09:01:51+00:00</updated>
+    <updated>2023-10-26T08:44:55+00:00</updated>
     <published>2022-04-29T00:00:00+00:00</published>
     <link href="https://weld.cdi-spec.org/news/2022/04/29/weld-500Final/" rel="alternate" type="text/html" />
     <author>
@@ -632,7 +769,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2022/03/23/weld-500CR2/</id>
     <title>Weld 5.0.0.CR2</title>
-    <updated>2023-08-09T09:01:51+00:00</updated>
+    <updated>2023-10-26T08:44:55+00:00</updated>
     <published>2022-03-23T00:00:00+00:00</published>
     <link href="https://weld.cdi-spec.org/news/2022/03/23/weld-500CR2/" rel="alternate" type="text/html" />
     <author>
@@ -672,7 +809,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2022/02/23/weld-500CR1/</id>
     <title>Weld 5.0.0.CR1</title>
-    <updated>2023-08-09T09:01:51+00:00</updated>
+    <updated>2023-10-26T08:44:55+00:00</updated>
     <published>2022-02-23T00:00:00+00:00</published>
     <link href="https://weld.cdi-spec.org/news/2022/02/23/weld-500CR1/" rel="alternate" type="text/html" />
     <author>
@@ -741,7 +878,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2022/02/16/weld-403Final-319Final/</id>
     <title>Weld 4.0.3.Final and 3.1.9.Final</title>
-    <updated>2023-08-09T09:01:51+00:00</updated>
+    <updated>2023-10-26T08:44:55+00:00</updated>
     <published>2022-02-16T00:00:00+00:00</published>
     <link href="https://weld.cdi-spec.org/news/2022/02/16/weld-403Final-319Final/" rel="alternate" type="text/html" />
     <author>
@@ -838,7 +975,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2022/01/24/weld-500Beta1/</id>
     <title>Weld 5.0.0.Beta1</title>
-    <updated>2023-08-09T09:01:51+00:00</updated>
+    <updated>2023-10-26T08:44:55+00:00</updated>
     <published>2022-01-24T00:00:00+00:00</published>
     <link href="https://weld.cdi-spec.org/news/2022/01/24/weld-500Beta1/" rel="alternate" type="text/html" />
     <author>
@@ -1149,7 +1286,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2021/07/14/weld-402Final-318Final/</id>
     <title>Weld 4.0.2.Final and 3.1.8.Final</title>
-    <updated>2023-08-09T09:01:51+00:00</updated>
+    <updated>2023-10-26T08:44:55+00:00</updated>
     <published>2021-07-14T00:00:00+00:00</published>
     <link href="https://weld.cdi-spec.org/news/2021/07/14/weld-402Final-318Final/" rel="alternate" type="text/html" />
     <author>
@@ -1230,7 +1367,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2021/04/14/weld-401SP1-317SP1/</id>
     <title>Weld 4.0.1.SP1 and 3.1.7.SP1</title>
-    <updated>2023-08-09T09:01:51+00:00</updated>
+    <updated>2023-10-26T08:44:55+00:00</updated>
     <published>2021-04-14T00:00:00+00:00</published>
     <link href="https://weld.cdi-spec.org/news/2021/04/14/weld-401SP1-317SP1/" rel="alternate" type="text/html" />
     <author>
@@ -1310,7 +1447,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2021/03/22/weld-401Final/</id>
     <title>Weld 4.0.1.Final</title>
-    <updated>2023-08-09T09:01:51+00:00</updated>
+    <updated>2023-10-26T08:44:55+00:00</updated>
     <published>2021-03-22T00:00:00+00:00</published>
     <link href="https://weld.cdi-spec.org/news/2021/03/22/weld-401Final/" rel="alternate" type="text/html" />
     <author>
@@ -1429,7 +1566,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2021/03/18/weld-317Final/</id>
     <title>Weld 3.1.7.Final</title>
-    <updated>2023-08-09T09:01:51+00:00</updated>
+    <updated>2023-10-26T08:44:55+00:00</updated>
     <published>2021-03-18T00:00:00+00:00</published>
     <link href="https://weld.cdi-spec.org/news/2021/03/18/weld-317Final/" rel="alternate" type="text/html" />
     <author>
@@ -1543,7 +1680,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2021/01/13/weld-316Final/</id>
     <title>Weld 3.1.6.Final</title>
-    <updated>2023-08-09T09:01:51+00:00</updated>
+    <updated>2023-10-26T08:44:55+00:00</updated>
     <published>2021-01-13T00:00:00+00:00</published>
     <link href="https://weld.cdi-spec.org/news/2021/01/13/weld-316Final/" rel="alternate" type="text/html" />
     <author>
@@ -1701,7 +1838,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2020/12/16/weld-400Final/</id>
     <title>Weld 4.0.0.Final</title>
-    <updated>2023-08-09T09:01:51+00:00</updated>
+    <updated>2023-10-26T08:44:55+00:00</updated>
     <published>2020-12-16T00:00:00+00:00</published>
     <link href="https://weld.cdi-spec.org/news/2020/12/16/weld-400Final/" rel="alternate" type="text/html" />
     <author>
@@ -1779,7 +1916,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2020/09/18/weld-400Beta1/</id>
     <title>Weld 4.0.0.Beta1</title>
-    <updated>2023-08-09T09:01:51+00:00</updated>
+    <updated>2023-10-26T08:44:55+00:00</updated>
     <published>2020-09-18T00:00:00+00:00</published>
     <link href="https://weld.cdi-spec.org/news/2020/09/18/weld-400Beta1/" rel="alternate" type="text/html" />
     <author>
@@ -1896,7 +2033,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2020/08/12/weld-315Final/</id>
     <title>Weld 3.1.5.Final</title>
-    <updated>2023-08-09T09:01:51+00:00</updated>
+    <updated>2023-10-26T08:44:55+00:00</updated>
     <published>2020-08-12T00:00:00+00:00</published>
     <link href="https://weld.cdi-spec.org/news/2020/08/12/weld-315Final/" rel="alternate" type="text/html" />
     <author>
@@ -2034,7 +2171,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2020/05/13/weld-jakarta-ee-9/</id>
     <title>Weld 4 and Jakarta EE 9</title>
-    <updated>2023-08-09T09:01:51+00:00</updated>
+    <updated>2023-10-26T08:44:55+00:00</updated>
     <published>2020-05-13T00:00:00+00:00</published>
     <link href="https://weld.cdi-spec.org/news/2020/05/13/weld-jakarta-ee-9/" rel="alternate" type="text/html" />
     <author>
@@ -2173,7 +2310,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2020/03/28/weld-314Final/</id>
     <title>Weld 3.1.4.Final</title>
-    <updated>2023-08-09T09:01:51+00:00</updated>
+    <updated>2023-10-26T08:44:55+00:00</updated>
     <published>2020-03-28T00:00:00+00:00</published>
     <link href="https://weld.cdi-spec.org/news/2020/03/28/weld-314Final/" rel="alternate" type="text/html" />
     <author>
@@ -2285,7 +2422,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2019/11/28/weld-313Final/</id>
     <title>Weld 3.1.3.Final</title>
-    <updated>2023-08-09T09:01:51+00:00</updated>
+    <updated>2023-10-26T08:44:55+00:00</updated>
     <published>2019-11-28T00:00:00+00:00</published>
     <link href="https://weld.cdi-spec.org/news/2019/11/28/weld-313Final/" rel="alternate" type="text/html" />
     <author>
@@ -2419,7 +2556,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2019/08/06/weld-312Final/</id>
     <title>Weld 3.1.2.Final</title>
-    <updated>2023-08-09T09:01:51+00:00</updated>
+    <updated>2023-10-26T08:44:55+00:00</updated>
     <published>2019-08-06T00:00:00+00:00</published>
     <link href="https://weld.cdi-spec.org/news/2019/08/06/weld-312Final/" rel="alternate" type="text/html" />
     <author>
@@ -2573,7 +2710,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2019/05/07/weld-311Final/</id>
     <title>Weld 3.1.1.Final</title>
-    <updated>2023-08-09T09:01:51+00:00</updated>
+    <updated>2023-10-26T08:44:55+00:00</updated>
     <published>2019-05-07T00:00:00+00:00</published>
     <link href="https://weld.cdi-spec.org/news/2019/05/07/weld-311Final/" rel="alternate" type="text/html" />
     <author>
@@ -2706,7 +2843,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2019/02/06/weld-310Final/</id>
     <title>Weld 3.1.0.Final</title>
-    <updated>2023-08-09T09:01:51+00:00</updated>
+    <updated>2023-10-26T08:44:55+00:00</updated>
     <published>2019-02-06T00:00:00+00:00</published>
     <link href="https://weld.cdi-spec.org/news/2019/02/06/weld-310Final/" rel="alternate" type="text/html" />
     <author>
@@ -2958,7 +3095,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2018/09/26/weld-248Final/</id>
     <title>Weld 2.4.8.Final</title>
-    <updated>2023-08-09T09:01:51+00:00</updated>
+    <updated>2023-10-26T08:44:55+00:00</updated>
     <published>2018-09-26T00:00:00+00:00</published>
     <link href="https://weld.cdi-spec.org/news/2018/09/26/weld-248Final/" rel="alternate" type="text/html" />
     <author>
@@ -3095,7 +3232,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2018/07/26/weld-305Final/</id>
     <title>Weld 3.0.5.Final</title>
-    <updated>2023-08-09T09:01:51+00:00</updated>
+    <updated>2023-10-26T08:44:55+00:00</updated>
     <published>2018-07-26T00:00:00+00:00</published>
     <link href="https://weld.cdi-spec.org/news/2018/07/26/weld-305Final/" rel="alternate" type="text/html" />
     <author>
@@ -3259,7 +3396,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2018/07/10/weld-team-changes/</id>
     <title>Weld team changes</title>
-    <updated>2023-08-09T09:01:51+00:00</updated>
+    <updated>2023-10-26T08:44:55+00:00</updated>
     <published>2018-07-10T00:00:00+00:00</published>
     <link href="https://weld.cdi-spec.org/news/2018/07/10/weld-team-changes/" rel="alternate" type="text/html" />
     <author>
@@ -3308,7 +3445,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2018/04/26/weld-304Final/</id>
     <title>Weld 3.0.4.Final</title>
-    <updated>2023-08-09T09:01:51+00:00</updated>
+    <updated>2023-10-26T08:44:55+00:00</updated>
     <published>2018-04-26T00:00:00+00:00</published>
     <link href="https://weld.cdi-spec.org/news/2018/04/26/weld-304Final/" rel="alternate" type="text/html" />
     <author>
@@ -3507,7 +3644,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2018/03/20/weld-247Final/</id>
     <title>Weld 2.4.7.Final</title>
-    <updated>2023-08-09T09:01:51+00:00</updated>
+    <updated>2023-10-26T08:44:55+00:00</updated>
     <published>2018-03-20T00:00:00+00:00</published>
     <link href="https://weld.cdi-spec.org/news/2018/03/20/weld-247Final/" rel="alternate" type="text/html" />
     <author>
@@ -3690,7 +3827,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2018/02/09/weld-303Final/</id>
     <title>Weld 3.0.3.Final</title>
-    <updated>2023-08-09T09:01:51+00:00</updated>
+    <updated>2023-10-26T08:44:55+00:00</updated>
     <published>2018-02-09T00:00:00+00:00</published>
     <link href="https://weld.cdi-spec.org/news/2018/02/09/weld-303Final/" rel="alternate" type="text/html" />
     <author>
@@ -3825,7 +3962,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2017/12/19/weld-meets-junit5/</id>
     <title>Weld meets JUnit 5</title>
-    <updated>2023-08-09T09:01:51+00:00</updated>
+    <updated>2023-10-26T08:44:55+00:00</updated>
     <published>2017-12-19T00:00:00+00:00</published>
     <link href="https://weld.cdi-spec.org/news/2017/12/19/weld-meets-junit5/" rel="alternate" type="text/html" />
     <author>
@@ -4002,7 +4139,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2017/12/18/weld-246Final/</id>
     <title>Weld 2.4.6.Final</title>
-    <updated>2023-08-09T09:01:51+00:00</updated>
+    <updated>2023-10-26T08:44:55+00:00</updated>
     <published>2017-12-18T00:00:00+00:00</published>
     <link href="https://weld.cdi-spec.org/news/2017/12/18/weld-246Final/" rel="alternate" type="text/html" />
     <author>
@@ -4181,7 +4318,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2017/11/23/weld-302Final/</id>
     <title>Weld 3.0.2.Final</title>
-    <updated>2023-08-09T09:01:51+00:00</updated>
+    <updated>2023-10-26T08:44:55+00:00</updated>
     <published>2017-11-23T00:00:00+00:00</published>
     <link href="https://weld.cdi-spec.org/news/2017/11/23/weld-302Final/" rel="alternate" type="text/html" />
     <author>
@@ -4356,7 +4493,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2017/09/11/weld-245Final/</id>
     <title>Weld 2.4.5.Final</title>
-    <updated>2023-08-09T09:01:51+00:00</updated>
+    <updated>2023-10-26T08:44:55+00:00</updated>
     <published>2017-09-11T00:00:00+00:00</published>
     <link href="https://weld.cdi-spec.org/news/2017/09/11/weld-245Final/" rel="alternate" type="text/html" />
     <author>
@@ -4473,7 +4610,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2017/08/25/weld-301Final/</id>
     <title>Weld 3.0.1.Final</title>
-    <updated>2023-08-09T09:01:51+00:00</updated>
+    <updated>2023-10-26T08:44:55+00:00</updated>
     <published>2017-08-25T00:00:00+00:00</published>
     <link href="https://weld.cdi-spec.org/news/2017/08/25/weld-301Final/" rel="alternate" type="text/html" />
     <author>
@@ -4624,7 +4761,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2017/08/07/weld-vertx-next/</id>
     <title>Weld Vert.x Next?</title>
-    <updated>2023-08-09T09:01:51+00:00</updated>
+    <updated>2023-10-26T08:44:55+00:00</updated>
     <published>2017-08-07T00:00:00+00:00</published>
     <link href="https://weld.cdi-spec.org/news/2017/08/07/weld-vertx-next/" rel="alternate" type="text/html" />
     <author>
@@ -4883,7 +5020,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2017/06/14/weld-244Final/</id>
     <title>Weld 2.4.4.Final</title>
-    <updated>2023-08-09T09:01:51+00:00</updated>
+    <updated>2023-10-26T08:44:55+00:00</updated>
     <published>2017-06-14T00:00:00+00:00</published>
     <link href="https://weld.cdi-spec.org/news/2017/06/14/weld-244Final/" rel="alternate" type="text/html" />
     <author>
@@ -5035,7 +5172,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2017/05/19/tour-around-weld-3/</id>
     <title>Tour around Weld 3</title>
-    <updated>2023-08-09T09:01:51+00:00</updated>
+    <updated>2023-10-26T08:44:55+00:00</updated>
     <published>2017-05-19T00:00:00+00:00</published>
     <link href="https://weld.cdi-spec.org/news/2017/05/19/tour-around-weld-3/" rel="alternate" type="text/html" />
     <author>
@@ -5353,7 +5490,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2017/05/15/weld-300Final/</id>
     <title>Weld 3.0.0.Final - the first implementation of CDI 2.0!</title>
-    <updated>2023-08-09T09:01:51+00:00</updated>
+    <updated>2023-10-26T08:44:55+00:00</updated>
     <published>2017-05-15T00:00:00+00:00</published>
     <link href="https://weld.cdi-spec.org/news/2017/05/15/weld-300Final/" rel="alternate" type="text/html" />
     <author>
@@ -5531,7 +5668,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2017/04/07/weld-243Final/</id>
     <title>Weld 2.4.3.Final</title>
-    <updated>2023-08-09T09:01:51+00:00</updated>
+    <updated>2023-10-26T08:44:55+00:00</updated>
     <published>2017-04-07T00:00:00+00:00</published>
     <link href="https://weld.cdi-spec.org/news/2017/04/07/weld-243Final/" rel="alternate" type="text/html" />
     <author>
@@ -5659,7 +5796,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2017/03/03/weld-300CR2/</id>
     <title>Weld 3.0.0.CR2</title>
-    <updated>2023-08-09T09:01:51+00:00</updated>
+    <updated>2023-10-26T08:44:55+00:00</updated>
     <published>2017-03-03T00:00:00+00:00</published>
     <link href="https://weld.cdi-spec.org/news/2017/03/03/weld-300CR2/" rel="alternate" type="text/html" />
     <author>
@@ -5795,7 +5932,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2017/02/02/weld-242Final/</id>
     <title>Weld 2.4.2.Final</title>
-    <updated>2023-08-09T09:01:51+00:00</updated>
+    <updated>2023-10-26T08:44:55+00:00</updated>
     <published>2017-02-02T00:00:00+00:00</published>
     <link href="https://weld.cdi-spec.org/news/2017/02/02/weld-242Final/" rel="alternate" type="text/html" />
     <author>
@@ -5913,7 +6050,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2017/02/01/tip4-testing/</id>
     <title>Weld Tip 4 - Testing CDI/Weld apps</title>
-    <updated>2023-08-09T09:01:51+00:00</updated>
+    <updated>2023-10-26T08:44:55+00:00</updated>
     <published>2017-02-01T00:00:00+00:00</published>
     <link href="https://weld.cdi-spec.org/news/2017/02/01/tip4-testing/" rel="alternate" type="text/html" />
     <author>
@@ -6176,7 +6313,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2017/01/23/weld-300CR1/</id>
     <title>Weld 3.0.0.CR1</title>
-    <updated>2023-08-09T09:01:51+00:00</updated>
+    <updated>2023-10-26T08:44:55+00:00</updated>
     <published>2017-01-23T00:00:00+00:00</published>
     <link href="https://weld.cdi-spec.org/news/2017/01/23/weld-300CR1/" rel="alternate" type="text/html" />
     <author>
@@ -6228,7 +6365,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2016/12/19/weld-300Beta1/</id>
     <title>Weld 3.0.0.Beta1</title>
-    <updated>2023-08-09T09:01:51+00:00</updated>
+    <updated>2023-10-26T08:44:55+00:00</updated>
     <published>2016-12-19T00:00:00+00:00</published>
     <link href="https://weld.cdi-spec.org/news/2016/12/19/weld-300Beta1/" rel="alternate" type="text/html" />
     <author>
@@ -6339,7 +6476,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2016/11/18/weld-241Final/</id>
     <title>Weld 2.4.1.Final</title>
-    <updated>2023-08-09T09:01:51+00:00</updated>
+    <updated>2023-10-26T08:44:55+00:00</updated>
     <published>2016-11-18T00:00:00+00:00</published>
     <link href="https://weld.cdi-spec.org/news/2016/11/18/weld-241Final/" rel="alternate" type="text/html" />
     <author>
@@ -6439,356 +6576,4 @@
       &lt;/div&gt;
     </content>
   </entry>
-  <entry>
-    <id>https://weld.cdi-spec.org/news/2016/10/25/tip3-performance/</id>
-    <title>Weld Tip 3 - Boost performance of Weld apps</title>
-    <updated>2023-08-09T09:01:51+00:00</updated>
-    <published>2016-10-25T00:00:00+00:00</published>
-    <link href="https://weld.cdi-spec.org/news/2016/10/25/tip3-performance/" rel="alternate" type="text/html" />
-    <author>
-      <name>Martin Kouba</name>
-    </author>
-    <category term="tips"></category>
-    <summary>
-      Contents
-      
-      Bootstrap
-      
-      Discovery mode
-      Extensions
-      Jandex
-      
-      
-      Runtime
-      
-      Identify problematic components easily
-      Lazy initialization of bean instances
-      Drawbacks of @Dependent pseudo-scope
-      Mapping CDI contexts to HTTP requests
-      Bean identifier index optimization
-      
-      
-      
-      
-      
-      In this article we&#8217;re going to dive into various performance aspects of CDI applications.
-      As you&#8217;ve probably noticed performance testing is sometimes tricky.
-      First of all, it&#8217;s difficult to create a meaningful benchmark.
-      One should understand the JVM specifics (the need for warmup, garbage collection, JVM settings, etc.) and also use appropriate tools (e.g. JMH for microbenchmarks) accordingly.
-      But even that usually proves to be unsufficient.
-      One should also run the test in a relevant context (data, load, etc.).
-      Performance specialists also say that&#8217;s it&#8217;s good to...
-    </summary>
-    <content type="html">
-      &lt;div id=&quot;toc&quot; class=&quot;toc&quot;&gt;
-      &lt;div id=&quot;toctitle&quot; class=&quot;title&quot;&gt;Contents&lt;/div&gt;
-      &lt;ul class=&quot;sectlevel1&quot;&gt;
-      &lt;li&gt;&lt;a href=&quot;#_bootstrap&quot;&gt;Bootstrap&lt;/a&gt;
-      &lt;ul class=&quot;sectlevel2&quot;&gt;
-      &lt;li&gt;&lt;a href=&quot;#_discovery_mode&quot;&gt;Discovery mode&lt;/a&gt;&lt;/li&gt;
-      &lt;li&gt;&lt;a href=&quot;#_extensions&quot;&gt;Extensions&lt;/a&gt;&lt;/li&gt;
-      &lt;li&gt;&lt;a href=&quot;#jandex&quot;&gt;Jandex&lt;/a&gt;&lt;/li&gt;
-      &lt;/ul&gt;
-      &lt;/li&gt;
-      &lt;li&gt;&lt;a href=&quot;#_runtime&quot;&gt;Runtime&lt;/a&gt;
-      &lt;ul class=&quot;sectlevel2&quot;&gt;
-      &lt;li&gt;&lt;a href=&quot;#_identify_problematic_components_easily&quot;&gt;Identify problematic components easily&lt;/a&gt;&lt;/li&gt;
-      &lt;li&gt;&lt;a href=&quot;#_lazy_initialization_of_bean_instances&quot;&gt;Lazy initialization of bean instances&lt;/a&gt;&lt;/li&gt;
-      &lt;li&gt;&lt;a href=&quot;#_drawbacks_of_dependent_pseudo_scope&quot;&gt;Drawbacks of &lt;code&gt;@Dependent&lt;/code&gt; pseudo-scope&lt;/a&gt;&lt;/li&gt;
-      &lt;li&gt;&lt;a href=&quot;#_mapping_cdi_contexts_to_http_requests&quot;&gt;Mapping CDI contexts to HTTP requests&lt;/a&gt;&lt;/li&gt;
-      &lt;li&gt;&lt;a href=&quot;#_bean_identifier_index_optimization&quot;&gt;Bean identifier index optimization&lt;/a&gt;&lt;/li&gt;
-      &lt;/ul&gt;
-      &lt;/li&gt;
-      &lt;/ul&gt;
-      &lt;/div&gt;
-      &lt;div class=&quot;paragraph&quot;&gt;
-      &lt;p&gt;In this article we’re going to dive into various performance aspects of CDI applications.
-      As you’ve probably noticed performance testing is sometimes tricky.
-      First of all, it’s difficult to create a meaningful benchmark.
-      One should understand the JVM specifics (the need for warmup, garbage collection, JVM settings, etc.) and also use appropriate tools (e.g. &lt;a href=&quot;http://openjdk.java.net/projects/code-tools/jmh/&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;JMH&lt;/a&gt; for microbenchmarks) accordingly.
-      But even that usually proves to be unsufficient.
-      One should also run the test in a relevant context (data, load, etc.).
-      Performance specialists also say that’s it’s good to avoid premature optimizations but keep performance aspects in mind when tuning the &quot;final&quot; code.
-      But all these considerations are out of scope of this article.
-      Let’s go through several areas where CDI affects the performance of your application and discuss the possibilities.&lt;/p&gt;
-      &lt;/div&gt;
-      &lt;div class=&quot;sect1&quot;&gt;
-      &lt;h2 id=&quot;_bootstrap&quot;&gt;Bootstrap&lt;/h2&gt;
-      &lt;div class=&quot;sectionbody&quot;&gt;
-      &lt;div class=&quot;paragraph&quot;&gt;
-      &lt;p&gt;During bootstrap the overhead of a framework should be minimal so that it does not &lt;em&gt;slow down&lt;/em&gt; the application startup and also does not eat all the memory available.
-      However, CDI needs to do all that magic behind the scenes - read annotations, build and validate metadata, etc.
-      The following sections describe what could be done to minimize the impact.&lt;/p&gt;
-      &lt;/div&gt;
-      &lt;div class=&quot;sect2&quot;&gt;
-      &lt;h3 id=&quot;_discovery_mode&quot;&gt;Discovery mode&lt;/h3&gt;
-      &lt;div class=&quot;paragraph&quot;&gt;
-      &lt;p&gt;In CDI 1.0 there was only one &lt;em&gt;&quot;discovery mode&quot;&lt;/em&gt;.
-      How does it work?
-      Simply put: find all bean archives (containing &lt;code&gt;beans.xml&lt;/code&gt;), discover and process all the found classes (identify beans, etc.).
-      Needless to say, this might be a performance problem for large applications with thousands of classes.
-      In CDI 1.1+ we call this mode &lt;code&gt;all&lt;/code&gt; and a bean archive with this mode is called &lt;strong&gt;EXPLICIT&lt;/strong&gt;.
-      Since CDI 1.1+ a new discovery mode - &lt;code&gt;annotated&lt;/code&gt; - can be used.
-      The difference is that if this mode is used only classes with a &lt;a href=&quot;http://docs.jboss.org/cdi/spec/1.2/cdi-spec.html#bean_defining_annotations&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;bean defining annotation&lt;/a&gt; are considered.
-      In other words, a component must be explicitly designated.
-      A bean archive with this mode is called &lt;strong&gt;IMPLICIT&lt;/strong&gt;.
-      To make things a little bit more complicated, an implicit bean archive does not have to contain a &lt;code&gt;beans.xml&lt;/code&gt; file at all.
-      One class with a bean defining annotation or a session bean is enough.&lt;/p&gt;
-      &lt;/div&gt;
-      &lt;div class=&quot;paragraph&quot;&gt;
-      &lt;p&gt;Implicit bean archive has pros and cons:&lt;/p&gt;
-      &lt;/div&gt;
-      &lt;div class=&quot;ulist&quot;&gt;
-      &lt;ul&gt;
-      &lt;li&gt;
-      &lt;p&gt;&lt;span class=&quot;icon&quot;&gt;&lt;i class=&quot;fa fa-thumbs-o-up&quot; /&gt;&lt;/span&gt; saves a lot of memory if an archive contains a lot of classes which should NOT become beans (the container does not have to store the metadata)&lt;/p&gt;
-      &lt;/li&gt;
-      &lt;li&gt;
-      &lt;p&gt;&lt;span class=&quot;icon&quot;&gt;&lt;i class=&quot;fa fa-thumbs-o-up&quot; /&gt;&lt;/span&gt; speeds up the bootstrap (the container does not have to process all the types, fire events like &lt;code&gt;ProcessBean&lt;/code&gt;, etc.)&lt;/p&gt;
-      &lt;/li&gt;
-      &lt;li&gt;
-      &lt;p&gt;&lt;span class=&quot;icon&quot;&gt;&lt;i class=&quot;fa fa-thumbs-down&quot; /&gt;&lt;/span&gt; does not fire &lt;code&gt;ProcessAnnotatedType&lt;/code&gt; for all types from the bean archive; this breaks some extensions (e.g. &lt;code&gt;MessageBundleExtension&lt;/code&gt; from DeltaSpike)&lt;/p&gt;
-      &lt;/li&gt;
-      &lt;li&gt;
-      &lt;p&gt;&lt;span class=&quot;icon&quot;&gt;&lt;i class=&quot;fa fa-thumbs-down&quot; /&gt;&lt;/span&gt; does not pick up &lt;code&gt;@javax.inject.Singleton&lt;/code&gt; beans (it’s not a bean defining annotation)&lt;/p&gt;
-      &lt;/li&gt;
-      &lt;/ul&gt;
-      &lt;/div&gt;
-      &lt;div class=&quot;paragraph&quot;&gt;
-      &lt;p&gt;&lt;strong&gt;CONCLUSION&lt;/strong&gt;: If possible, use the &lt;code&gt;annotated&lt;/code&gt; discovery mode.&lt;/p&gt;
-      &lt;/div&gt;
-      &lt;div class=&quot;admonitionblock tip&quot;&gt;
-      &lt;table&gt;
-      &lt;tr&gt;
-      &lt;td class=&quot;icon&quot;&gt;
-      &lt;i class=&quot;fa icon-tip&quot; title=&quot;Tip&quot; /&gt;
-      &lt;/td&gt;
-      &lt;td class=&quot;content&quot;&gt;
-      Most Weld-based runtimes allow to suppress implicit bean archives without &lt;code&gt;beans.xml&lt;/code&gt;, i.e. to require the &lt;code&gt;beans.xml&lt;/code&gt; file in bean archives so that it’s not necessary to scan all the parts of the application. See also &lt;a href=&quot;https://weld.cdi-spec.org/documentation/#4&quot;&gt;FAQ&lt;/a&gt;.
-      &lt;/td&gt;
-      &lt;/tr&gt;
-      &lt;/table&gt;
-      &lt;/div&gt;
-      &lt;div class=&quot;admonitionblock tip&quot;&gt;
-      &lt;table&gt;
-      &lt;tr&gt;
-      &lt;td class=&quot;icon&quot;&gt;
-      &lt;i class=&quot;fa icon-tip&quot; title=&quot;Tip&quot; /&gt;
-      &lt;/td&gt;
-      &lt;td class=&quot;content&quot;&gt;
-      If it’s not possible to use &lt;code&gt;annotated&lt;/code&gt; mode, you can try a Weld-specific feature to conserve memory used: &lt;a href=&quot;http://docs.jboss.org/weld/reference/latest/en-US/html/configure.html#veto-types-without-bean-defining-annotation&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;Veto types without bean defining annotation&lt;/a&gt;.
-      A similar solution is going to be standardized in CDI 2.0 (see also &lt;a href=&quot;https://issues.jboss.org/browse/CDI-420&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;CDI-420&lt;/a&gt;).
-      &lt;/td&gt;
-      &lt;/tr&gt;
-      &lt;/table&gt;
-      &lt;/div&gt;
-      &lt;/div&gt;
-      &lt;div class=&quot;sect2&quot;&gt;
-      &lt;h3 id=&quot;_extensions&quot;&gt;Extensions&lt;/h3&gt;
-      &lt;div class=&quot;paragraph&quot;&gt;
-      &lt;p&gt;CDI portable extensions are essential integration points.
-      And users love integrated technologies.
-      However, the more extensions the more work must be done during bootstrap.
-      For example, there is a &lt;code&gt;ProcessAnnotatedType&lt;/code&gt; container lifecycle event.
-      This event is fired:&lt;/p&gt;
-      &lt;/div&gt;
-      &lt;div class=&quot;ulist&quot;&gt;
-      &lt;ul&gt;
-      &lt;li&gt;
-      &lt;p&gt;for every type in an EXPLICIT bean archive,&lt;/p&gt;
-      &lt;/li&gt;
-      &lt;li&gt;
-      &lt;p&gt;for every session bean and every type with a bean defining annotation in an IMPLICIT bean archive.&lt;/p&gt;
-      &lt;/li&gt;
-      &lt;/ul&gt;
-      &lt;/div&gt;
-      &lt;div class=&quot;paragraph&quot;&gt;
-      &lt;p&gt;The delivery might be restricted by means of type arguments, e.g. for observer &lt;code&gt;void observeNumbers(@Observes ProcessAnnotatedType&amp;lt;? extends Number&amp;gt; event)&lt;/code&gt; an extension will be notified for every class assignable to &lt;code&gt;Number&lt;/code&gt;.
-      However, if you do &lt;code&gt;&amp;lt;T&amp;gt; void observe(@Observes ProcessAnnotatedType&amp;lt;T&amp;gt; event)&lt;/code&gt; your extension will be notified for every class that is discovered.
-      Now if we have an application with one EXPLICIT bean archive with 2000 classes, then a specific observer method on such extesion will be called 2000x.
-      And if there are three similar extensions, the CDI container will have to create 2000 events and notify 6000 observers.
-      This should be ok unless the observer logic is overly complex.&lt;/p&gt;
-      &lt;/div&gt;
-      &lt;div class=&quot;paragraph&quot;&gt;
-      &lt;p&gt;&lt;strong&gt;CONCLUSION&lt;/strong&gt;: Pay attention to extensions used in your application.
-      If you wonder what extensions are in service, use for example Weld Probe observers view or fired events view together with &lt;a href=&quot;http://docs.jboss.org/weld/reference/latest/en-US/html/configure.html#config-dev-mode&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;&lt;code&gt;org.jboss.weld.probe.eventMonitor.containerLifecycleEvents&lt;/code&gt; enabled&lt;/a&gt;.&lt;/p&gt;
-      &lt;/div&gt;
-      &lt;div class=&quot;admonitionblock tip&quot;&gt;
-      &lt;table&gt;
-      &lt;tr&gt;
-      &lt;td class=&quot;icon&quot;&gt;
-      &lt;i class=&quot;fa icon-tip&quot; title=&quot;Tip&quot; /&gt;
-      &lt;/td&gt;
-      &lt;td class=&quot;content&quot;&gt;
-      If possible, don’t use the extensions which observe all the annotated types from your application, i.e. which defined something like &lt;code&gt;void observe(@Observes ProcessAnnotatedType&amp;lt;?&amp;gt; event)&lt;/code&gt;.
-      Since CDI 1.1 &lt;code&gt;@WithAnnotations&lt;/code&gt; should be used to restrict the set of types an extension is going to process. Weld Probe warns you about these extensions.
-      &lt;/td&gt;
-      &lt;/tr&gt;
-      &lt;/table&gt;
-      &lt;/div&gt;
-      &lt;/div&gt;
-      &lt;div class=&quot;sect2&quot;&gt;
-      &lt;h3 id=&quot;jandex&quot;&gt;Jandex&lt;/h3&gt;
-      &lt;div class=&quot;paragraph&quot;&gt;
-      &lt;p&gt;In some environments (WildFly, Weld SE, and more) Weld can leverage an &quot;offline reflection library&quot;, such as &lt;a href=&quot;https://github.com/wildfly/jandex&quot; target=&quot;&amp;lt;em&amp;gt;blank&quot;&gt;Jandex&lt;/a&gt;, to speed up the scanning process.
-      These libraries allow to effectively filter classes &lt;a href=&quot;http://docs.jboss.org/cdi/spec/1.2/cdi-spec.html#what_classes_are_beans&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;which are not beans&lt;/a&gt; and vetoed classes.
-      It works like this: Jandex generates an index (scans the bytecode) and Weld is using this index to filter out useless classes.
-      As a result Weld does not even have to _load the classes&lt;/p&gt; or use &lt;em&gt;reflection API&lt;/em&gt; to detect types which should be ignored.&lt;/div&gt;
-      &lt;/div&gt;
-      &lt;div class=&quot;admonitionblock tip&quot;&gt;
-      &lt;table&gt;
-      &lt;tr&gt;
-      &lt;td class=&quot;icon&quot;&gt;
-      &lt;i class=&quot;fa icon-tip&quot; title=&quot;Tip&quot; /&gt;
-      &lt;/td&gt;
-      &lt;td class=&quot;content&quot;&gt;
-      In Weld SE and Servlet it’s also possible to generate the Jandex index beforehand, e.g. using the &lt;a href=&quot;https://github.com/wildfly/jandex#user-content-using-the-ant-task-to-index-your-project&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;Ant task&lt;/a&gt;.
-      &lt;/td&gt;
-      &lt;/tr&gt;
-      &lt;/table&gt;
-      &lt;/div&gt;
-      &lt;/div&gt;
-      &lt;/div&gt;
-      
-      &lt;div class=&quot;sect1&quot;&gt;
-      &lt;h2 id=&quot;_runtime&quot;&gt;Runtime&lt;/h2&gt;
-      &lt;div class=&quot;sectionbody&quot;&gt;
-      &lt;div class=&quot;paragraph&quot;&gt;
-      &lt;p&gt;In runtime the overhead of a framework should be minimal so that it’s not an application bottleneck.
-      However, CDI needs to do all that magic behind the scenes - create bean instances, manage contexts, intercept and decorate invocations, etc.
-      The following sections describe what could be done to minimize the impact.&lt;/p&gt;
-      &lt;/div&gt;
-      &lt;div class=&quot;sect2&quot;&gt;
-      &lt;h3 id=&quot;_identify_problematic_components_easily&quot;&gt;Identify problematic components easily&lt;/h3&gt;
-      &lt;div class=&quot;paragraph&quot;&gt;
-      &lt;p&gt;Before you start a profiler or a similar tool, it’s a good idea to identify all the CDI components involved in a problematic &quot;request&quot;.
-      This means all the beans, observer methods, interceptors and decorators.
-      The good start might be the Weld Probe invocation trees view.
-      An invocation tree shows all the business method invocations (including producers, disposers and observer methods).
-      Once you spot a problematic component, you can check the business logic and associated interceptors and decorators.
-      Sometimes profilers are just an overkill.&lt;/p&gt;
-      &lt;/div&gt;
-      &lt;/div&gt;
-      &lt;div class=&quot;sect2&quot;&gt;
-      &lt;h3 id=&quot;_lazy_initialization_of_bean_instances&quot;&gt;Lazy initialization of bean instances&lt;/h3&gt;
-      &lt;div class=&quot;paragraph&quot;&gt;
-      &lt;p&gt;Weld initializes bean instances of normal scoped beans lazily.
-      In other words, when injecting a normal scoped bean (&lt;code&gt;@RequestScoped&lt;/code&gt;, &lt;code&gt;@ApplicationScoped&lt;/code&gt;, etc.) a new instance is not created until actually used.
-      Instead, a shared client proxy is injected.
-      This proxy invokes a method upon the correct bean instance (created if necessary).&lt;/p&gt;
-      &lt;/div&gt;
-      &lt;div class=&quot;admonitionblock tip&quot;&gt;
-      &lt;table&gt;
-      &lt;tr&gt;
-      &lt;td class=&quot;icon&quot;&gt;
-      &lt;i class=&quot;fa icon-tip&quot; title=&quot;Tip&quot; /&gt;
-      &lt;/td&gt;
-      &lt;td class=&quot;content&quot;&gt;
-      Having many injection points resolving to normal scoped beans does not necessarily mean additional overhead associated with bean instance creation.
-      &lt;/td&gt;
-      &lt;/tr&gt;
-      &lt;/table&gt;
-      &lt;/div&gt;
-      &lt;div class=&quot;paragraph&quot;&gt;
-      &lt;p&gt;In the following example, an &lt;code&gt;OrderProcessor&lt;/code&gt; instance is not created until its &lt;code&gt;OrderProcess.process()&lt;/code&gt; method is called:&lt;/p&gt;
-      &lt;/div&gt;
-      &lt;div class=&quot;listingblock&quot;&gt;
-      &lt;div class=&quot;content&quot;&gt;
-      &lt;pre class=&quot;highlightjs highlight&quot;&gt;&lt;code class=&quot;language-java hljs&quot; data-lang=&quot;java&quot;&gt;@ApplicationScoped
-      class OrderProcessor {
-        @PostConstruct
-        void init() {
-          // Do some expensive initialization logic
-        }
-        void process() {
-          // Business logic
-        }
-      }
-      @RequestScoped
-      class OrderService {
-        @Inject
-        OrderProcessor processor; // A shared client proxy is injected
-      
-        void create(Order order) {
-          if (order.isValid()) {
-              // Processor is not initialized unless we have a valid order
-              processor.process(order);
-          }
-        }
-      }&lt;/code&gt;&lt;/pre&gt;
-      &lt;/div&gt;
-      &lt;/div&gt;
-      &lt;div class=&quot;admonitionblock tip&quot;&gt;
-      &lt;table&gt;
-      &lt;tr&gt;
-      &lt;td class=&quot;icon&quot;&gt;
-      &lt;i class=&quot;fa icon-tip&quot; title=&quot;Tip&quot; /&gt;
-      &lt;/td&gt;
-      &lt;td class=&quot;content&quot;&gt;
-      Weld’s session context is also initilized lazily and doesn’t require an HTTP session to actually exist until a bean instance must be written (i.e. until a method of a &lt;code&gt;@SessionScoped&lt;/code&gt; bean is invoked).
-      &lt;/td&gt;
-      &lt;/tr&gt;
-      &lt;/table&gt;
-      &lt;/div&gt;
-      &lt;/div&gt;
-      &lt;div class=&quot;sect2&quot;&gt;
-      &lt;h3 id=&quot;_drawbacks_of_dependent_pseudo_scope&quot;&gt;Drawbacks of &lt;code&gt;@Dependent&lt;/code&gt; pseudo-scope&lt;/h3&gt;
-      &lt;div class=&quot;paragraph&quot;&gt;
-      &lt;p&gt;From performance point of view &lt;code&gt;@Dependent&lt;/code&gt; is NOT a best fit for:&lt;/p&gt;
-      &lt;/div&gt;
-      &lt;div class=&quot;ulist&quot;&gt;
-      &lt;ul&gt;
-      &lt;li&gt;
-      &lt;p&gt;&lt;span class=&quot;icon&quot;&gt;&lt;i class=&quot;fa fa-thumbs-down&quot; /&gt;&lt;/span&gt; a bean that declares a producer which is frequently used (i.e. the produced bean is created very often)&lt;/p&gt;
-      &lt;/li&gt;
-      &lt;li&gt;
-      &lt;p&gt;&lt;span class=&quot;icon&quot;&gt;&lt;i class=&quot;fa fa-thumbs-down&quot; /&gt;&lt;/span&gt; a bean that declares an observer method which is frequently notified (i.e. the event is fired very often)&lt;/p&gt;
-      &lt;/li&gt;
-      &lt;li&gt;
-      &lt;p&gt;&lt;span class=&quot;icon&quot;&gt;&lt;i class=&quot;fa fa-thumbs-down&quot; /&gt;&lt;/span&gt; a bean which is used in EL expressions&lt;/p&gt;
-      &lt;/li&gt;
-      &lt;/ul&gt;
-      &lt;/div&gt;
-      &lt;div class=&quot;paragraph&quot;&gt;
-      &lt;p&gt;For all these cases, a new &lt;code&gt;@Dependent&lt;/code&gt; bean instance is created to handle the logic and destroyed when the invocation/evaluation completes.
-      In other words, the bean instances are not reused.
-      That’s not necessarily a problem if a bean does not have an &quot;expensive&quot; initialization or depends on others &quot;heavyweight&quot; components.
-      But very often, a wider scope is more suitable.&lt;/p&gt;
-      &lt;/div&gt;
-      &lt;/div&gt;
-      &lt;div class=&quot;sect2&quot;&gt;
-      &lt;h3 id=&quot;_mapping_cdi_contexts_to_http_requests&quot;&gt;Mapping CDI contexts to HTTP requests&lt;/h3&gt;
-      &lt;div class=&quot;paragraph&quot;&gt;
-      &lt;p&gt;By default, bult-in CDI contexts are activated at the beginning of an HTTP request processing and deactivated once the processing finishes.
-      This might be an unnecessary overhead in certain situations, e.g. when serving static resources (images, JavaScript, etc.).
-      Weld allows to activate the contexts only for a subset of requests only.
-      A regular expression may be used for filtering HTTP requests that should have contexts active during their processing.&lt;/p&gt;
-      &lt;/div&gt;
-      &lt;div class=&quot;listingblock&quot;&gt;
-      &lt;div class=&quot;content&quot;&gt;
-      &lt;pre class=&quot;highlightjs highlight&quot;&gt;&lt;code class=&quot;language-xml hljs&quot; data-lang=&quot;xml&quot;&gt;&amp;lt;web-app version=&quot;3.1&quot; xmlns=&quot;http://xmlns.jcp.org/xml/ns/javaee/&quot;
-          xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
-          xsi:schemaLocation=&quot;http://xmlns.jcp.org/xml/ns/javaee http://xmlns.jcp.org/xml/ns/javaee/web-app_3_1.xsd&quot;&amp;gt;
-          &amp;lt;context-param&amp;gt;
-              &amp;lt;param-name&amp;gt;org.jboss.weld.context.mapping&amp;lt;/param-name&amp;gt;
-              &amp;lt;param-value&amp;gt;.*\.html&amp;lt;/param-value&amp;gt; &amp;lt;!-- Only activate contexts for resources with html suffix, e.g. /some/path.html --&amp;gt;
-          &amp;lt;/context-param&amp;gt;
-      &amp;lt;/web-app&amp;gt;&lt;/code&gt;&lt;/pre&gt;
-      &lt;/div&gt;
-      &lt;/div&gt;
-      &lt;/div&gt;
-      &lt;div class=&quot;sect2&quot;&gt;
-      &lt;h3 id=&quot;_bean_identifier_index_optimization&quot;&gt;Bean identifier index optimization&lt;/h3&gt;
-      &lt;div class=&quot;paragraph&quot;&gt;
-      &lt;p&gt;This optimization is used to &lt;strong&gt;reduce the HTTP session replication overhead&lt;/strong&gt; (clustering use case).
-      Simply put: Weld tries to minimize the amount of bytes send over the network.
-      However, the inconsistency detection mechanism may cause problems in environments where application stop does not imply HTTP session destruction.
-      Thus it’s disabled by default in Servlet containers.
-      See also the &lt;a href=&quot;http://docs.jboss.org/weld/reference/latest/en-US/html/configure.html#_bean_identifier_index_optimization&quot;&gt;reference guide&lt;/a&gt; for more info.&lt;/p&gt;
-      &lt;/div&gt;
-      &lt;/div&gt;
-      &lt;/div&gt;
-      &lt;/div&gt;
-    </content>
-  </entry>
 </feed>
diff --git a/news/2023/10/26/weld-600Alpha1/index.html b/news/2023/10/26/weld-600Alpha1/index.html
new file mode 100644
index 00000000..b701cc47
--- /dev/null
+++ b/news/2023/10/26/weld-600Alpha1/index.html
@@ -0,0 +1,304 @@
+<!DOCTYPE html>
+<html>
+  <head>
+    <meta charset="utf-8">
+    <title>
+      Weld: Weld 6.0.0.Alpha1
+    </title>
+    <meta content="width=device-width, initial-scale=1.0" name="viewport">
+    <meta content="Weld 6.0.0.Alpha1 is now available" name="description">
+    <link href="/images/weld_icon_32x.ico" rel="shortcut icon" type="image/x-icon">
+    <link href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.5/css/bootstrap.min.css" rel="stylesheet" type="text/css">
+    <link href="https://maxcdn.bootstrapcdn.com/font-awesome/4.4.0/css/font-awesome.min.css" rel="stylesheet" type="text/css">
+    <link href="//static.jboss.org/css/tabzilla.css" media="screen" rel="stylesheet" type="text/css">
+    <link href="https://weld.cdi-spec.org/stylesheets/styles.css" rel="stylesheet" type="text/css">
+    <script src="//static.jboss.org/theme/js/libs/jquery/jquery-1.9.1.min.js" type="text/javascript"></script>
+    <script src="//static.jboss.org/js/_jbossorg-tabzilla.js" type="text/javascript"></script>
+    <!--[if lt IE 9]>
+      <script src="//html5shim.googlecode.com/svn/trunk/html5.js" type="text/javascript"></script>
+    <![endif]-->
+    <link href="https://weld.cdi-spec.org/news.atom" rel="alternate" type="application/atom+xml">
+    <link href="//cdn.jsdelivr.net/highlight.js/8.9.1/styles/hybrid.min.css" rel="stylesheet">
+    <script src="//cdn.jsdelivr.net/highlight.js/8.9.1/highlight.min.js" type="text/javascript"></script>
+    <script>
+      hljs.initHighlightingOnLoad();
+    </script>
+  </head>
+  <body>
+    <div class="container-fluid">
+      <div class="row">
+        <div class="col-md-2 col-sm-3">
+          <div class="sidebar-nav">
+            <div class="navbar navbar-default" role="navigation">
+              <div class="navbar-header">
+                <button ="button" class="navbar-toggle" data-target=".sidebar-navbar-collapse" data-toggle="collapse">
+                  <span class="sr-only">
+                    Toggle navigation
+                  </span>
+                  <span class="icon-bar"></span>
+                  <span class="icon-bar"></span>
+                  <span class="icon-bar"></span>
+                  <span class="icon-bar"></span>
+                </button>
+                <a ="#" class="visible-xs navbar-brand">
+                  <img alt="Weld Logo" src="/images/weld_logo_100x.png">
+                </a>
+              </div>
+              <div class="collapse navbar-collapse sidebar-navbar-collapse">
+                <ul class="nav navbar-nav">
+                  <li>
+                    <a href="/">
+                      <i class="fa fa-home"></i>
+                      &nbsp;Home
+                    </a>
+                  </li>
+                  <li>
+                    <a href="/download">
+                      <i class="fa fa-download"></i>
+                      &nbsp;Download
+                    </a>
+                  </li>
+                  <li>
+                    <a href="/news">
+                      <i class="fa fa-newspaper-o"></i>
+                      &nbsp;News
+                    </a>
+                  </li>
+                  <li>
+                    <a href="https://issues.jboss.org/projects/WELD?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page" target="_blank">
+                      <i class="fa fa-road"></i>
+                      &nbsp;Road Map
+                    </a>
+                  </li>
+                  <li>
+                    <a href="/documentation">
+                      <i class="fa fa-book"></i>
+                      &nbsp;Docs &amp; FAQ
+                    </a>
+                  </li>
+                  <li>
+                    <a href="/news/tags/tips">
+                      <i class="fa fa-lightbulb-o"></i>
+                      &nbsp;Tips and Tricks
+                    </a>
+                  </li>
+                  <li>
+                    <a href="/community">
+                      <i class="fa fa-group"></i>
+                      &nbsp;Community
+                    </a>
+                  </li>
+                  <li>
+                    <a href="http://github.com/weld" target="_blank">
+                      <i class="fa fa-github-alt"></i>
+                      &nbsp;Source Code
+                    </a>
+                  </li>
+                  <li>
+                    <a href="https://issues.jboss.org/browse/WELD#selectedTab=com.atlassian.jira.plugin.system.project%3Asummary-panel" target="_blank">
+                      <i class="fa fa-tasks"></i>
+                      &nbsp;Bug Tracker
+                    </a>
+                  </li>
+                  <li>
+                    <a href="https://twitter.com/jbossweld" target="_blank">
+                      <i class="fa fa-twitter"></i>
+                      &nbsp;Follow @jbossweld
+                    </a>
+                  </li>
+                </ul>
+              </div>
+            </div>
+          </div>
+        </div>
+        <div class="col-md-10 col-sm-9">
+          <div class="row hidden-xs">
+            <div class="dropup">
+              <div id="ajbossproject">
+                A JBoss Project
+              </div>
+              <a class="tabnav-closed" href="#" id="tab">Red Hat</a>
+              <script>
+                window.addEventListener('load', function() {renderTabzilla("Weld", "weld", false )}, false);
+              </script>
+            </div>
+          </div>
+          <div class="row">
+            <div class="col-md-4">
+              <a href="/">
+                <img alt="Weld Logo" class="hidden-xs weld-home-logo" src="/images/weld_logo_450x.png">
+              </a>
+            </div>
+            <div class="col-md-8">
+              <img alt="CDI tagcloud" class="hidden-xs hidden-sm cdi-background" src="/images/CDIbackground.png">
+            </div>
+          </div>
+          <div class="row content-wrapper">
+            <div class="col-md-12">
+              <div class="post">
+                <h1>
+                  Weld 6.0.0.Alpha1
+                  <a href="http://weld.cdi-spec.org/news.atom" title="Subscribe to Weld news">
+                    <i class="fa fa-rss"></i>
+                  </a>
+                </h1>
+                <div class="news-date news-boxed">
+                  2023-10-26
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/release">release</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Matej Novotny
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>Looking for a CDI 4.1 implementation? We&#8217;ve got you covered!
+                  Weld Core 6.0.0.Alpha1 is now available and comes along with CDI API 4.1.0.Alpha1.
+                  Note that this version also uses latest version (2.2.0-RC1) of the Jakarta Interceptors specification.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>CDI/CDI TCK related additions:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Create first implementation of CDI method invokers using <code>MethodHandles</code> (<a href="https://issues.redhat.com/browse/WELD-2764">WELD-2764</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>If you want to read up more about the original CDI API design and PR, take a look (<a href="https://github.com/jakartaee/cdi/pull/639">here</a>)</p>
+                  </li>
+                  <li>
+                  <p>Note that this feature is still being improved on both, CDI side and (<a href="https://issues.redhat.com/browse/WELD-2765">Weld side</a>) but the general shape of it is already carved out</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Support standardized means of getting interceptor bindings from <code>InvocationContext</code> (<a href="https://issues.redhat.com/browse/WELD-2756">WELD-2756</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>This was already possible via set of methods in <code>WeldInvocationContext</code> as well as the <code>String</code> key under which we stored these bindings in <code>InvocationContext</code></p>
+                  </li>
+                  <li>
+                  <p>Both of the above are no deprecated (but still working) and users are expected to use the standardized approach</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Support inspectable <code>CreationalContext</code> and <code>Contextual</code> in CDI TCK SPI (<a href="https://issues.redhat.com/browse/WELD-2757">WELD-2757</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>Other bugfixes and project QoL features:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Fix proxy creation for beans using <code>@Typed</code> and having package-protected types split across packages (<a href="https://issues.redhat.com/browse/WELD-2758">WELD-2758</a>)</p>
+                  </li>
+                  <li>
+                  <p>Correct how we determine proxy package for beans with unassignable types in their bean type set (<a href="https://issues.redhat.com/browse/WELD-2763">WELD-2763</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>This  was only problematic in environments using <code>WeldDefaultProxyServices</code> to define their proxies (such as Weld SE)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p><code>WeldManager#getContexts</code> now correctly returns an empty set when there are no contexts for given scope (<a href="https://issues.redhat.com/browse/WELD-2761">WELD-2761</a>)</p>
+                  </li>
+                  <li>
+                  <p>Fix possible memory leak with repetitive thread group creation (<a href="https://issues.redhat.com/browse/WELD-2755">WELD-2755</a>)</p>
+                  </li>
+                  <li>
+                  <p><code>WeldInitialListener</code> can no longer throw NPE is application fails to start (<a href="https://issues.redhat.com/browse/WELD-2752">WELD-2752</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Only possible in some EE containers on repeated re-deployment of Weld applications</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p><code>LazySessionBeanStore</code> no longer swallows exceptions happening when attempting to initiate HTTP session (<a href="https://issues.redhat.com/browse/WELD-2762">WELD-2762</a>)</p>
+                  </li>
+                  <li>
+                  <p>Weld Core and Weld API are now using formatter plugin and impsort instead of checkstyle (<a href="https://issues.redhat.com/browse/WELD-2753">WELD-2753</a>)</p>
+                  </li>
+                  <li>
+                  <p>Jandex version was bumped to 3.x across the project (<a href="https://issues.redhat.com/browse/WELD-2754">WELD-2754</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>As always, if you find further issues with Weld 6, let us know and we&#8217;ll try to help.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="/download/">Download</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/6.0.0.Alpha1/en-US/html_single/" target="_blank" rel="noopener">Documentation</a> &#93;
+                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12413485" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                </div>
+                
+                            <div id="disqus_thread"></div>
+                            <script type="text/javascript">
+                            var disqus_shortname = 'weld-cdi';
+                            var disqus_url = "https://weld.cdi-spec.org/news/2023/10/26/weld-600Alpha1/";
+                            var disqus_developer = null;
+                            var disqus_identifier = "bff4c754b4ad6171249a58298557386fd128f500";
+                            (function() {
+                              var dsq = document.createElement("script"); dsq.type = "text/javascript"; dsq.async = true;
+                              dsq.src = '//' + disqus_shortname + '.disqus.com/embed.js';
+                              (document.getElementsByTagName("head")[0] || document.getElementsByTagName("body")[0]).appendChild(dsq);
+                            })();
+                            </script>
+                            <noscript>Please enable JavaScript to view the <a href="http://disqus.com/?ref_noscript=weld-cdi">comments powered by Disqus.</a></noscript>
+              </div>
+            </div>
+          </div>
+        </div>
+      </div>
+    </div>
+    <footer>
+      <div class="row">
+        <div class="container" id="companyfooter">
+          <div class="redhatlogo" style="text-align:center;">
+            <div class="logospacer" style="height:10px;"></div>
+            <a href="http://www.redhat.com/">
+              <img src="https://static.jboss.org/theme/images/common/redhat_logo.png">
+            </a>
+          </div>
+        </div>
+      </div>
+    </footer>
+  </body>
+  <script src="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.5/js/bootstrap.min.js" type="text/javascript"></script>
+  <script type="text/javascript">
+  var _gaq = _gaq || [];
+  _gaq.push(['_setAccount','UA-45187401-1']);
+  _gaq.push(['_trackPageview']);
+  (function() {
+   var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
+   ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
+   var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
+  })();
+  </script>
+  <script>
+    $(document).ready(function() {
+      $('#toggle_menu').click(function(){
+        $("#mobile_menu").toggle();
+      });
+    });
+  </script>
+</html>
diff --git a/news/index.html b/news/index.html
index fcf1ccda..b1c790f5 100644
--- a/news/index.html
+++ b/news/index.html
@@ -141,6 +141,120 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2023/10/26/weld-600Alpha1/">Weld 6.0.0.Alpha1</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2023-10-26
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/release">release</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Matej Novotny
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>Looking for a CDI 4.1 implementation? We&#8217;ve got you covered!
+                  Weld Core 6.0.0.Alpha1 is now available and comes along with CDI API 4.1.0.Alpha1.
+                  Note that this version also uses latest version (2.2.0-RC1) of the Jakarta Interceptors specification.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>CDI/CDI TCK related additions:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Create first implementation of CDI method invokers using <code>MethodHandles</code> (<a href="https://issues.redhat.com/browse/WELD-2764">WELD-2764</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>If you want to read up more about the original CDI API design and PR, take a look (<a href="https://github.com/jakartaee/cdi/pull/639">here</a>)</p>
+                  </li>
+                  <li>
+                  <p>Note that this feature is still being improved on both, CDI side and (<a href="https://issues.redhat.com/browse/WELD-2765">Weld side</a>) but the general shape of it is already carved out</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Support standardized means of getting interceptor bindings from <code>InvocationContext</code> (<a href="https://issues.redhat.com/browse/WELD-2756">WELD-2756</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>This was already possible via set of methods in <code>WeldInvocationContext</code> as well as the <code>String</code> key under which we stored these bindings in <code>InvocationContext</code></p>
+                  </li>
+                  <li>
+                  <p>Both of the above are no deprecated (but still working) and users are expected to use the standardized approach</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Support inspectable <code>CreationalContext</code> and <code>Contextual</code> in CDI TCK SPI (<a href="https://issues.redhat.com/browse/WELD-2757">WELD-2757</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>Other bugfixes and project QoL features:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Fix proxy creation for beans using <code>@Typed</code> and having package-protected types split across packages (<a href="https://issues.redhat.com/browse/WELD-2758">WELD-2758</a>)</p>
+                  </li>
+                  <li>
+                  <p>Correct how we determine proxy package for beans with unassignable types in their bean type set (<a href="https://issues.redhat.com/browse/WELD-2763">WELD-2763</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>This  was only problematic in environments using <code>WeldDefaultProxyServices</code> to define their proxies (such as Weld SE)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p><code>WeldManager#getContexts</code> now correctly returns an empty set when there are no contexts for given scope (<a href="https://issues.redhat.com/browse/WELD-2761">WELD-2761</a>)</p>
+                  </li>
+                  <li>
+                  <p>Fix possible memory leak with repetitive thread group creation (<a href="https://issues.redhat.com/browse/WELD-2755">WELD-2755</a>)</p>
+                  </li>
+                  <li>
+                  <p><code>WeldInitialListener</code> can no longer throw NPE is application fails to start (<a href="https://issues.redhat.com/browse/WELD-2752">WELD-2752</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Only possible in some EE containers on repeated re-deployment of Weld applications</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p><code>LazySessionBeanStore</code> no longer swallows exceptions happening when attempting to initiate HTTP session (<a href="https://issues.redhat.com/browse/WELD-2762">WELD-2762</a>)</p>
+                  </li>
+                  <li>
+                  <p>Weld Core and Weld API are now using formatter plugin and impsort instead of checkstyle (<a href="https://issues.redhat.com/browse/WELD-2753">WELD-2753</a>)</p>
+                  </li>
+                  <li>
+                  <p>Jandex version was bumped to 3.x across the project (<a href="https://issues.redhat.com/browse/WELD-2754">WELD-2754</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>As always, if you find further issues with Weld 6, let us know and we&#8217;ll try to help.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="/download/">Download</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/6.0.0.Alpha1/en-US/html_single/" target="_blank" rel="noopener">Documentation</a> &#93;
+                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12413485" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2023/10/05/weld-512Final/">Weld 5.1.2.Final</a>
@@ -351,94 +465,6 @@ <h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2022/10/03/weld-510Final/">Weld 5.1.0.Final</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2022-10-3
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/release">release</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Matej Novotny
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>Weld Core 5.1.0.Final and Weld API 5.0.SP3 are now availabe in Maven Central.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Most notable change, which is also the cause of a minor version bump, is the removal of Weld Probe from our codebase.
-                  Details are in <a href="https://issues.redhat.com/browse/WELD-2733" target=""_blank)">this JIRA issue</a> and were also communicated via <a href="https://lists.jboss.org/archives/list/weld-dev@lists.jboss.org/thread/I72EU5I746F4DESLSENJVZFAEFPHXJYV/" target=""_blank">weld-dev email</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>In short, Probe hasn&#8217;t been maintained for a long time and its UI part is using outdated libraries and would need to be completely re-written which is something that we opted not to do at the moment.
-                  The JIRA issue has more information as to how we could re-integrate it in the future if there is interest from the community.</p>
-                  </div>
-                  <div class="admonitionblock warning">
-                  <table>
-                  <tr>
-                  <td class="icon">
-                  <div class="title">Warning</div>
-                  </td>
-                  <td class="content">
-                  Probe removal affects any integrators that were using Probe up until now! This typically concerns EE integrators such as WildFly or Liberty.
-                  </td>
-                  </tr>
-                  </table>
-                  </div>
-                  <div class="paragraph">
-                  <p>As usual, here is a list of notable bugfixes in this version:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Made decorators more Groovy friendly (<a href="https://issues.jboss.org/browse/WELD-2713" target="_blank" rel="noopener">WELD-2713</a>)</p>
-                  </li>
-                  <li>
-                  <p>Updated Jandex and remove deprecated usages (<a href="https://issues.jboss.org/browse/WELD-2724" target="_blank" rel="noopener">WELD-2724</a>)</p>
-                  </li>
-                  <li>
-                  <p>Added tools to execute TCK lang model in EE container (using WildFly) (<a href="https://issues.jboss.org/browse/WELD-2725" target="_blank" rel="noopener">WELD-2725</a>)</p>
-                  </li>
-                  <li>
-                  <p>Introduced method to <code>WeldManager</code> which allows to obtain instances of all registered contexts regardless of whether they are active (<a href="https://issues.jboss.org/browse/WELD-2726" target="_blank" rel="noopener">WELD-2726</a>)</p>
-                  </li>
-                  <li>
-                  <p>Brought WildFly Arquillian dependency setup up to date and fix affected examples (<a href="https://issues.jboss.org/browse/WELD-2727" target="_blank" rel="noopener">WELD-2727</a>)</p>
-                  </li>
-                  <li>
-                  <p><code>AbstractResourceServices</code> in Weld API now correctly take into consideration lookup value of <code>@Resource</code> (<a href="https://issues.jboss.org/browse/WELD-2728" target="_blank" rel="noopener">WELD-2728</a>)</p>
-                  </li>
-                  <li>
-                  <p><code>AbstractResourceServices</code> now supports setter methods for <code>@Resource</code> where the name is defaulted (<a href="https://issues.jboss.org/browse/WELD-2732" target="_blank" rel="noopener">WELD-2732</a>)</p>
-                  </li>
-                  <li>
-                  <p>Corrected the implementation of <code>WeldExpressionFactory#equals</code> (<a href="https://issues.jboss.org/browse/WELD-2729" target="_blank" rel="noopener">WELD-2729</a>)</p>
-                  </li>
-                  <li>
-                  <p>Fixed <code>BeanManager</code> bean types to also include <code>BeanContainer</code> (<a href="https://issues.jboss.org/browse/WELD-2731" target="_blank" rel="noopener">WELD-2731</a>)</p>
-                  </li>
-                  <li>
-                  <p>Avoid logging information about non-bindings member when using <code>BeanManager#isQualifier</code> for annotations that aren&#8217;t qualifiers (<a href="https://issues.jboss.org/browse/WELD-2643" target="_blank" rel="noopener">WELD-2643</a>)</p>
-                  </li>
-                  <li>
-                  <p>Removal of Weld Probe (<a href="https://issues.jboss.org/browse/WELD-2733" target="_blank" rel="noopener">WELD-2733</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>&#91; <a href="/download/">Download</a> &#93;
-                  &#91; <a href="http://docs.jboss.org/weld/reference/5.1.0.Final/en-US/html_single/" target="_blank" rel="noopener">Documentation</a> &#93;
-                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12391030" target="_blank" rel="noopener">Release notes</a> &#93;</p>
-                  </div>
-                </div>
-                <hr>
-              </div>
               <div class="pagination-links"><span class="current-page">1</span> <a href="/news/page/2.html" class="page-link">2</a> <span class="skip">...</span><a href="/news/page/17.html" class="page-link">17</a> <a href="/news/page/18.html" class="page-link">18</a> <a href="/news/page/2.html" class="next-link">Next</a> </div>
               <hr>
               <div>
diff --git a/news/page/10.html b/news/page/10.html
index 68ece535..b693562c 100644
--- a/news/page/10.html
+++ b/news/page/10.html
@@ -141,6 +141,98 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2017/02/02/weld-242Final/">Weld 2.4.2.Final</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2017-2-2
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/release">release</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Martin Kouba
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>As you may know, CDI 2 (JSR 365) is in Public Review phase.
+                  That&#8217;s great news for early adopters.
+                  But for now, I am very pleased to announce another production-ready version of <strong>Weld 2.4</strong> (CDI 1.2).
+                  See also <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12332808" target="_blank" rel="noopener">the release details</a>.
+                  Thanks to everyone involved in this release!</p>
+                  </div>
+                  <div class="admonitionblock warning">
+                  <table>
+                  <tr>
+                  <td class="icon">
+                  <div class="title">Warning</div>
+                  </td>
+                  <td class="content">
+                  There is a <a href="https://issues.jboss.org/browse/WELD-2328" target="_blank" rel="noopener">regression</a> in Weld <strong>2.4.2.Final</strong>. The problem only occurs if a <a href="https://docs.oracle.com/javase/tutorial/essential/environment/security.html" target="_blank" rel="noopener">Security Manager</a> is used. However, users are encouraged to upgrade to <strong>2.4.2.SP1</strong> which contains a fix for the issue.
+                  </td>
+                  </tr>
+                  </table>
+                  </div>
+                  <div class="paragraph">
+                  <p>Notable fixes and improvements:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Added <strong>trimmed bean archives</strong> support (CDI 2.0, <a href="https://issues.jboss.org/browse/WELD-2314" target="_blank" rel="noopener">WELD-2314</a>)</p>
+                  </li>
+                  <li>
+                  <p>Fixed Weld SE and Weld Servlet cooperation (<a href="https://issues.jboss.org/browse/WELD-2260" target="_blank" rel="noopener">WELD-2260</a> and <a href="https://issues.jboss.org/browse/WELD-2262" target="_blank" rel="noopener">WELD-2262</a>)</p>
+                  </li>
+                  <li>
+                  <p>Fixed <code>ActivateRequestContextInterceptor</code> - align the priority with CDI 2.0, fire <code>@Initialized</code> and <code>@Destroyed</code> events (CDI 2.0, <a href="https://issues.jboss.org/browse/WELD-2281" target="_blank" rel="noopener">WELD-2281</a>)</p>
+                  </li>
+                  <li>
+                  <p>Fixed JDK9 build problems (<a href="https://issues.jboss.org/browse/WELD-2303" target="_blank" rel="noopener">WELD-2303</a> and <a href="https://issues.jboss.org/browse/WELD-2301" target="_blank" rel="noopener">WELD-2301</a>)</p>
+                  </li>
+                  <li>
+                  <p>Validation - allow to use CDI 2 rules when validating selected alternatives in <code>bean.xml</code> (<a href="https://issues.jboss.org/browse/WELD-2313" target="_blank" rel="noopener">WELD-2313</a>)</p>
+                  </li>
+                  <li>
+                  <p>Performance improvements in <code>javax.enterprise.inject.Instance</code> implementation (CDI 2.0, <a href="https://issues.jboss.org/browse/WELD-2323" target="_blank" rel="noopener">WELD-2323</a>)</p>
+                  </li>
+                  <li>
+                  <p>Illegal bean types ignored for a session bean (<a href="https://issues.jboss.org/browse/WELD-2315" target="_blank" rel="noopener">WELD-2315</a>)</p>
+                  </li>
+                  <li>
+                  <p>Dependency upgrade - <code>jboss-classfilewriter</code> to 1.2.1.Final (enables interception of default methods, see also <a href="https://issues.jboss.org/browse/WELD-2093" target="_blank" rel="noopener">WELD-2093</a>)</p>
+                  </li>
+                  <li>
+                  <p>Weld SE - addded useful methods from <code>SeContainerInitializer</code> (CDI 2.0, <a href="https://issues.jboss.org/browse/WELD-2316" target="_blank" rel="noopener">WELD-2316</a>)</p>
+                  </li>
+                  <li>
+                  <p>Probe development tool - extended bean archive info</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_wildfly_patch">WildFly Patch</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>As usual, a <a href="http://download.jboss.org/weld/2.4.2.Final/wildfly-10.1.0.Final-weld-2.4.2.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly</a> is available.
+                  This time the target platform is <strong>WildFly 10.1.0.Final</strong>.
+                  If you’re not familiar with patching WildFly, check the <a href="/documentation/#12">FAQ</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="http://docs.jboss.org/cdi/api/1.2/" target="_blank" rel="noopener">CDI 1.2 API</a> &#93;
+                  &#91; <a href="/download/">Download</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/2.4.0.Final/en-US/html/" target="_blank" rel="noopener">Documentation</a> &#93;
+                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12332808" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2017/02/01/tip4-testing/">Weld Tip 4 - Testing CDI/Weld apps</a>
@@ -548,307 +640,6 @@ <h2 id="_wildfly_patch">WildFly Patch</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2016/10/25/tip3-performance/">Weld Tip 3 - Boost performance of Weld apps</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2016-10-25
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/tips">tips</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Martin Kouba
-                </div>
-                <p></p>
-                <div class="content">
-                  <div id="toc" class="toc">
-                  <div id="toctitle" class="title">Contents</div>
-                  <ul class="sectlevel1">
-                  <li><a href="#_bootstrap">Bootstrap</a>
-                  <ul class="sectlevel2">
-                  <li><a href="#_discovery_mode">Discovery mode</a></li>
-                  <li><a href="#_extensions">Extensions</a></li>
-                  <li><a href="#jandex">Jandex</a></li>
-                  </ul>
-                  </li>
-                  <li><a href="#_runtime">Runtime</a>
-                  <ul class="sectlevel2">
-                  <li><a href="#_identify_problematic_components_easily">Identify problematic components easily</a></li>
-                  <li><a href="#_lazy_initialization_of_bean_instances">Lazy initialization of bean instances</a></li>
-                  <li><a href="#_drawbacks_of_dependent_pseudo_scope">Drawbacks of <code>@Dependent</code> pseudo-scope</a></li>
-                  <li><a href="#_mapping_cdi_contexts_to_http_requests">Mapping CDI contexts to HTTP requests</a></li>
-                  <li><a href="#_bean_identifier_index_optimization">Bean identifier index optimization</a></li>
-                  </ul>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>In this article we&#8217;re going to dive into various performance aspects of CDI applications.
-                  As you&#8217;ve probably noticed performance testing is sometimes tricky.
-                  First of all, it&#8217;s difficult to create a meaningful benchmark.
-                  One should understand the JVM specifics (the need for warmup, garbage collection, JVM settings, etc.) and also use appropriate tools (e.g. <a href="http://openjdk.java.net/projects/code-tools/jmh/" target="_blank" rel="noopener">JMH</a> for microbenchmarks) accordingly.
-                  But even that usually proves to be unsufficient.
-                  One should also run the test in a relevant context (data, load, etc.).
-                  Performance specialists also say that&#8217;s it&#8217;s good to avoid premature optimizations but keep performance aspects in mind when tuning the "final" code.
-                  But all these considerations are out of scope of this article.
-                  Let&#8217;s go through several areas where CDI affects the performance of your application and discuss the possibilities.</p>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_bootstrap">Bootstrap</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>During bootstrap the overhead of a framework should be minimal so that it does not <em>slow down</em> the application startup and also does not eat all the memory available.
-                  However, CDI needs to do all that magic behind the scenes - read annotations, build and validate metadata, etc.
-                  The following sections describe what could be done to minimize the impact.</p>
-                  </div>
-                  <div class="sect2">
-                  <h3 id="_discovery_mode">Discovery mode</h3>
-                  <div class="paragraph">
-                  <p>In CDI 1.0 there was only one <em>"discovery mode"</em>.
-                  How does it work?
-                  Simply put: find all bean archives (containing <code>beans.xml</code>), discover and process all the found classes (identify beans, etc.).
-                  Needless to say, this might be a performance problem for large applications with thousands of classes.
-                  In CDI 1.1+ we call this mode <code>all</code> and a bean archive with this mode is called <strong>EXPLICIT</strong>.
-                  Since CDI 1.1+ a new discovery mode - <code>annotated</code> - can be used.
-                  The difference is that if this mode is used only classes with a <a href="http://docs.jboss.org/cdi/spec/1.2/cdi-spec.html#bean_defining_annotations" target="_blank" rel="noopener">bean defining annotation</a> are considered.
-                  In other words, a component must be explicitly designated.
-                  A bean archive with this mode is called <strong>IMPLICIT</strong>.
-                  To make things a little bit more complicated, an implicit bean archive does not have to contain a <code>beans.xml</code> file at all.
-                  One class with a bean defining annotation or a session bean is enough.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Implicit bean archive has pros and cons:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p><span class="icon"><i class="fa fa-thumbs-o-up"></i></span> saves a lot of memory if an archive contains a lot of classes which should NOT become beans (the container does not have to store the metadata)</p>
-                  </li>
-                  <li>
-                  <p><span class="icon"><i class="fa fa-thumbs-o-up"></i></span> speeds up the bootstrap (the container does not have to process all the types, fire events like <code>ProcessBean</code>, etc.)</p>
-                  </li>
-                  <li>
-                  <p><span class="icon"><i class="fa fa-thumbs-down"></i></span> does not fire <code>ProcessAnnotatedType</code> for all types from the bean archive; this breaks some extensions (e.g. <code>MessageBundleExtension</code> from DeltaSpike)</p>
-                  </li>
-                  <li>
-                  <p><span class="icon"><i class="fa fa-thumbs-down"></i></span> does not pick up <code>@javax.inject.Singleton</code> beans (it&#8217;s not a bean defining annotation)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p><strong>CONCLUSION</strong>: If possible, use the <code>annotated</code> discovery mode.</p>
-                  </div>
-                  <div class="admonitionblock tip">
-                  <table>
-                  <tr>
-                  <td class="icon">
-                  <i class="fa icon-tip" title="Tip"></i>
-                  </td>
-                  <td class="content">
-                  Most Weld-based runtimes allow to suppress implicit bean archives without <code>beans.xml</code>, i.e. to require the <code>beans.xml</code> file in bean archives so that it&#8217;s not necessary to scan all the parts of the application. See also <a href="/documentation/#4">FAQ</a>.
-                  </td>
-                  </tr>
-                  </table>
-                  </div>
-                  <div class="admonitionblock tip">
-                  <table>
-                  <tr>
-                  <td class="icon">
-                  <i class="fa icon-tip" title="Tip"></i>
-                  </td>
-                  <td class="content">
-                  If it&#8217;s not possible to use <code>annotated</code> mode, you can try a Weld-specific feature to conserve memory used: <a href="http://docs.jboss.org/weld/reference/latest/en-US/html/configure.html#veto-types-without-bean-defining-annotation" target="_blank" rel="noopener">Veto types without bean defining annotation</a>.
-                  A similar solution is going to be standardized in CDI 2.0 (see also <a href="https://issues.jboss.org/browse/CDI-420" target="_blank" rel="noopener">CDI-420</a>).
-                  </td>
-                  </tr>
-                  </table>
-                  </div>
-                  </div>
-                  <div class="sect2">
-                  <h3 id="_extensions">Extensions</h3>
-                  <div class="paragraph">
-                  <p>CDI portable extensions are essential integration points.
-                  And users love integrated technologies.
-                  However, the more extensions the more work must be done during bootstrap.
-                  For example, there is a <code>ProcessAnnotatedType</code> container lifecycle event.
-                  This event is fired:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>for every type in an EXPLICIT bean archive,</p>
-                  </li>
-                  <li>
-                  <p>for every session bean and every type with a bean defining annotation in an IMPLICIT bean archive.</p>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>The delivery might be restricted by means of type arguments, e.g. for observer <code>void observeNumbers(@Observes ProcessAnnotatedType&lt;? extends Number&gt; event)</code> an extension will be notified for every class assignable to <code>Number</code>.
-                  However, if you do <code>&lt;T&gt; void observe(@Observes ProcessAnnotatedType&lt;T&gt; event)</code> your extension will be notified for every class that is discovered.
-                  Now if we have an application with one EXPLICIT bean archive with 2000 classes, then a specific observer method on such extesion will be called 2000x.
-                  And if there are three similar extensions, the CDI container will have to create 2000 events and notify 6000 observers.
-                  This should be ok unless the observer logic is overly complex.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p><strong>CONCLUSION</strong>: Pay attention to extensions used in your application.
-                  If you wonder what extensions are in service, use for example Weld Probe observers view or fired events view together with <a href="http://docs.jboss.org/weld/reference/latest/en-US/html/configure.html#config-dev-mode" target="_blank" rel="noopener"><code>org.jboss.weld.probe.eventMonitor.containerLifecycleEvents</code> enabled</a>.</p>
-                  </div>
-                  <div class="admonitionblock tip">
-                  <table>
-                  <tr>
-                  <td class="icon">
-                  <i class="fa icon-tip" title="Tip"></i>
-                  </td>
-                  <td class="content">
-                  If possible, don&#8217;t use the extensions which observe all the annotated types from your application, i.e. which defined something like <code>void observe(@Observes ProcessAnnotatedType&lt;?&gt; event)</code>.
-                  Since CDI 1.1 <code>@WithAnnotations</code> should be used to restrict the set of types an extension is going to process. Weld Probe warns you about these extensions.
-                  </td>
-                  </tr>
-                  </table>
-                  </div>
-                  </div>
-                  <div class="sect2">
-                  <h3 id="jandex">Jandex</h3>
-                  <div class="paragraph">
-                  <p>In some environments (WildFly, Weld SE, and more) Weld can leverage an "offline reflection library", such as <a href="https://github.com/wildfly/jandex" target="<em>blank">Jandex</a>, to speed up the scanning process.
-                  These libraries allow to effectively filter classes <a href="http://docs.jboss.org/cdi/spec/1.2/cdi-spec.html#what_classes_are_beans" target="_blank" rel="noopener">which are not beans</a> and vetoed classes.
-                  It works like this: Jandex generates an index (scans the bytecode) and Weld is using this index to filter out useless classes.
-                  As a result Weld does not even have to _load the classes</em> or use <em>reflection API</em> to detect types which should be ignored.</p>
-                  </div>
-                  <div class="admonitionblock tip">
-                  <table>
-                  <tr>
-                  <td class="icon">
-                  <i class="fa icon-tip" title="Tip"></i>
-                  </td>
-                  <td class="content">
-                  In Weld SE and Servlet it’s also possible to generate the Jandex index beforehand, e.g. using the <a href="https://github.com/wildfly/jandex#user-content-using-the-ant-task-to-index-your-project" target="_blank" rel="noopener">Ant task</a>.
-                  </td>
-                  </tr>
-                  </table>
-                  </div>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_runtime">Runtime</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>In runtime the overhead of a framework should be minimal so that it&#8217;s not an application bottleneck.
-                  However, CDI needs to do all that magic behind the scenes - create bean instances, manage contexts, intercept and decorate invocations, etc.
-                  The following sections describe what could be done to minimize the impact.</p>
-                  </div>
-                  <div class="sect2">
-                  <h3 id="_identify_problematic_components_easily">Identify problematic components easily</h3>
-                  <div class="paragraph">
-                  <p>Before you start a profiler or a similar tool, it&#8217;s a good idea to identify all the CDI components involved in a problematic "request".
-                  This means all the beans, observer methods, interceptors and decorators.
-                  The good start might be the Weld Probe invocation trees view.
-                  An invocation tree shows all the business method invocations (including producers, disposers and observer methods).
-                  Once you spot a problematic component, you can check the business logic and associated interceptors and decorators.
-                  Sometimes profilers are just an overkill.</p>
-                  </div>
-                  </div>
-                  <div class="sect2">
-                  <h3 id="_lazy_initialization_of_bean_instances">Lazy initialization of bean instances</h3>
-                  <div class="paragraph">
-                  <p>Weld initializes bean instances of normal scoped beans lazily.
-                  In other words, when injecting a normal scoped bean (<code>@RequestScoped</code>, <code>@ApplicationScoped</code>, etc.) a new instance is not created until actually used.
-                  Instead, a shared client proxy is injected.
-                  This proxy invokes a method upon the correct bean instance (created if necessary).</p>
-                  </div>
-                  <div class="admonitionblock tip">
-                  <table>
-                  <tr>
-                  <td class="icon">
-                  <i class="fa icon-tip" title="Tip"></i>
-                  </td>
-                  <td class="content">
-                  Having many injection points resolving to normal scoped beans does not necessarily mean additional overhead associated with bean instance creation.
-                  </td>
-                  </tr>
-                  </table>
-                  </div>
-                  <div class="paragraph">
-                  <p>In the following example, an <code>OrderProcessor</code> instance is not created until its <code>OrderProcess.process()</code> method is called:</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@ApplicationScoped&#x000A;    class OrderProcessor {&#x000A;      @PostConstruct&#x000A;      void init() {&#x000A;        // Do some expensive initialization logic&#x000A;      }&#x000A;      void process() {&#x000A;        // Business logic&#x000A;      }&#x000A;    }&#x000A;    @RequestScoped&#x000A;    class OrderService {&#x000A;      @Inject&#x000A;      OrderProcessor processor; // A shared client proxy is injected&#x000A;    &#x000A;      void create(Order order) {&#x000A;        if (order.isValid()) {&#x000A;            // Processor is not initialized unless we have a valid order&#x000A;            processor.process(order);&#x000A;        }&#x000A;      }&#x000A;    }</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">
-                  Weld&#8217;s session context is also initilized lazily and doesn&#8217;t require an HTTP session to actually exist until a bean instance must be written (i.e. until a method of a <code>@SessionScoped</code> bean is invoked).
-                  </td>
-                  </tr>
-                  </table>
-                  </div>
-                  </div>
-                  <div class="sect2">
-                  <h3 id="_drawbacks_of_dependent_pseudo_scope">Drawbacks of <code>@Dependent</code> pseudo-scope</h3>
-                  <div class="paragraph">
-                  <p>From performance point of view <code>@Dependent</code> is NOT a best fit for:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p><span class="icon"><i class="fa fa-thumbs-down"></i></span> a bean that declares a producer which is frequently used (i.e. the produced bean is created very often)</p>
-                  </li>
-                  <li>
-                  <p><span class="icon"><i class="fa fa-thumbs-down"></i></span> a bean that declares an observer method which is frequently notified (i.e. the event is fired very often)</p>
-                  </li>
-                  <li>
-                  <p><span class="icon"><i class="fa fa-thumbs-down"></i></span> a bean which is used in EL expressions</p>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>For all these cases, a new <code>@Dependent</code> bean instance is created to handle the logic and destroyed when the invocation/evaluation completes.
-                  In other words, the bean instances are not reused.
-                  That&#8217;s not necessarily a problem if a bean does not have an "expensive" initialization or depends on others "heavyweight" components.
-                  But very often, a wider scope is more suitable.</p>
-                  </div>
-                  </div>
-                  <div class="sect2">
-                  <h3 id="_mapping_cdi_contexts_to_http_requests">Mapping CDI contexts to HTTP requests</h3>
-                  <div class="paragraph">
-                  <p>By default, bult-in CDI contexts are activated at the beginning of an HTTP request processing and deactivated once the processing finishes.
-                  This might be an unnecessary overhead in certain situations, e.g. when serving static resources (images, JavaScript, etc.).
-                  Weld allows to activate the contexts only for a subset of requests only.
-                  A regular expression may be used for filtering HTTP requests that should have contexts active during their processing.</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;web-app version="3.1" xmlns="http://xmlns.jcp.org/xml/ns/javaee/"&#x000A;        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"&#x000A;        xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee http://xmlns.jcp.org/xml/ns/javaee/web-app_3_1.xsd"&gt;&#x000A;        &lt;context-param&gt;&#x000A;            &lt;param-name&gt;org.jboss.weld.context.mapping&lt;/param-name&gt;&#x000A;            &lt;param-value&gt;.*\.html&lt;/param-value&gt; &lt;!-- Only activate contexts for resources with html suffix, e.g. /some/path.html --&gt;&#x000A;        &lt;/context-param&gt;&#x000A;    &lt;/web-app&gt;</code></pre>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect2">
-                  <h3 id="_bean_identifier_index_optimization">Bean identifier index optimization</h3>
-                  <div class="paragraph">
-                  <p>This optimization is used to <strong>reduce the HTTP session replication overhead</strong> (clustering use case).
-                  Simply put: Weld tries to minimize the amount of bytes send over the network.
-                  However, the inconsistency detection mechanism may cause problems in environments where application stop does not imply HTTP session destruction.
-                  Thus it&#8217;s disabled by default in Servlet containers.
-                  See also the <a href="http://docs.jboss.org/weld/reference/latest/en-US/html/configure.html#_bean_identifier_index_optimization">reference guide</a> for more info.</p>
-                  </div>
-                  </div>
-                  </div>
-                  </div>
-                </div>
-                <hr>
-              </div>
               <div class="pagination-links"><a href="/news/page/9.html" class="previous-link">Previous</a> <a href="/news/" class="page-link">1</a> <a href="/news/page/2.html" class="page-link">2</a> <span class="skip">...</span><a href="/news/page/9.html" class="page-link">9</a> <span class="current-page">10</span> <a href="/news/page/11.html" class="page-link">11</a> <span class="skip">...</span><a href="/news/page/17.html" class="page-link">17</a> <a href="/news/page/18.html" class="page-link">18</a> <a href="/news/page/11.html" class="next-link">Next</a> </div>
               <hr>
               <div>
diff --git a/news/page/11.html b/news/page/11.html
index 68e6f1a2..cac15876 100644
--- a/news/page/11.html
+++ b/news/page/11.html
@@ -141,6 +141,307 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2016/10/25/tip3-performance/">Weld Tip 3 - Boost performance of Weld apps</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2016-10-25
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/tips">tips</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Martin Kouba
+                </div>
+                <p></p>
+                <div class="content">
+                  <div id="toc" class="toc">
+                  <div id="toctitle" class="title">Contents</div>
+                  <ul class="sectlevel1">
+                  <li><a href="#_bootstrap">Bootstrap</a>
+                  <ul class="sectlevel2">
+                  <li><a href="#_discovery_mode">Discovery mode</a></li>
+                  <li><a href="#_extensions">Extensions</a></li>
+                  <li><a href="#jandex">Jandex</a></li>
+                  </ul>
+                  </li>
+                  <li><a href="#_runtime">Runtime</a>
+                  <ul class="sectlevel2">
+                  <li><a href="#_identify_problematic_components_easily">Identify problematic components easily</a></li>
+                  <li><a href="#_lazy_initialization_of_bean_instances">Lazy initialization of bean instances</a></li>
+                  <li><a href="#_drawbacks_of_dependent_pseudo_scope">Drawbacks of <code>@Dependent</code> pseudo-scope</a></li>
+                  <li><a href="#_mapping_cdi_contexts_to_http_requests">Mapping CDI contexts to HTTP requests</a></li>
+                  <li><a href="#_bean_identifier_index_optimization">Bean identifier index optimization</a></li>
+                  </ul>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>In this article we&#8217;re going to dive into various performance aspects of CDI applications.
+                  As you&#8217;ve probably noticed performance testing is sometimes tricky.
+                  First of all, it&#8217;s difficult to create a meaningful benchmark.
+                  One should understand the JVM specifics (the need for warmup, garbage collection, JVM settings, etc.) and also use appropriate tools (e.g. <a href="http://openjdk.java.net/projects/code-tools/jmh/" target="_blank" rel="noopener">JMH</a> for microbenchmarks) accordingly.
+                  But even that usually proves to be unsufficient.
+                  One should also run the test in a relevant context (data, load, etc.).
+                  Performance specialists also say that&#8217;s it&#8217;s good to avoid premature optimizations but keep performance aspects in mind when tuning the "final" code.
+                  But all these considerations are out of scope of this article.
+                  Let&#8217;s go through several areas where CDI affects the performance of your application and discuss the possibilities.</p>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_bootstrap">Bootstrap</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>During bootstrap the overhead of a framework should be minimal so that it does not <em>slow down</em> the application startup and also does not eat all the memory available.
+                  However, CDI needs to do all that magic behind the scenes - read annotations, build and validate metadata, etc.
+                  The following sections describe what could be done to minimize the impact.</p>
+                  </div>
+                  <div class="sect2">
+                  <h3 id="_discovery_mode">Discovery mode</h3>
+                  <div class="paragraph">
+                  <p>In CDI 1.0 there was only one <em>"discovery mode"</em>.
+                  How does it work?
+                  Simply put: find all bean archives (containing <code>beans.xml</code>), discover and process all the found classes (identify beans, etc.).
+                  Needless to say, this might be a performance problem for large applications with thousands of classes.
+                  In CDI 1.1+ we call this mode <code>all</code> and a bean archive with this mode is called <strong>EXPLICIT</strong>.
+                  Since CDI 1.1+ a new discovery mode - <code>annotated</code> - can be used.
+                  The difference is that if this mode is used only classes with a <a href="http://docs.jboss.org/cdi/spec/1.2/cdi-spec.html#bean_defining_annotations" target="_blank" rel="noopener">bean defining annotation</a> are considered.
+                  In other words, a component must be explicitly designated.
+                  A bean archive with this mode is called <strong>IMPLICIT</strong>.
+                  To make things a little bit more complicated, an implicit bean archive does not have to contain a <code>beans.xml</code> file at all.
+                  One class with a bean defining annotation or a session bean is enough.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Implicit bean archive has pros and cons:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p><span class="icon"><i class="fa fa-thumbs-o-up"></i></span> saves a lot of memory if an archive contains a lot of classes which should NOT become beans (the container does not have to store the metadata)</p>
+                  </li>
+                  <li>
+                  <p><span class="icon"><i class="fa fa-thumbs-o-up"></i></span> speeds up the bootstrap (the container does not have to process all the types, fire events like <code>ProcessBean</code>, etc.)</p>
+                  </li>
+                  <li>
+                  <p><span class="icon"><i class="fa fa-thumbs-down"></i></span> does not fire <code>ProcessAnnotatedType</code> for all types from the bean archive; this breaks some extensions (e.g. <code>MessageBundleExtension</code> from DeltaSpike)</p>
+                  </li>
+                  <li>
+                  <p><span class="icon"><i class="fa fa-thumbs-down"></i></span> does not pick up <code>@javax.inject.Singleton</code> beans (it&#8217;s not a bean defining annotation)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p><strong>CONCLUSION</strong>: If possible, use the <code>annotated</code> discovery mode.</p>
+                  </div>
+                  <div class="admonitionblock tip">
+                  <table>
+                  <tr>
+                  <td class="icon">
+                  <i class="fa icon-tip" title="Tip"></i>
+                  </td>
+                  <td class="content">
+                  Most Weld-based runtimes allow to suppress implicit bean archives without <code>beans.xml</code>, i.e. to require the <code>beans.xml</code> file in bean archives so that it&#8217;s not necessary to scan all the parts of the application. See also <a href="/documentation/#4">FAQ</a>.
+                  </td>
+                  </tr>
+                  </table>
+                  </div>
+                  <div class="admonitionblock tip">
+                  <table>
+                  <tr>
+                  <td class="icon">
+                  <i class="fa icon-tip" title="Tip"></i>
+                  </td>
+                  <td class="content">
+                  If it&#8217;s not possible to use <code>annotated</code> mode, you can try a Weld-specific feature to conserve memory used: <a href="http://docs.jboss.org/weld/reference/latest/en-US/html/configure.html#veto-types-without-bean-defining-annotation" target="_blank" rel="noopener">Veto types without bean defining annotation</a>.
+                  A similar solution is going to be standardized in CDI 2.0 (see also <a href="https://issues.jboss.org/browse/CDI-420" target="_blank" rel="noopener">CDI-420</a>).
+                  </td>
+                  </tr>
+                  </table>
+                  </div>
+                  </div>
+                  <div class="sect2">
+                  <h3 id="_extensions">Extensions</h3>
+                  <div class="paragraph">
+                  <p>CDI portable extensions are essential integration points.
+                  And users love integrated technologies.
+                  However, the more extensions the more work must be done during bootstrap.
+                  For example, there is a <code>ProcessAnnotatedType</code> container lifecycle event.
+                  This event is fired:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>for every type in an EXPLICIT bean archive,</p>
+                  </li>
+                  <li>
+                  <p>for every session bean and every type with a bean defining annotation in an IMPLICIT bean archive.</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>The delivery might be restricted by means of type arguments, e.g. for observer <code>void observeNumbers(@Observes ProcessAnnotatedType&lt;? extends Number&gt; event)</code> an extension will be notified for every class assignable to <code>Number</code>.
+                  However, if you do <code>&lt;T&gt; void observe(@Observes ProcessAnnotatedType&lt;T&gt; event)</code> your extension will be notified for every class that is discovered.
+                  Now if we have an application with one EXPLICIT bean archive with 2000 classes, then a specific observer method on such extesion will be called 2000x.
+                  And if there are three similar extensions, the CDI container will have to create 2000 events and notify 6000 observers.
+                  This should be ok unless the observer logic is overly complex.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p><strong>CONCLUSION</strong>: Pay attention to extensions used in your application.
+                  If you wonder what extensions are in service, use for example Weld Probe observers view or fired events view together with <a href="http://docs.jboss.org/weld/reference/latest/en-US/html/configure.html#config-dev-mode" target="_blank" rel="noopener"><code>org.jboss.weld.probe.eventMonitor.containerLifecycleEvents</code> enabled</a>.</p>
+                  </div>
+                  <div class="admonitionblock tip">
+                  <table>
+                  <tr>
+                  <td class="icon">
+                  <i class="fa icon-tip" title="Tip"></i>
+                  </td>
+                  <td class="content">
+                  If possible, don&#8217;t use the extensions which observe all the annotated types from your application, i.e. which defined something like <code>void observe(@Observes ProcessAnnotatedType&lt;?&gt; event)</code>.
+                  Since CDI 1.1 <code>@WithAnnotations</code> should be used to restrict the set of types an extension is going to process. Weld Probe warns you about these extensions.
+                  </td>
+                  </tr>
+                  </table>
+                  </div>
+                  </div>
+                  <div class="sect2">
+                  <h3 id="jandex">Jandex</h3>
+                  <div class="paragraph">
+                  <p>In some environments (WildFly, Weld SE, and more) Weld can leverage an "offline reflection library", such as <a href="https://github.com/wildfly/jandex" target="<em>blank">Jandex</a>, to speed up the scanning process.
+                  These libraries allow to effectively filter classes <a href="http://docs.jboss.org/cdi/spec/1.2/cdi-spec.html#what_classes_are_beans" target="_blank" rel="noopener">which are not beans</a> and vetoed classes.
+                  It works like this: Jandex generates an index (scans the bytecode) and Weld is using this index to filter out useless classes.
+                  As a result Weld does not even have to _load the classes</em> or use <em>reflection API</em> to detect types which should be ignored.</p>
+                  </div>
+                  <div class="admonitionblock tip">
+                  <table>
+                  <tr>
+                  <td class="icon">
+                  <i class="fa icon-tip" title="Tip"></i>
+                  </td>
+                  <td class="content">
+                  In Weld SE and Servlet it’s also possible to generate the Jandex index beforehand, e.g. using the <a href="https://github.com/wildfly/jandex#user-content-using-the-ant-task-to-index-your-project" target="_blank" rel="noopener">Ant task</a>.
+                  </td>
+                  </tr>
+                  </table>
+                  </div>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_runtime">Runtime</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>In runtime the overhead of a framework should be minimal so that it&#8217;s not an application bottleneck.
+                  However, CDI needs to do all that magic behind the scenes - create bean instances, manage contexts, intercept and decorate invocations, etc.
+                  The following sections describe what could be done to minimize the impact.</p>
+                  </div>
+                  <div class="sect2">
+                  <h3 id="_identify_problematic_components_easily">Identify problematic components easily</h3>
+                  <div class="paragraph">
+                  <p>Before you start a profiler or a similar tool, it&#8217;s a good idea to identify all the CDI components involved in a problematic "request".
+                  This means all the beans, observer methods, interceptors and decorators.
+                  The good start might be the Weld Probe invocation trees view.
+                  An invocation tree shows all the business method invocations (including producers, disposers and observer methods).
+                  Once you spot a problematic component, you can check the business logic and associated interceptors and decorators.
+                  Sometimes profilers are just an overkill.</p>
+                  </div>
+                  </div>
+                  <div class="sect2">
+                  <h3 id="_lazy_initialization_of_bean_instances">Lazy initialization of bean instances</h3>
+                  <div class="paragraph">
+                  <p>Weld initializes bean instances of normal scoped beans lazily.
+                  In other words, when injecting a normal scoped bean (<code>@RequestScoped</code>, <code>@ApplicationScoped</code>, etc.) a new instance is not created until actually used.
+                  Instead, a shared client proxy is injected.
+                  This proxy invokes a method upon the correct bean instance (created if necessary).</p>
+                  </div>
+                  <div class="admonitionblock tip">
+                  <table>
+                  <tr>
+                  <td class="icon">
+                  <i class="fa icon-tip" title="Tip"></i>
+                  </td>
+                  <td class="content">
+                  Having many injection points resolving to normal scoped beans does not necessarily mean additional overhead associated with bean instance creation.
+                  </td>
+                  </tr>
+                  </table>
+                  </div>
+                  <div class="paragraph">
+                  <p>In the following example, an <code>OrderProcessor</code> instance is not created until its <code>OrderProcess.process()</code> method is called:</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@ApplicationScoped&#x000A;    class OrderProcessor {&#x000A;      @PostConstruct&#x000A;      void init() {&#x000A;        // Do some expensive initialization logic&#x000A;      }&#x000A;      void process() {&#x000A;        // Business logic&#x000A;      }&#x000A;    }&#x000A;    @RequestScoped&#x000A;    class OrderService {&#x000A;      @Inject&#x000A;      OrderProcessor processor; // A shared client proxy is injected&#x000A;    &#x000A;      void create(Order order) {&#x000A;        if (order.isValid()) {&#x000A;            // Processor is not initialized unless we have a valid order&#x000A;            processor.process(order);&#x000A;        }&#x000A;      }&#x000A;    }</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">
+                  Weld&#8217;s session context is also initilized lazily and doesn&#8217;t require an HTTP session to actually exist until a bean instance must be written (i.e. until a method of a <code>@SessionScoped</code> bean is invoked).
+                  </td>
+                  </tr>
+                  </table>
+                  </div>
+                  </div>
+                  <div class="sect2">
+                  <h3 id="_drawbacks_of_dependent_pseudo_scope">Drawbacks of <code>@Dependent</code> pseudo-scope</h3>
+                  <div class="paragraph">
+                  <p>From performance point of view <code>@Dependent</code> is NOT a best fit for:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p><span class="icon"><i class="fa fa-thumbs-down"></i></span> a bean that declares a producer which is frequently used (i.e. the produced bean is created very often)</p>
+                  </li>
+                  <li>
+                  <p><span class="icon"><i class="fa fa-thumbs-down"></i></span> a bean that declares an observer method which is frequently notified (i.e. the event is fired very often)</p>
+                  </li>
+                  <li>
+                  <p><span class="icon"><i class="fa fa-thumbs-down"></i></span> a bean which is used in EL expressions</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>For all these cases, a new <code>@Dependent</code> bean instance is created to handle the logic and destroyed when the invocation/evaluation completes.
+                  In other words, the bean instances are not reused.
+                  That&#8217;s not necessarily a problem if a bean does not have an "expensive" initialization or depends on others "heavyweight" components.
+                  But very often, a wider scope is more suitable.</p>
+                  </div>
+                  </div>
+                  <div class="sect2">
+                  <h3 id="_mapping_cdi_contexts_to_http_requests">Mapping CDI contexts to HTTP requests</h3>
+                  <div class="paragraph">
+                  <p>By default, bult-in CDI contexts are activated at the beginning of an HTTP request processing and deactivated once the processing finishes.
+                  This might be an unnecessary overhead in certain situations, e.g. when serving static resources (images, JavaScript, etc.).
+                  Weld allows to activate the contexts only for a subset of requests only.
+                  A regular expression may be used for filtering HTTP requests that should have contexts active during their processing.</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;web-app version="3.1" xmlns="http://xmlns.jcp.org/xml/ns/javaee/"&#x000A;        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"&#x000A;        xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee http://xmlns.jcp.org/xml/ns/javaee/web-app_3_1.xsd"&gt;&#x000A;        &lt;context-param&gt;&#x000A;            &lt;param-name&gt;org.jboss.weld.context.mapping&lt;/param-name&gt;&#x000A;            &lt;param-value&gt;.*\.html&lt;/param-value&gt; &lt;!-- Only activate contexts for resources with html suffix, e.g. /some/path.html --&gt;&#x000A;        &lt;/context-param&gt;&#x000A;    &lt;/web-app&gt;</code></pre>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect2">
+                  <h3 id="_bean_identifier_index_optimization">Bean identifier index optimization</h3>
+                  <div class="paragraph">
+                  <p>This optimization is used to <strong>reduce the HTTP session replication overhead</strong> (clustering use case).
+                  Simply put: Weld tries to minimize the amount of bytes send over the network.
+                  However, the inconsistency detection mechanism may cause problems in environments where application stop does not imply HTTP session destruction.
+                  Thus it&#8217;s disabled by default in Servlet containers.
+                  See also the <a href="http://docs.jboss.org/weld/reference/latest/en-US/html/configure.html#_bean_identifier_index_optimization">reference guide</a> for more info.</p>
+                  </div>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2016/10/07/tip2-devmode/">Weld Tip 2 - Development Mode</a>
@@ -826,47 +1127,6 @@ <h2 id="_wildfly_patch">WildFly Patch</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2016/07/21/arq-container-weld-releasel/">Arquillian container Weld 2.0.0.Beta1 released!</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2016-7-21
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/arquillian">arquillian</a>
-                    ,
-                    <a href="/news/tags/testing">testing</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Tomas Remes
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>We are pleased to announce a release of embedded Arquillian container adapter for Weld.
-                  This container has deserved some love for really long time.
-                  We tried to refactor it and introduced new master branch which now corresponds to the 2.0.0.x version stream.
-                  The original master was branched in 1.0.
-                  There is no more any <code>arquillian-weld-ee-embedded-1.1</code> or <code>arquillian-weld-se-embedded</code>.
-                  It&#8217;s squashed to one <code>arquillian-weld-embedded</code> and you can configure environments either programmatically or using configuration properties.
-                  See link:https://github.com/arquillian/arquillian-container-weld
-                  This new version is going to be used in Weld as soon as possible.</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="title">Maven Coordinates:</div>
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">    &lt;dependency&gt;&#x000A;            &lt;groupId&gt;org.jboss.arquillian.container&lt;/groupId&gt;&#x000A;            &lt;artifactId&gt;arquillian-weld-embedded&lt;/artifactId&gt;&#x000A;            &lt;version&gt;2.0.0.Beta1&lt;/version&gt;&#x000A;        &lt;/dependency&gt;</code></pre>
-                  </div>
-                  </div>
-                  <div class="paragraph">
-                  <p>We would really appreciate if you can try it and let us know your experience!</p>
-                  </div>
-                </div>
-                <hr>
-              </div>
               <div class="pagination-links"><a href="/news/page/10.html" class="previous-link">Previous</a> <a href="/news/" class="page-link">1</a> <a href="/news/page/2.html" class="page-link">2</a> <span class="skip">...</span><a href="/news/page/10.html" class="page-link">10</a> <span class="current-page">11</span> <a href="/news/page/12.html" class="page-link">12</a> <span class="skip">...</span><a href="/news/page/17.html" class="page-link">17</a> <a href="/news/page/18.html" class="page-link">18</a> <a href="/news/page/12.html" class="next-link">Next</a> </div>
               <hr>
               <div>
diff --git a/news/page/12.html b/news/page/12.html
index b48ef863..5218955a 100644
--- a/news/page/12.html
+++ b/news/page/12.html
@@ -141,6 +141,47 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2016/07/21/arq-container-weld-releasel/">Arquillian container Weld 2.0.0.Beta1 released!</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2016-7-21
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/arquillian">arquillian</a>
+                    ,
+                    <a href="/news/tags/testing">testing</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Tomas Remes
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>We are pleased to announce a release of embedded Arquillian container adapter for Weld.
+                  This container has deserved some love for really long time.
+                  We tried to refactor it and introduced new master branch which now corresponds to the 2.0.0.x version stream.
+                  The original master was branched in 1.0.
+                  There is no more any <code>arquillian-weld-ee-embedded-1.1</code> or <code>arquillian-weld-se-embedded</code>.
+                  It&#8217;s squashed to one <code>arquillian-weld-embedded</code> and you can configure environments either programmatically or using configuration properties.
+                  See link:https://github.com/arquillian/arquillian-container-weld
+                  This new version is going to be used in Weld as soon as possible.</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="title">Maven Coordinates:</div>
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">    &lt;dependency&gt;&#x000A;            &lt;groupId&gt;org.jboss.arquillian.container&lt;/groupId&gt;&#x000A;            &lt;artifactId&gt;arquillian-weld-embedded&lt;/artifactId&gt;&#x000A;            &lt;version&gt;2.0.0.Beta1&lt;/version&gt;&#x000A;        &lt;/dependency&gt;</code></pre>
+                  </div>
+                  </div>
+                  <div class="paragraph">
+                  <p>We would really appreciate if you can try it and let us know your experience!</p>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2016/07/01/weld-235Final/">Weld 2.3.5.Final</a>
@@ -560,106 +601,6 @@ <h2 id="_wildfly_patch">WildFly Patch</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2016/04/22/weld-234Final/">Weld 2.3.4.Final</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2016-4-22
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/release">release</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Martin Kouba
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>Weld 2.3.4.Final the next version of the stable 2.3 branch has been released!
-                  See also <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12329779" target="_blank" rel="noopener">the release details</a>.
-                  Thanks to everyone involved in this release!</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Notable bugfixes and improvements:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>log important actions performed by extensions (<a href="https://issues.jboss.org/browse/WELD-2134" target="_blank" rel="noopener">WELD-2134</a>)</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>for example, if you want to track down all extensions modifying <code>AnnotatedType</code> definitions, then <a href="/documentation/#7" target="_blank" rel="noopener">enable the debug logging for Weld</a> and look for messages containing <code>ProcessAnnotatedType.setAnnotatedType() called by &#8230;&#8203;</code></p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Conversations - allow to configure the default timeout and the concurrent access timeout (<a href="https://issues.jboss.org/browse/WELD-2113" target="_blank" rel="noopener">WELD-2113</a>)</p>
-                  </li>
-                  <li>
-                  <p>recover if a transaction is in progress but a JTA Synchronization callback cannot be registered (<a href="https://issues.jboss.org/browse/WELD-2120" target="_blank" rel="noopener">WELD-2120</a>)</p>
-                  </li>
-                  <li>
-                  <p>EJB proxies do not implement private methods anymore (<a href="https://issues.jboss.org/browse/WELD-2119" target="_blank" rel="noopener">WELD-2119</a>)</p>
-                  </li>
-                  <li>
-                  <p>interceptor instances used for @AroundConstruct are now reused for other types of interception (<a href="https://issues.jboss.org/browse/WELD-2131" target="_blank" rel="noopener">WELD-2131</a>)</p>
-                  </li>
-                  <li>
-                  <p>Weld Servlet</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>fixed handling of archives from <code>WEB-INF/lib</code> on Tomcat 8 with <code>unpackWARs=false</code> (<a href="https://issues.jboss.org/browse/WELD-2122" target="_blank" rel="noopener">WELD-2122</a>)</p>
-                  </li>
-                  <li>
-                  <p><code>WeldTerminalListener</code> should not throw NPE if injection into listeners is not supported (<a href="https://issues.jboss.org/browse/WELD-2123" target="_blank" rel="noopener">WELD-2123</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Weld SE</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>improved support of <a href="http://docs.jboss.org/weld/reference/2.3.4.Final/en-US/html/environments.html#_implicit_bean_archive_support_2">implicit bean archives</a> (<a href="https://issues.jboss.org/browse/WELD-2129" target="_blank" rel="noopener">WELD-2129</a>)</p>
-                  </li>
-                  <li>
-                  <p>there are two new built-in interceptor bindings - <code>@ActivateRequestScope</code> and <code>@ActivateThreadScope</code> - to activate the <a href="http://docs.jboss.org/weld/reference/2.3.4.Final/en-US/html/environments.html#_request_context" target="_blank" rel="noopener">request scope</a> or the <a href="http://docs.jboss.org/weld/reference/2.3.4.Final/en-US/html/environments.html#_thread_context" target="_blank" rel="noopener">thread scope</a> within a business method invocation</p>
-                  </li>
-                  <li>
-                  <p>Weld builder allows to configure bean archive isolation, development mode and registration of shutdown hook manually (<a href="https://issues.jboss.org/browse/WELD-2135" target="_blank" rel="noopener">WELD-2135</a>)</p>
-                  </li>
-                  <li>
-                  <p>a basic nested archive support was added (<a href="https://issues.jboss.org/browse/WELD-1930" target="_blank" rel="noopener">WELD-1930</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_wildfly_patch">WildFly Patch</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>As usual, a <a href="http://download.jboss.org/weld/2.3.4.Final/wildfly-10.0.0.Final-weld-2.3.4.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly</a> is available. This time the target platform is <strong>WildFly 10.0.0.Final</strong>.  If you’re not familiar with patching WildFly, check <a href="http://blog.eisele.net/2015/02/playing-with-weld-probe-see-all-of-your.html" target="_blank" rel="noopener">Markus&#8217;s tutorial</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>&#91; <a href="http://docs.jboss.org/cdi/api/1.2/" target="_blank" rel="noopener">CDI 1.2 API</a> &#93;
-                  &#91; <a href="/download/">Download</a> &#93;
-                  &#91; <a href="http://docs.jboss.org/weld/reference/2.3.4.Final/en-US/html/" target="_blank" rel="noopener">Documentation</a> &#93;
-                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12329779" target="_blank" rel="noopener">Release notes</a> &#93;</p>
-                  </div>
-                  </div>
-                  </div>
-                </div>
-                <hr>
-              </div>
               <div class="pagination-links"><a href="/news/page/11.html" class="previous-link">Previous</a> <a href="/news/" class="page-link">1</a> <a href="/news/page/2.html" class="page-link">2</a> <span class="skip">...</span><a href="/news/page/11.html" class="page-link">11</a> <span class="current-page">12</span> <a href="/news/page/13.html" class="page-link">13</a> <span class="skip">...</span><a href="/news/page/17.html" class="page-link">17</a> <a href="/news/page/18.html" class="page-link">18</a> <a href="/news/page/13.html" class="next-link">Next</a> </div>
               <hr>
               <div>
diff --git a/news/page/13.html b/news/page/13.html
index 2913b69a..04f89174 100644
--- a/news/page/13.html
+++ b/news/page/13.html
@@ -141,6 +141,106 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2016/04/22/weld-234Final/">Weld 2.3.4.Final</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2016-4-22
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/release">release</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Martin Kouba
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>Weld 2.3.4.Final the next version of the stable 2.3 branch has been released!
+                  See also <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12329779" target="_blank" rel="noopener">the release details</a>.
+                  Thanks to everyone involved in this release!</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Notable bugfixes and improvements:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>log important actions performed by extensions (<a href="https://issues.jboss.org/browse/WELD-2134" target="_blank" rel="noopener">WELD-2134</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>for example, if you want to track down all extensions modifying <code>AnnotatedType</code> definitions, then <a href="/documentation/#7" target="_blank" rel="noopener">enable the debug logging for Weld</a> and look for messages containing <code>ProcessAnnotatedType.setAnnotatedType() called by &#8230;&#8203;</code></p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Conversations - allow to configure the default timeout and the concurrent access timeout (<a href="https://issues.jboss.org/browse/WELD-2113" target="_blank" rel="noopener">WELD-2113</a>)</p>
+                  </li>
+                  <li>
+                  <p>recover if a transaction is in progress but a JTA Synchronization callback cannot be registered (<a href="https://issues.jboss.org/browse/WELD-2120" target="_blank" rel="noopener">WELD-2120</a>)</p>
+                  </li>
+                  <li>
+                  <p>EJB proxies do not implement private methods anymore (<a href="https://issues.jboss.org/browse/WELD-2119" target="_blank" rel="noopener">WELD-2119</a>)</p>
+                  </li>
+                  <li>
+                  <p>interceptor instances used for @AroundConstruct are now reused for other types of interception (<a href="https://issues.jboss.org/browse/WELD-2131" target="_blank" rel="noopener">WELD-2131</a>)</p>
+                  </li>
+                  <li>
+                  <p>Weld Servlet</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>fixed handling of archives from <code>WEB-INF/lib</code> on Tomcat 8 with <code>unpackWARs=false</code> (<a href="https://issues.jboss.org/browse/WELD-2122" target="_blank" rel="noopener">WELD-2122</a>)</p>
+                  </li>
+                  <li>
+                  <p><code>WeldTerminalListener</code> should not throw NPE if injection into listeners is not supported (<a href="https://issues.jboss.org/browse/WELD-2123" target="_blank" rel="noopener">WELD-2123</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Weld SE</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>improved support of <a href="http://docs.jboss.org/weld/reference/2.3.4.Final/en-US/html/environments.html#_implicit_bean_archive_support_2">implicit bean archives</a> (<a href="https://issues.jboss.org/browse/WELD-2129" target="_blank" rel="noopener">WELD-2129</a>)</p>
+                  </li>
+                  <li>
+                  <p>there are two new built-in interceptor bindings - <code>@ActivateRequestScope</code> and <code>@ActivateThreadScope</code> - to activate the <a href="http://docs.jboss.org/weld/reference/2.3.4.Final/en-US/html/environments.html#_request_context" target="_blank" rel="noopener">request scope</a> or the <a href="http://docs.jboss.org/weld/reference/2.3.4.Final/en-US/html/environments.html#_thread_context" target="_blank" rel="noopener">thread scope</a> within a business method invocation</p>
+                  </li>
+                  <li>
+                  <p>Weld builder allows to configure bean archive isolation, development mode and registration of shutdown hook manually (<a href="https://issues.jboss.org/browse/WELD-2135" target="_blank" rel="noopener">WELD-2135</a>)</p>
+                  </li>
+                  <li>
+                  <p>a basic nested archive support was added (<a href="https://issues.jboss.org/browse/WELD-1930" target="_blank" rel="noopener">WELD-1930</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_wildfly_patch">WildFly Patch</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>As usual, a <a href="http://download.jboss.org/weld/2.3.4.Final/wildfly-10.0.0.Final-weld-2.3.4.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly</a> is available. This time the target platform is <strong>WildFly 10.0.0.Final</strong>.  If you’re not familiar with patching WildFly, check <a href="http://blog.eisele.net/2015/02/playing-with-weld-probe-see-all-of-your.html" target="_blank" rel="noopener">Markus&#8217;s tutorial</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="http://docs.jboss.org/cdi/api/1.2/" target="_blank" rel="noopener">CDI 1.2 API</a> &#93;
+                  &#91; <a href="/download/">Download</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/2.3.4.Final/en-US/html/" target="_blank" rel="noopener">Documentation</a> &#93;
+                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12329779" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2016/04/11/weld-meets-vertx/">Weld meets Vert.x</a>
@@ -437,72 +537,6 @@ <h2 id="_wildfly_patch">WildFly Patch</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2015/12/10/weld-232Final/">Weld 2.3.2.Final</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2015-12-10
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/release">release</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Martin Kouba
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>Weld 2.3.2.Final the last version for this year has been released! It is a bug-fixing release with 15 issues resolved. See also <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12328625">the release details</a>. Thanks to everyone involved in this release!</p>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_notable_bug_fixes_and_enhancements">Notable bug-fixes and enhancements</h2>
-                  <div class="sectionbody">
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Weld proxies - add workaround for IBM JVM 8 (<a href="https://issues.jboss.org/browse/WELD-2056">WELD-2056</a> and <a href="https://issues.apache.org/jira/browse/DELTASPIKE-1010">DELTASPIKE-1010</a>)</p>
-                  </li>
-                  <li>
-                  <p>Fix resource injection when using <code>arquillian-weld-ee-embedded-1.1</code> (<a href="https://issues.jboss.org/browse/WELD-2065">WELD-2065</a> and <a href="https://issues.jboss.org/browse/ARQ-2000">ARQ-2000</a>)</p>
-                  </li>
-                  <li>
-                  <p>All conversation contexts should be destroyed after the <code>Servlet.service()</code> method completes (<a href="https://issues.jboss.org/browse/WELD-2052">WELD-2052</a>)</p>
-                  </li>
-                  <li>
-                  <p>Clear <code>RequestScopedCache</code> for remote EJB calls (<a href="https://issues.jboss.org/browse/WELD-2069">WELD-2069</a>)</p>
-                  </li>
-                  <li>
-                  <p>Weld Servlet</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Allow to perform dependency injection upon objects not having a CDI-compatible constructor (<a href="https://issues.jboss.org/browse/WELD-2039">WELD-2039</a>)</p>
-                  </li>
-                  <li>
-                  <p>Add Jandex support even for WARs not extracted to the file system (<a href="https://issues.jboss.org/browse/WELD-2070">WELD-2070</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Probe development tool is now part of the OSGi bundle (<a href="https://issues.jboss.org/browse/WELD-2061">WELD-2061</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>&#91; <a href="http://docs.jboss.org/cdi/api/1.2/">CDI 1.2 API</a> &#93;
-                  &#91; <a href="/download/">Download</a> &#93;
-                  &#91; <a href="http://docs.jboss.org/weld/reference/2.3.2.Final/en-US/html/">Documentation</a> &#93;
-                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12328625">Release notes</a> &#93;</p>
-                  </div>
-                  </div>
-                  </div>
-                </div>
-                <hr>
-              </div>
               <div class="pagination-links"><a href="/news/page/12.html" class="previous-link">Previous</a> <a href="/news/" class="page-link">1</a> <a href="/news/page/2.html" class="page-link">2</a> <span class="skip">...</span><a href="/news/page/12.html" class="page-link">12</a> <span class="current-page">13</span> <a href="/news/page/14.html" class="page-link">14</a> <span class="skip">...</span><a href="/news/page/17.html" class="page-link">17</a> <a href="/news/page/18.html" class="page-link">18</a> <a href="/news/page/14.html" class="next-link">Next</a> </div>
               <hr>
               <div>
diff --git a/news/page/14.html b/news/page/14.html
index 898e023e..2af9207d 100644
--- a/news/page/14.html
+++ b/news/page/14.html
@@ -141,6 +141,72 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2015/12/10/weld-232Final/">Weld 2.3.2.Final</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2015-12-10
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/release">release</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Martin Kouba
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>Weld 2.3.2.Final the last version for this year has been released! It is a bug-fixing release with 15 issues resolved. See also <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12328625">the release details</a>. Thanks to everyone involved in this release!</p>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_notable_bug_fixes_and_enhancements">Notable bug-fixes and enhancements</h2>
+                  <div class="sectionbody">
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Weld proxies - add workaround for IBM JVM 8 (<a href="https://issues.jboss.org/browse/WELD-2056">WELD-2056</a> and <a href="https://issues.apache.org/jira/browse/DELTASPIKE-1010">DELTASPIKE-1010</a>)</p>
+                  </li>
+                  <li>
+                  <p>Fix resource injection when using <code>arquillian-weld-ee-embedded-1.1</code> (<a href="https://issues.jboss.org/browse/WELD-2065">WELD-2065</a> and <a href="https://issues.jboss.org/browse/ARQ-2000">ARQ-2000</a>)</p>
+                  </li>
+                  <li>
+                  <p>All conversation contexts should be destroyed after the <code>Servlet.service()</code> method completes (<a href="https://issues.jboss.org/browse/WELD-2052">WELD-2052</a>)</p>
+                  </li>
+                  <li>
+                  <p>Clear <code>RequestScopedCache</code> for remote EJB calls (<a href="https://issues.jboss.org/browse/WELD-2069">WELD-2069</a>)</p>
+                  </li>
+                  <li>
+                  <p>Weld Servlet</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Allow to perform dependency injection upon objects not having a CDI-compatible constructor (<a href="https://issues.jboss.org/browse/WELD-2039">WELD-2039</a>)</p>
+                  </li>
+                  <li>
+                  <p>Add Jandex support even for WARs not extracted to the file system (<a href="https://issues.jboss.org/browse/WELD-2070">WELD-2070</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Probe development tool is now part of the OSGi bundle (<a href="https://issues.jboss.org/browse/WELD-2061">WELD-2061</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="http://docs.jboss.org/cdi/api/1.2/">CDI 1.2 API</a> &#93;
+                  &#91; <a href="/download/">Download</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/2.3.2.Final/en-US/html/">Documentation</a> &#93;
+                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12328625">Release notes</a> &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2015/12/04/weld-300Alpha14/">Weld 3.0.0.Alpha14</a>
@@ -425,69 +491,6 @@ <h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2015/09/18/weld-230Final/">Weld 2.3.0.Final released!</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2015-9-18
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/release">release</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Martin Kouba
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>Weld 2.3.0.Final has been just released! From now on, 2.3 is the current stable version of Weld and 2.2 is not actively developed anymore - i.e. no new features are added, only bugs will be fixed. Weld 2.3 will remain a <strong>CDI 1.2</strong> implementation. We are incrementing the minor version due to several new features added. Weld 2.3 is also included in <a href="http://wildfly.org/">WildFly 10</a> application server.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Notable features and changes:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Java 6 support was dropped - Java 7 is the minimal requirement for building and running Weld 2.3</p>
-                  </li>
-                  <li>
-                  <p>Weld 2.3 comes with a special mode for application development, the <a href="http://docs.jboss.org/weld/reference/2.3.0.Final/en-US/html/devmode.html#probe">Probe development tool</a> allows to inspect application CDI components at runtime</p>
-                  </li>
-                  <li>
-                  <p>Weld SE Bootstrap API was enhanced in many ways - new features are mostly backported from <a href="http://weld.cdi-spec.org/news/2015/08/05/weld-300Alpha12/#_weld_se_bootstrap_api">Weld 3 development branch</a></p>
-                  </li>
-                  <li>
-                  <p>Weld Servlet now supports Undertow web server</p>
-                  </li>
-                  <li>
-                  <p>Revised delivery of <code>@Initialized</code>/<code>@Destroyed</code> events for <code>@ApplicationScoped</code> in an EAR (see also <a href="https://issues.jboss.org/browse/WELD-1821">WELD-1821</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>&#91; <a href="http://docs.jboss.org/cdi/api/1.2/">CDI 1.2 API</a> &#93;
-                  &#91; <a href="http://weld.cdi-spec.org/download/">Download</a> &#93;
-                  &#91; <a href="http://docs.jboss.org/weld/reference/2.3.0.Final/en-US/html/">Documentation</a> &#93;
-                  &#91; <a href="https://issues.jboss.org/projects/WELD/versions/12328057">Release notes</a> &#93;</p>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_weld_2_2_16_sp1">Weld 2.2.16.SP1</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>In addition, Weld 2.2.16.SP1 has been also released. It&#8217;s a bugfix release for 2.2 branch.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>&#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12327594">Weld 2.2.16.Final Release notes</a> &#93;
-                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12328216">Weld 2.2.16.SP1 Release notes</a> &#93;</p>
-                  </div>
-                  </div>
-                  </div>
-                </div>
-                <hr>
-              </div>
               <div class="pagination-links"><a href="/news/page/13.html" class="previous-link">Previous</a> <a href="/news/" class="page-link">1</a> <a href="/news/page/2.html" class="page-link">2</a> <span class="skip">...</span><a href="/news/page/13.html" class="page-link">13</a> <span class="current-page">14</span> <a href="/news/page/15.html" class="page-link">15</a> <span class="skip">...</span><a href="/news/page/17.html" class="page-link">17</a> <a href="/news/page/18.html" class="page-link">18</a> <a href="/news/page/15.html" class="next-link">Next</a> </div>
               <hr>
               <div>
diff --git a/news/page/15.html b/news/page/15.html
index 54009d5a..ba3e65b9 100644
--- a/news/page/15.html
+++ b/news/page/15.html
@@ -141,6 +141,69 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2015/09/18/weld-230Final/">Weld 2.3.0.Final released!</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2015-9-18
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/release">release</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Martin Kouba
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>Weld 2.3.0.Final has been just released! From now on, 2.3 is the current stable version of Weld and 2.2 is not actively developed anymore - i.e. no new features are added, only bugs will be fixed. Weld 2.3 will remain a <strong>CDI 1.2</strong> implementation. We are incrementing the minor version due to several new features added. Weld 2.3 is also included in <a href="http://wildfly.org/">WildFly 10</a> application server.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Notable features and changes:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Java 6 support was dropped - Java 7 is the minimal requirement for building and running Weld 2.3</p>
+                  </li>
+                  <li>
+                  <p>Weld 2.3 comes with a special mode for application development, the <a href="http://docs.jboss.org/weld/reference/2.3.0.Final/en-US/html/devmode.html#probe">Probe development tool</a> allows to inspect application CDI components at runtime</p>
+                  </li>
+                  <li>
+                  <p>Weld SE Bootstrap API was enhanced in many ways - new features are mostly backported from <a href="http://weld.cdi-spec.org/news/2015/08/05/weld-300Alpha12/#_weld_se_bootstrap_api">Weld 3 development branch</a></p>
+                  </li>
+                  <li>
+                  <p>Weld Servlet now supports Undertow web server</p>
+                  </li>
+                  <li>
+                  <p>Revised delivery of <code>@Initialized</code>/<code>@Destroyed</code> events for <code>@ApplicationScoped</code> in an EAR (see also <a href="https://issues.jboss.org/browse/WELD-1821">WELD-1821</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="http://docs.jboss.org/cdi/api/1.2/">CDI 1.2 API</a> &#93;
+                  &#91; <a href="http://weld.cdi-spec.org/download/">Download</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/2.3.0.Final/en-US/html/">Documentation</a> &#93;
+                  &#91; <a href="https://issues.jboss.org/projects/WELD/versions/12328057">Release notes</a> &#93;</p>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_weld_2_2_16_sp1">Weld 2.2.16.SP1</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>In addition, Weld 2.2.16.SP1 has been also released. It&#8217;s a bugfix release for 2.2 branch.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12327594">Weld 2.2.16.Final Release notes</a> &#93;
+                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12328216">Weld 2.2.16.SP1 Release notes</a> &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2015/09/15/jdk-8u60-problem/">JDK 8u60 reveals a problem in Weld</a>
@@ -587,141 +650,6 @@ <h2 id="_weld_probe_enhancements">Weld Probe Enhancements</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2015/02/25/weld-300Alpha5/">Weld 3.0.0.Alpha5</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2015-2-25
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/release">release</a>
-                    ,
-                    <a href="/news/tags/cdi2">cdi2</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Jozef Hartinger
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>Weld 3.0.0.Alpha5, the latest release in the series of CDI 2.0 prototypes, has been released.
-                  The highlights of the release include new Bean builder API and many improvements to Weld Probe.</p>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_bean_builder_api">Bean Builder API</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>The common way for frameworks and libraries to expose their API to applications via CDI is by using producer methods.
-                  An alternative approach is a custom implementation of the <code>javax.enterprise.inject.spi.Bean</code> interface that is registered by a CDI portable extension.
-                  This latter approach gives the extension more control but is also less straightforward.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>One of the goals of CDI 2.0 is to fill this gap and simplify extension development.
-                  This Weld release comes with a preview of the <a href="http://docs.jboss.org/weld/javadoc/3.0/weld-api/org/jboss/weld/experimental/BeanBuilder.html">Bean builder API</a>.
-                  The API is inspired by Bean builder
-                  <a href="http://deltaspike.apache.org/javadoc/1.2.1/org/apache/deltaspike/core/util/bean/BeanBuilder.html">API provided by DeltaSpike</a>.
-                  In addition, Java 8 lambdas are used in the API to simplify the entire process even further.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Here&#8217;s an example of a simple extension that builds and registers a bean:</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">void register(@Observes ExperimentalAfterBeanDiscovery event) {&#x000A;        event.addBean()&#x000A;            .addType(Integer.class)&#x000A;            .addQualifier(Random.LITERAL)&#x000A;            .produceWith(() -&gt; new java.util.Random().nextInt(1000));&#x000A;    }</code></pre>
-                  </div>
-                  </div>
-                  <div class="paragraph">
-                  <p>That&#8217;s it!
-                  Likewise, it is easy to can define a bean with custom disposal logic using a lambda expression:</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">void register(@Observes ExperimentalAfterBeanDiscovery event) {&#x000A;        event.addBean()&#x000A;            .addType(Connection.class)&#x000A;            .produceWith(this::newConnection)&#x000A;            .disposeWith(connection -&gt; connection.close());&#x000A;    }</code></pre>
-                  </div>
-                  </div>
-                  <div class="paragraph">
-                  <p>See the <a href="http://docs.jboss.org/weld/javadoc/3.0/weld-api/org/jboss/weld/experimental/BeanBuilder.html">BeanBuilder Javadoc</a> for more information.</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_event_monitoring_with_probe">Event monitoring with Probe</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>We introduced Probe in the <a href="http://weld.cdi-spec.org/news/2015/02/05/weld-300Alpha4/">previous blog post</a>.
-                  This release adds event monitoring view to Probe.
-                  In this view both system and application events are displayed.
-                  The events can be filtered by type and qualifiers.
-                  It is also possible to track which observer methods a particular event was delivered to.</p>
-                  </div>
-                  <div class="imageblock">
-                  <div class="content">
-                  <img src="/images/blog/probe-events.png" alt="Weld Probe event monitoring">
-                  </div>
-                  </div>
-                  <div class="sect2">
-                  <h3 id="_further_improvements">Further improvements</h3>
-                  <div class="paragraph">
-                  <p>In addition, there were a couple of minor improvements to Probe, namely:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>better filtering of invocation trees - Probe now searches the whole tree, not just the entry points</p>
-                  </li>
-                  <li>
-                  <p>the context view now displays the conversation context</p>
-                  </li>
-                  <li>
-                  <p>Probe is now more careful and does not try to bind interceptors to classes that are not proxyable</p>
-                  </li>
-                  <li>
-                  <p>all the configuration options for Probe are now <a href="http://docs.jboss.org/weld/reference/3.0.0.Alpha5/en-US/html/configure.html#config-dev-mode">documented</a></p>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>The easiest way to get Probe to run locally is to patch WildFly with a <a href="http://sourceforge.net/projects/jboss/files/Weld/3.0.0.Alpha5">Weld patch</a>.
-                  If you&#8217;re not familiar with patching WildFly, check <a href="http://blog.eisele.net/2015/02/playing-with-weld-probe-see-all-of-your.html">Markus&#8217;s tutorial</a>.</p>
-                  </div>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_relaxed_construction">Relaxed construction</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>CDI requires that beans that are normal-scoped, intercepted or decorated always define a no-argument constructor.
-                  This requirement applies even if the bean already defines an @Inject annotated constructor with parameters.
-                  This is purely a technical requirement implied by how Java allocates class instances.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Weld is however able to operate fine even if this requirement is not met.
-                  Weld uses special non-portable JVM APIs that allow it to allocate proxy instances without calling proxy’s constructor.
-                  This mode is non-portable and needs to be <a href="http://docs.jboss.org/weld/reference/3.0.0.Alpha5/en-US/html/configure.html#relaxedConstruction">explicitly enabled using a configuration option</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>This mode is not new but has been neglected in the past.
-                  For this release we added a bunch of tests for this mode, fixed a lot of bugs and enabled it by default in Weld-SE.
-                  Any feedback on this mode is appreciated.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>&#91; <a href="http://docs.jboss.org/weld/javadoc/3.0/weld-api/org/jboss/weld/experimental/package-frame.html">Experimental API documentation</a> &#93;
-                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12326167">Release notes</a> &#93;
-                  &#91; <a href="https://sourceforge.net/projects/jboss/files/Weld/3.0.0.Alpha5">Distribution</a> &#93;
-                  &#91; Patch for Wildfly
-                  (<a href="http://sourceforge.net/projects/jboss/files/Weld/3.0.0.Alpha5/wildfly-8.2.0.Final-weld-3.0.0.Alpha5-patch.zip/download">8.2</a>,
-                  <a href="http://sourceforge.net/projects/jboss/files/Weld/3.0.0.Alpha5/wildfly-9.0.0.Alpha1-weld-3.0.0.Alpha5-patch.zip/download">9 Alpha</a>)
-                  &#93;</p>
-                  </div>
-                  </div>
-                  </div>
-                </div>
-                <hr>
-              </div>
               <div class="pagination-links"><a href="/news/page/14.html" class="previous-link">Previous</a> <a href="/news/" class="page-link">1</a> <a href="/news/page/2.html" class="page-link">2</a> <span class="skip">...</span><a href="/news/page/14.html" class="page-link">14</a> <span class="current-page">15</span> <a href="/news/page/16.html" class="page-link">16</a> <a href="/news/page/17.html" class="page-link">17</a> <a href="/news/page/18.html" class="page-link">18</a> <a href="/news/page/16.html" class="next-link">Next</a> </div>
               <hr>
               <div>
diff --git a/news/page/16.html b/news/page/16.html
index a22f48fc..851ea3cb 100644
--- a/news/page/16.html
+++ b/news/page/16.html
@@ -141,6 +141,141 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2015/02/25/weld-300Alpha5/">Weld 3.0.0.Alpha5</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2015-2-25
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/release">release</a>
+                    ,
+                    <a href="/news/tags/cdi2">cdi2</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Jozef Hartinger
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>Weld 3.0.0.Alpha5, the latest release in the series of CDI 2.0 prototypes, has been released.
+                  The highlights of the release include new Bean builder API and many improvements to Weld Probe.</p>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_bean_builder_api">Bean Builder API</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>The common way for frameworks and libraries to expose their API to applications via CDI is by using producer methods.
+                  An alternative approach is a custom implementation of the <code>javax.enterprise.inject.spi.Bean</code> interface that is registered by a CDI portable extension.
+                  This latter approach gives the extension more control but is also less straightforward.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>One of the goals of CDI 2.0 is to fill this gap and simplify extension development.
+                  This Weld release comes with a preview of the <a href="http://docs.jboss.org/weld/javadoc/3.0/weld-api/org/jboss/weld/experimental/BeanBuilder.html">Bean builder API</a>.
+                  The API is inspired by Bean builder
+                  <a href="http://deltaspike.apache.org/javadoc/1.2.1/org/apache/deltaspike/core/util/bean/BeanBuilder.html">API provided by DeltaSpike</a>.
+                  In addition, Java 8 lambdas are used in the API to simplify the entire process even further.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Here&#8217;s an example of a simple extension that builds and registers a bean:</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">void register(@Observes ExperimentalAfterBeanDiscovery event) {&#x000A;        event.addBean()&#x000A;            .addType(Integer.class)&#x000A;            .addQualifier(Random.LITERAL)&#x000A;            .produceWith(() -&gt; new java.util.Random().nextInt(1000));&#x000A;    }</code></pre>
+                  </div>
+                  </div>
+                  <div class="paragraph">
+                  <p>That&#8217;s it!
+                  Likewise, it is easy to can define a bean with custom disposal logic using a lambda expression:</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">void register(@Observes ExperimentalAfterBeanDiscovery event) {&#x000A;        event.addBean()&#x000A;            .addType(Connection.class)&#x000A;            .produceWith(this::newConnection)&#x000A;            .disposeWith(connection -&gt; connection.close());&#x000A;    }</code></pre>
+                  </div>
+                  </div>
+                  <div class="paragraph">
+                  <p>See the <a href="http://docs.jboss.org/weld/javadoc/3.0/weld-api/org/jboss/weld/experimental/BeanBuilder.html">BeanBuilder Javadoc</a> for more information.</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_event_monitoring_with_probe">Event monitoring with Probe</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>We introduced Probe in the <a href="http://weld.cdi-spec.org/news/2015/02/05/weld-300Alpha4/">previous blog post</a>.
+                  This release adds event monitoring view to Probe.
+                  In this view both system and application events are displayed.
+                  The events can be filtered by type and qualifiers.
+                  It is also possible to track which observer methods a particular event was delivered to.</p>
+                  </div>
+                  <div class="imageblock">
+                  <div class="content">
+                  <img src="/images/blog/probe-events.png" alt="Weld Probe event monitoring">
+                  </div>
+                  </div>
+                  <div class="sect2">
+                  <h3 id="_further_improvements">Further improvements</h3>
+                  <div class="paragraph">
+                  <p>In addition, there were a couple of minor improvements to Probe, namely:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>better filtering of invocation trees - Probe now searches the whole tree, not just the entry points</p>
+                  </li>
+                  <li>
+                  <p>the context view now displays the conversation context</p>
+                  </li>
+                  <li>
+                  <p>Probe is now more careful and does not try to bind interceptors to classes that are not proxyable</p>
+                  </li>
+                  <li>
+                  <p>all the configuration options for Probe are now <a href="http://docs.jboss.org/weld/reference/3.0.0.Alpha5/en-US/html/configure.html#config-dev-mode">documented</a></p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>The easiest way to get Probe to run locally is to patch WildFly with a <a href="http://sourceforge.net/projects/jboss/files/Weld/3.0.0.Alpha5">Weld patch</a>.
+                  If you&#8217;re not familiar with patching WildFly, check <a href="http://blog.eisele.net/2015/02/playing-with-weld-probe-see-all-of-your.html">Markus&#8217;s tutorial</a>.</p>
+                  </div>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_relaxed_construction">Relaxed construction</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>CDI requires that beans that are normal-scoped, intercepted or decorated always define a no-argument constructor.
+                  This requirement applies even if the bean already defines an @Inject annotated constructor with parameters.
+                  This is purely a technical requirement implied by how Java allocates class instances.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Weld is however able to operate fine even if this requirement is not met.
+                  Weld uses special non-portable JVM APIs that allow it to allocate proxy instances without calling proxy’s constructor.
+                  This mode is non-portable and needs to be <a href="http://docs.jboss.org/weld/reference/3.0.0.Alpha5/en-US/html/configure.html#relaxedConstruction">explicitly enabled using a configuration option</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>This mode is not new but has been neglected in the past.
+                  For this release we added a bunch of tests for this mode, fixed a lot of bugs and enabled it by default in Weld-SE.
+                  Any feedback on this mode is appreciated.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="http://docs.jboss.org/weld/javadoc/3.0/weld-api/org/jboss/weld/experimental/package-frame.html">Experimental API documentation</a> &#93;
+                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12326167">Release notes</a> &#93;
+                  &#91; <a href="https://sourceforge.net/projects/jboss/files/Weld/3.0.0.Alpha5">Distribution</a> &#93;
+                  &#91; Patch for Wildfly
+                  (<a href="http://sourceforge.net/projects/jboss/files/Weld/3.0.0.Alpha5/wildfly-8.2.0.Final-weld-3.0.0.Alpha5-patch.zip/download">8.2</a>,
+                  <a href="http://sourceforge.net/projects/jboss/files/Weld/3.0.0.Alpha5/wildfly-9.0.0.Alpha1-weld-3.0.0.Alpha5-patch.zip/download">9 Alpha</a>)
+                  &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2015/02/05/weld-300Alpha4/">Weld 3.0.0.Alpha4</a>
@@ -815,165 +950,6 @@ <h2 id="_weld_3_0">Weld 3.0</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2014/04/15/weld-220-final/">Weld 2.2 (CDI 1.2 reference implementation) released!</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2014-4-15
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Jozef Hartinger
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>Today we released Weld 2.2.0.Final - the reference implementation of <a href="http://docs.jboss.org/cdi/spec/1.2/cdi-spec.html">Contexts and Dependency Injection for Java EE 1.2 (CDI 1.2)</a>.
-                  Besides implementing the changes in the specification, this release comes with several new features, performance improvements and more than 50 bug fixes.</p>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_cdi_1_2">CDI 1.2</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>CDI 1.2 is a maintenance release of the <a href="https://jcp.org/en/jsr/detail?id=346">CDI specification</a>. It contains a number of small fixes and clarifications as well as several enhancements.
-                  Most notable changes for application developers are related to the definition of <em>bean defining annotations</em>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>In <a href="http://docs.jboss.org/cdi/spec/1.2/cdi-spec.html#bean_defining_annotations">CDI 1.2</a>, the set of bean defining annotations now contains:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>all the normal scope annotations (e.g. @RequestScoped, @ApplicationScoped, &#8230;&#8203;)</p>
-                  </li>
-                  <li>
-                  <p>the built-in @Dependent scope</p>
-                  </li>
-                  <li>
-                  <p>@Interceptor and @Decorator annotations</p>
-                  </li>
-                  <li>
-                  <p>stereotype annotations</p>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>As a result, any class annotated with a <em>bean defining annotation</em> is by default recognized by the application server and registered as a CDI bean. The beans.xml file is optional.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>In addition, there are other fixes, clarifications and minor enhancements in this maintenance release of the CDI specification.
-                  See <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12311062&amp;version=12323655">the release notes</a> for the complete list of changes.</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_performance">Performance</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>Weld is now capable of using bytecode-scanning utilities, such as the <a href="https://github.com/wildfly/jandex">Jandex</a> tool, to speed up deployment.
-                  This is especially notable in extra large deployments (e.g. 5000+ classes) where we observed up to <strong>20% faster deployment</strong>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>In addition, there are noticeable improvements in the following areas:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>runtime performance of observers, interceptors and decorators</p>
-                  </li>
-                  <li>
-                  <p>session replication overhead (failover)</p>
-                  </li>
-                  <li>
-                  <p>memory consumption</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_weld_2_2_on_wildfly">Weld 2.2 on WildFly</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p><a href="http://wildfly.org">WildFly</a> does not come with Weld 2.2 support yet. It is however easy to patch an existing WildFly installation to use Weld 2.2.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>To do so, follow these steps:</p>
-                  </div>
-                  <div class="olist arabic">
-                  <ol class="arabic">
-                  <li>
-                  <p>Download a patch appropriate for the WildFly version (e.g. 8.0.0.Final) from the <a href="http://sourceforge.net/projects/jboss/files/Weld/2.2.0.Final/">download section</a></p>
-                  </li>
-                  <li>
-                  <p>In the WildFly installation, run the CLI console</p>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre>sh jboss-cli.sh</pre>
-                  </div>
-                  </div>
-                  </li>
-                  <li>
-                  <p>From the console run the following command:</p>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre>patch apply /path/to/wildfly-8.0.0.Final-weld-2.2.0.Final-patch.zip</pre>
-                  </div>
-                  </div>
-                  </li>
-                  </ol>
-                  </div>
-                  <div class="paragraph">
-                  <p>Your installation is now patched!</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_weld_se_and_servlet">Weld SE and Servlet</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>Weld comes with the SE module which allows CDI to be used in plain Java SE environment. In Weld 2.2 we added partial support for implicit bean archives.
-                  Partial support here means that the beans.xml file is still required, but <strong>bean-discovery-mode=”annotated”</strong> can be specified for Weld to only discover classes explicitly annotated with bean defining annotations (see above).</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>In addition to the Weld SE module, Weld also provides the Weld Servlet module which makes it possible to use Weld on top of a plain Servlet container, such as Apache Tomcat or Jetty.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>In this release we simplified configuration by bootstrapping Weld using the <em>ServletContainerInitializer</em>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Furthermore, Weld Servlet now supports <strong>Jetty 9.1</strong>. At the same time, the support for <strong>Tomcat 6 was dropped</strong>. To summarize, Weld Servlet is currently supported on the following Servlet containers:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Tomcat 7, 8</p>
-                  </li>
-                  <li>
-                  <p>Jetty 7, 8, 9.0, 9.1</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_acknowledgement">Acknowledgement</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>We greatly appreciate your contributions to this release.
-                  Big thanks go to: Martin Kouba, Matúš Abaffy, Matej Briškár, Ron Šmeral, Marek Schmidt, Marko Lukša, Tomáš Remeš, Stuart Douglas, Radoslav Husár, Max Pimm, Alexandre Gattiker, Antonin Stefanutti and Steve Moyer.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>&#91; <a href="http://docs.jboss.org/cdi/api/1.2/">CDI 1.2 API</a> &#93;
-                  &#91; <a href="http://weld.cdi-spec.org/download/">Download</a> &#93;
-                  &#91; <a href="http://docs.jboss.org/weld/reference/2.2.0.Final/en-US/html/">Documentation</a> &#93;
-                  &#91; <a href="https://issues.jboss.org/issues/?filter=12321473">Release notes</a> &#93;</p>
-                  </div>
-                  </div>
-                  </div>
-                </div>
-                <hr>
-              </div>
               <div class="pagination-links"><a href="/news/page/15.html" class="previous-link">Previous</a> <a href="/news/" class="page-link">1</a> <a href="/news/page/2.html" class="page-link">2</a> <span class="skip">...</span><a href="/news/page/15.html" class="page-link">15</a> <span class="current-page">16</span> <a href="/news/page/17.html" class="page-link">17</a> <a href="/news/page/18.html" class="page-link">18</a> <a href="/news/page/17.html" class="next-link">Next</a> </div>
               <hr>
               <div>
diff --git a/news/page/17.html b/news/page/17.html
index 41958cda..25fdaa8e 100644
--- a/news/page/17.html
+++ b/news/page/17.html
@@ -141,6 +141,165 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2014/04/15/weld-220-final/">Weld 2.2 (CDI 1.2 reference implementation) released!</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2014-4-15
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Jozef Hartinger
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>Today we released Weld 2.2.0.Final - the reference implementation of <a href="http://docs.jboss.org/cdi/spec/1.2/cdi-spec.html">Contexts and Dependency Injection for Java EE 1.2 (CDI 1.2)</a>.
+                  Besides implementing the changes in the specification, this release comes with several new features, performance improvements and more than 50 bug fixes.</p>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_cdi_1_2">CDI 1.2</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>CDI 1.2 is a maintenance release of the <a href="https://jcp.org/en/jsr/detail?id=346">CDI specification</a>. It contains a number of small fixes and clarifications as well as several enhancements.
+                  Most notable changes for application developers are related to the definition of <em>bean defining annotations</em>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>In <a href="http://docs.jboss.org/cdi/spec/1.2/cdi-spec.html#bean_defining_annotations">CDI 1.2</a>, the set of bean defining annotations now contains:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>all the normal scope annotations (e.g. @RequestScoped, @ApplicationScoped, &#8230;&#8203;)</p>
+                  </li>
+                  <li>
+                  <p>the built-in @Dependent scope</p>
+                  </li>
+                  <li>
+                  <p>@Interceptor and @Decorator annotations</p>
+                  </li>
+                  <li>
+                  <p>stereotype annotations</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>As a result, any class annotated with a <em>bean defining annotation</em> is by default recognized by the application server and registered as a CDI bean. The beans.xml file is optional.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>In addition, there are other fixes, clarifications and minor enhancements in this maintenance release of the CDI specification.
+                  See <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12311062&amp;version=12323655">the release notes</a> for the complete list of changes.</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_performance">Performance</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>Weld is now capable of using bytecode-scanning utilities, such as the <a href="https://github.com/wildfly/jandex">Jandex</a> tool, to speed up deployment.
+                  This is especially notable in extra large deployments (e.g. 5000+ classes) where we observed up to <strong>20% faster deployment</strong>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>In addition, there are noticeable improvements in the following areas:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>runtime performance of observers, interceptors and decorators</p>
+                  </li>
+                  <li>
+                  <p>session replication overhead (failover)</p>
+                  </li>
+                  <li>
+                  <p>memory consumption</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_weld_2_2_on_wildfly">Weld 2.2 on WildFly</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p><a href="http://wildfly.org">WildFly</a> does not come with Weld 2.2 support yet. It is however easy to patch an existing WildFly installation to use Weld 2.2.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>To do so, follow these steps:</p>
+                  </div>
+                  <div class="olist arabic">
+                  <ol class="arabic">
+                  <li>
+                  <p>Download a patch appropriate for the WildFly version (e.g. 8.0.0.Final) from the <a href="http://sourceforge.net/projects/jboss/files/Weld/2.2.0.Final/">download section</a></p>
+                  </li>
+                  <li>
+                  <p>In the WildFly installation, run the CLI console</p>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre>sh jboss-cli.sh</pre>
+                  </div>
+                  </div>
+                  </li>
+                  <li>
+                  <p>From the console run the following command:</p>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre>patch apply /path/to/wildfly-8.0.0.Final-weld-2.2.0.Final-patch.zip</pre>
+                  </div>
+                  </div>
+                  </li>
+                  </ol>
+                  </div>
+                  <div class="paragraph">
+                  <p>Your installation is now patched!</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_weld_se_and_servlet">Weld SE and Servlet</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>Weld comes with the SE module which allows CDI to be used in plain Java SE environment. In Weld 2.2 we added partial support for implicit bean archives.
+                  Partial support here means that the beans.xml file is still required, but <strong>bean-discovery-mode=”annotated”</strong> can be specified for Weld to only discover classes explicitly annotated with bean defining annotations (see above).</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>In addition to the Weld SE module, Weld also provides the Weld Servlet module which makes it possible to use Weld on top of a plain Servlet container, such as Apache Tomcat or Jetty.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>In this release we simplified configuration by bootstrapping Weld using the <em>ServletContainerInitializer</em>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Furthermore, Weld Servlet now supports <strong>Jetty 9.1</strong>. At the same time, the support for <strong>Tomcat 6 was dropped</strong>. To summarize, Weld Servlet is currently supported on the following Servlet containers:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Tomcat 7, 8</p>
+                  </li>
+                  <li>
+                  <p>Jetty 7, 8, 9.0, 9.1</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_acknowledgement">Acknowledgement</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>We greatly appreciate your contributions to this release.
+                  Big thanks go to: Martin Kouba, Matúš Abaffy, Matej Briškár, Ron Šmeral, Marek Schmidt, Marko Lukša, Tomáš Remeš, Stuart Douglas, Radoslav Husár, Max Pimm, Alexandre Gattiker, Antonin Stefanutti and Steve Moyer.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="http://docs.jboss.org/cdi/api/1.2/">CDI 1.2 API</a> &#93;
+                  &#91; <a href="http://weld.cdi-spec.org/download/">Download</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/2.2.0.Final/en-US/html/">Documentation</a> &#93;
+                  &#91; <a href="https://issues.jboss.org/issues/?filter=12321473">Release notes</a> &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2014/02/04/weld-220-alpha1/">CDI 1.2 and Weld 2.2</a>
@@ -397,24 +556,6 @@ <h2 id="_acknowledgement">Acknowledgement</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2013/09/20/weld-210beta2-tip/">Weld 2.1.0.Beta2 tip</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2013-9-20
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Martin Kouba
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>A tip how to configure a new feature introduced in Weld 2.1.0.Beta2 which allows to skip CDI context activation for some HTTP requests: <a href="http://goo.gl/PAiwBS" class="bare">http://goo.gl/PAiwBS</a></p>
-                  </div>
-                </div>
-                <hr>
-              </div>
               <div class="pagination-links"><a href="/news/page/16.html" class="previous-link">Previous</a> <a href="/news/" class="page-link">1</a> <a href="/news/page/2.html" class="page-link">2</a> <span class="skip">...</span><a href="/news/page/16.html" class="page-link">16</a> <span class="current-page">17</span> <a href="/news/page/18.html" class="page-link">18</a> <a href="/news/page/18.html" class="next-link">Next</a> </div>
               <hr>
               <div>
diff --git a/news/page/18.html b/news/page/18.html
index 79137bb0..d8bbef39 100644
--- a/news/page/18.html
+++ b/news/page/18.html
@@ -141,6 +141,24 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2013/09/20/weld-210beta2-tip/">Weld 2.1.0.Beta2 tip</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2013-9-20
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Martin Kouba
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>A tip how to configure a new feature introduced in Weld 2.1.0.Beta2 which allows to skip CDI context activation for some HTTP requests: <a href="http://goo.gl/PAiwBS" class="bare">http://goo.gl/PAiwBS</a></p>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2013/06/20/new-weld-site/">Weld has a new web site!</a>
diff --git a/news/page/2.html b/news/page/2.html
index c445fe57..6481690f 100644
--- a/news/page/2.html
+++ b/news/page/2.html
@@ -141,6 +141,94 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2022/10/03/weld-510Final/">Weld 5.1.0.Final</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2022-10-3
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/release">release</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Matej Novotny
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>Weld Core 5.1.0.Final and Weld API 5.0.SP3 are now availabe in Maven Central.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Most notable change, which is also the cause of a minor version bump, is the removal of Weld Probe from our codebase.
+                  Details are in <a href="https://issues.redhat.com/browse/WELD-2733" target=""_blank)">this JIRA issue</a> and were also communicated via <a href="https://lists.jboss.org/archives/list/weld-dev@lists.jboss.org/thread/I72EU5I746F4DESLSENJVZFAEFPHXJYV/" target=""_blank">weld-dev email</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>In short, Probe hasn&#8217;t been maintained for a long time and its UI part is using outdated libraries and would need to be completely re-written which is something that we opted not to do at the moment.
+                  The JIRA issue has more information as to how we could re-integrate it in the future if there is interest from the community.</p>
+                  </div>
+                  <div class="admonitionblock warning">
+                  <table>
+                  <tr>
+                  <td class="icon">
+                  <div class="title">Warning</div>
+                  </td>
+                  <td class="content">
+                  Probe removal affects any integrators that were using Probe up until now! This typically concerns EE integrators such as WildFly or Liberty.
+                  </td>
+                  </tr>
+                  </table>
+                  </div>
+                  <div class="paragraph">
+                  <p>As usual, here is a list of notable bugfixes in this version:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Made decorators more Groovy friendly (<a href="https://issues.jboss.org/browse/WELD-2713" target="_blank" rel="noopener">WELD-2713</a>)</p>
+                  </li>
+                  <li>
+                  <p>Updated Jandex and remove deprecated usages (<a href="https://issues.jboss.org/browse/WELD-2724" target="_blank" rel="noopener">WELD-2724</a>)</p>
+                  </li>
+                  <li>
+                  <p>Added tools to execute TCK lang model in EE container (using WildFly) (<a href="https://issues.jboss.org/browse/WELD-2725" target="_blank" rel="noopener">WELD-2725</a>)</p>
+                  </li>
+                  <li>
+                  <p>Introduced method to <code>WeldManager</code> which allows to obtain instances of all registered contexts regardless of whether they are active (<a href="https://issues.jboss.org/browse/WELD-2726" target="_blank" rel="noopener">WELD-2726</a>)</p>
+                  </li>
+                  <li>
+                  <p>Brought WildFly Arquillian dependency setup up to date and fix affected examples (<a href="https://issues.jboss.org/browse/WELD-2727" target="_blank" rel="noopener">WELD-2727</a>)</p>
+                  </li>
+                  <li>
+                  <p><code>AbstractResourceServices</code> in Weld API now correctly take into consideration lookup value of <code>@Resource</code> (<a href="https://issues.jboss.org/browse/WELD-2728" target="_blank" rel="noopener">WELD-2728</a>)</p>
+                  </li>
+                  <li>
+                  <p><code>AbstractResourceServices</code> now supports setter methods for <code>@Resource</code> where the name is defaulted (<a href="https://issues.jboss.org/browse/WELD-2732" target="_blank" rel="noopener">WELD-2732</a>)</p>
+                  </li>
+                  <li>
+                  <p>Corrected the implementation of <code>WeldExpressionFactory#equals</code> (<a href="https://issues.jboss.org/browse/WELD-2729" target="_blank" rel="noopener">WELD-2729</a>)</p>
+                  </li>
+                  <li>
+                  <p>Fixed <code>BeanManager</code> bean types to also include <code>BeanContainer</code> (<a href="https://issues.jboss.org/browse/WELD-2731" target="_blank" rel="noopener">WELD-2731</a>)</p>
+                  </li>
+                  <li>
+                  <p>Avoid logging information about non-bindings member when using <code>BeanManager#isQualifier</code> for annotations that aren&#8217;t qualifiers (<a href="https://issues.jboss.org/browse/WELD-2643" target="_blank" rel="noopener">WELD-2643</a>)</p>
+                  </li>
+                  <li>
+                  <p>Removal of Weld Probe (<a href="https://issues.jboss.org/browse/WELD-2733" target="_blank" rel="noopener">WELD-2733</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="/download/">Download</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/5.1.0.Final/en-US/html_single/" target="_blank" rel="noopener">Documentation</a> &#93;
+                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12391030" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2022/06/24/weld-501Final/">Weld 5.0.1.Final</a>
@@ -349,42 +437,6 @@ <h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2022/03/23/weld-500CR2/">Weld 5.0.0.CR2</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2022-3-23
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/release">release</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Matej Novotny
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>Final ballot of CDI 4 has uncovered untested and unimplemented area in the newly added <code>Startup</code> and <code>Shutdown</code> events.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Our previous release was guilty of not supporting this properly, hence here comes Weld API 5.0.CR2 and Weld Core 5.0.0.CR2.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Weld now automatically fires these events and the JIRA issue for this can be seen <a href="https://issues.jboss.org/browse/WELD-2709" target="_blank" rel="noopener">here (WELD-2709)</a>.
-                  However, integrators can choose to override this behavior and fire both events themselves in case there is more bootstrapping logic that needs to come together before the container is deemed ready.
-                  The API interface <a href="https://github.com/weld/api/blob/5.0.CR2/weld-spi/src/main/java/org/jboss/weld/bootstrap/api/Environment.java#L48-L70"><code>org.jboss.weld.bootstrap.api.Environment</code></a> allows implementors to override a specific method which will then prevent Weld from handling these events.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>&#91; <a href="/download/">Download</a> &#93;
-                  &#91; <a href="http://docs.jboss.org/weld/reference/5.0.0.CR2/en-US/html_single/" target="_blank" rel="noopener">Documentation</a> &#93;
-                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12382781" target="_blank" rel="noopener">Release notes</a> &#93;</p>
-                  </div>
-                </div>
-                <hr>
-              </div>
               <div class="pagination-links"><a href="/news/" class="previous-link">Previous</a> <a href="/news/" class="page-link">1</a> <span class="current-page">2</span> <a href="/news/page/3.html" class="page-link">3</a> <span class="skip">...</span><a href="/news/page/17.html" class="page-link">17</a> <a href="/news/page/18.html" class="page-link">18</a> <a href="/news/page/3.html" class="next-link">Next</a> </div>
               <hr>
               <div>
diff --git a/news/page/3.html b/news/page/3.html
index 05c56b70..aee51c97 100644
--- a/news/page/3.html
+++ b/news/page/3.html
@@ -141,6 +141,42 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2022/03/23/weld-500CR2/">Weld 5.0.0.CR2</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2022-3-23
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/release">release</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Matej Novotny
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>Final ballot of CDI 4 has uncovered untested and unimplemented area in the newly added <code>Startup</code> and <code>Shutdown</code> events.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Our previous release was guilty of not supporting this properly, hence here comes Weld API 5.0.CR2 and Weld Core 5.0.0.CR2.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Weld now automatically fires these events and the JIRA issue for this can be seen <a href="https://issues.jboss.org/browse/WELD-2709" target="_blank" rel="noopener">here (WELD-2709)</a>.
+                  However, integrators can choose to override this behavior and fire both events themselves in case there is more bootstrapping logic that needs to come together before the container is deemed ready.
+                  The API interface <a href="https://github.com/weld/api/blob/5.0.CR2/weld-spi/src/main/java/org/jboss/weld/bootstrap/api/Environment.java#L48-L70"><code>org.jboss.weld.bootstrap.api.Environment</code></a> allows implementors to override a specific method which will then prevent Weld from handling these events.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="/download/">Download</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/5.0.0.CR2/en-US/html_single/" target="_blank" rel="noopener">Documentation</a> &#93;
+                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12382781" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2022/02/23/weld-500CR1/">Weld 5.0.0.CR1</a>
@@ -635,67 +671,6 @@ <h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2021/04/14/weld-401SP1-317SP1/">Weld 4.0.1.SP1 and 3.1.7.SP1</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2021-4-14
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/release">release</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Matej Novotny
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>Thanks to your reports, several flaws were discovered in the new class defining for JDK 11+.
-                  We have addressed those issues and because we reckon they are potentially blocking, we have released Weld 3.1.7.SP1 and 4.0.1.SP1.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Two main issues were:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Producers returning an interface type could sometimes try to define a proxy class with invalid name (<a href="https://issues.jboss.org/browse/WELD-2662" target="_blank" rel="noopener">WELD-2662</a>)</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Similar thing could happen for inner classes which should now work as well</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Proxy class names for hierarchical type structures of interfaces could lead to a jumbled combination of package and name (<a href="https://issues.jboss.org/browse/WELD-2666" target="_blank" rel="noopener">WELD-2666</a>)</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Part of this fix is also an improvement wherein Weld actively tries to define new proxies into non-java packages making sure it uses <code>MethodHandles.Lookup</code> whenever applicable</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>Apart from that, this release also addresses a problem with Undertow servlet integration in which (<a href="https://issues.redhat.com/browse/WELD-2664" target=""_blank">Weld tried too eagerly to provide it&#8217;s own instances of <code>Listener</code></a>).</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>&#91; <a href="/download/">Download</a> &#93;
-                  &#91; <a href="http://docs.jboss.org/weld/reference/4.0.1.SP1/en-US/html_single/" target="_blank" rel="noopener">Documentation Weld 4.0.1.SP1</a> &#93;
-                  &#91; <a href="http://docs.jboss.org/weld/reference/3.1.7.SP1/en-US/html_single/" target="_blank" rel="noopener">Documentation Weld 3.1.7.SP1</a> &#93;
-                  &#91; <a href="https://issues.redhat.com/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12354546" target="_blank" rel="noopener">Release notes for Weld 4.0.1.SP1</a> &#93;
-                  &#91; <a href="https://issues.redhat.com/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12354545" target="_blank" rel="noopener">Release notes for Weld 3.1.7.SP1</a> &#93;</p>
-                  </div>
-                </div>
-                <hr>
-              </div>
               <div class="pagination-links"><a href="/news/page/2.html" class="previous-link">Previous</a> <a href="/news/" class="page-link">1</a> <a href="/news/page/2.html" class="page-link">2</a> <span class="current-page">3</span> <a href="/news/page/4.html" class="page-link">4</a> <span class="skip">...</span><a href="/news/page/17.html" class="page-link">17</a> <a href="/news/page/18.html" class="page-link">18</a> <a href="/news/page/4.html" class="next-link">Next</a> </div>
               <hr>
               <div>
diff --git a/news/page/4.html b/news/page/4.html
index 9aa0fa5b..9238d924 100644
--- a/news/page/4.html
+++ b/news/page/4.html
@@ -141,6 +141,67 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2021/04/14/weld-401SP1-317SP1/">Weld 4.0.1.SP1 and 3.1.7.SP1</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2021-4-14
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/release">release</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Matej Novotny
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>Thanks to your reports, several flaws were discovered in the new class defining for JDK 11+.
+                  We have addressed those issues and because we reckon they are potentially blocking, we have released Weld 3.1.7.SP1 and 4.0.1.SP1.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Two main issues were:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Producers returning an interface type could sometimes try to define a proxy class with invalid name (<a href="https://issues.jboss.org/browse/WELD-2662" target="_blank" rel="noopener">WELD-2662</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Similar thing could happen for inner classes which should now work as well</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Proxy class names for hierarchical type structures of interfaces could lead to a jumbled combination of package and name (<a href="https://issues.jboss.org/browse/WELD-2666" target="_blank" rel="noopener">WELD-2666</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Part of this fix is also an improvement wherein Weld actively tries to define new proxies into non-java packages making sure it uses <code>MethodHandles.Lookup</code> whenever applicable</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>Apart from that, this release also addresses a problem with Undertow servlet integration in which (<a href="https://issues.redhat.com/browse/WELD-2664" target=""_blank">Weld tried too eagerly to provide it&#8217;s own instances of <code>Listener</code></a>).</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="/download/">Download</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/4.0.1.SP1/en-US/html_single/" target="_blank" rel="noopener">Documentation Weld 4.0.1.SP1</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/3.1.7.SP1/en-US/html_single/" target="_blank" rel="noopener">Documentation Weld 3.1.7.SP1</a> &#93;
+                  &#91; <a href="https://issues.redhat.com/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12354546" target="_blank" rel="noopener">Release notes for Weld 4.0.1.SP1</a> &#93;
+                  &#91; <a href="https://issues.redhat.com/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12354545" target="_blank" rel="noopener">Release notes for Weld 3.1.7.SP1</a> &#93;</p>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2021/03/22/weld-401Final/">Weld 4.0.1.Final</a>
@@ -538,104 +599,6 @@ <h2 id="_wildfly_patch">WildFly Patch</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2020/09/18/weld-400Beta1/">Weld 4.0.0.Beta1</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2020-9-18
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/release">release</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Matej Novotny
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>A new Weld 4 release is now available!
-                  Latest core version is now 4.0.0.Beta1 and Weld API that ships with it is 4.0.Beta1.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>I will not be listing links to issues as usual, because I think more important work was done outside of JIRA tracking this time (although you can check the issues <a href="https://issues.redhat.com/projects/WELD/versions/12346364">here</a>).
-                  Instead, let me sum it up in a short list of noticeable changes:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>All Weld bits are now present in Maven Central</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Including servlet core (and shaded) which had to be left out last time</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>We are able to execute CDI TCKs in EE 9 environment once again and it&#8217;s all passing</p>
-                  </li>
-                  <li>
-                  <p>We are now able to test servlets with Tomcats and Undertow</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Jetty testing is not possible yet because there is no <a href="https://github.com/arquillian/arquillian-container-jetty/issues/43">Arquillian adapter</a> for it yet</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Reworked documentation generation tooling</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Weld docs now have similar look to those of CDI and are distributed in either PDF or single page HTML format</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Did some updates on Javadoc generation in API and Core if generated with JDK 11</p>
-                  </li>
-                  <li>
-                  <p>Big update pass on tooling and dependencies</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>We are now using Dependabot and have bumped almost every dependency and tooling in the project</p>
-                  </li>
-                  <li>
-                  <p>Which also led to nice cleanup and fixing of several issues</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>On top of that, every bugfix that would go into Weld 3 is of course being added to Weld 4 as well so those aren&#8217;t missing either!</p>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_wildfly_patch">WildFly Patch</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>Sadly we cannot provide a patch for WildFly as there is not yet any official release that would support EE 9.
-                  As soon as there is one, we will surely follow up with Weld patch!</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>&#91; <a href="/download/">Download</a> &#93;
-                  &#91; <a href="http://docs.jboss.org/weld/reference/4.0.0.Beta1/en-US/html_single/" target="_blank" rel="noopener">Documentation</a> &#93;
-                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12346364" target="_blank" rel="noopener">Release notes</a> &#93;</p>
-                  </div>
-                  </div>
-                  </div>
-                </div>
-                <hr>
-              </div>
               <div class="pagination-links"><a href="/news/page/3.html" class="previous-link">Previous</a> <a href="/news/" class="page-link">1</a> <a href="/news/page/2.html" class="page-link">2</a> <a href="/news/page/3.html" class="page-link">3</a> <span class="current-page">4</span> <a href="/news/page/5.html" class="page-link">5</a> <span class="skip">...</span><a href="/news/page/17.html" class="page-link">17</a> <a href="/news/page/18.html" class="page-link">18</a> <a href="/news/page/5.html" class="next-link">Next</a> </div>
               <hr>
               <div>
diff --git a/news/page/5.html b/news/page/5.html
index dbd5e154..6ff75a34 100644
--- a/news/page/5.html
+++ b/news/page/5.html
@@ -141,6 +141,104 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2020/09/18/weld-400Beta1/">Weld 4.0.0.Beta1</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2020-9-18
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/release">release</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Matej Novotny
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>A new Weld 4 release is now available!
+                  Latest core version is now 4.0.0.Beta1 and Weld API that ships with it is 4.0.Beta1.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>I will not be listing links to issues as usual, because I think more important work was done outside of JIRA tracking this time (although you can check the issues <a href="https://issues.redhat.com/projects/WELD/versions/12346364">here</a>).
+                  Instead, let me sum it up in a short list of noticeable changes:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>All Weld bits are now present in Maven Central</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Including servlet core (and shaded) which had to be left out last time</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>We are able to execute CDI TCKs in EE 9 environment once again and it&#8217;s all passing</p>
+                  </li>
+                  <li>
+                  <p>We are now able to test servlets with Tomcats and Undertow</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Jetty testing is not possible yet because there is no <a href="https://github.com/arquillian/arquillian-container-jetty/issues/43">Arquillian adapter</a> for it yet</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Reworked documentation generation tooling</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Weld docs now have similar look to those of CDI and are distributed in either PDF or single page HTML format</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Did some updates on Javadoc generation in API and Core if generated with JDK 11</p>
+                  </li>
+                  <li>
+                  <p>Big update pass on tooling and dependencies</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>We are now using Dependabot and have bumped almost every dependency and tooling in the project</p>
+                  </li>
+                  <li>
+                  <p>Which also led to nice cleanup and fixing of several issues</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>On top of that, every bugfix that would go into Weld 3 is of course being added to Weld 4 as well so those aren&#8217;t missing either!</p>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_wildfly_patch">WildFly Patch</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>Sadly we cannot provide a patch for WildFly as there is not yet any official release that would support EE 9.
+                  As soon as there is one, we will surely follow up with Weld patch!</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="/download/">Download</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/4.0.0.Beta1/en-US/html_single/" target="_blank" rel="noopener">Documentation</a> &#93;
+                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12346364" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2020/08/12/weld-315Final/">Weld 3.1.5.Final</a>
@@ -575,133 +673,6 @@ <h2 id="_wildfly_patch">WildFly Patch</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2019/08/06/weld-312Final/">Weld 3.1.2.Final</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2019-8-6
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/release">release</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Matej Novotny
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>Weld 3.1.2.Final is coming along with Weld API 3.1.SP1. It is another small release bringing in mainly bugfixes.
-                  One notable thing is that thanks to guys from Jetty, Weld 3.1.2.Final is ready to operate with lastest Jetty 9 as well as upcoming Jetty 10.
-                  Other than that we have tried to address some dodgy issues with possible race conditions and leaks - see for yourself!</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Fixes and improvements:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Weld API/SPI</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Fixed possible leak in Jandex index through <code>SimpleServiceRegistry</code> (<a href="https://issues.jboss.org/browse/WELD-2592" target="_blank" rel="noopener">WELD-2592</a>)</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>This could only happen on application server supporting Jandex index and was only noticeable with a lot of application deployed at the same time</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Weld Core</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Fixed a case where some context event notification wouldn&#8217;t trigger observers due to race condition (<a href="https://issues.jboss.org/browse/WELD-2557" target="_blank" rel="noopener">WELD-2557</a>)</p>
-                  </li>
-                  <li>
-                  <p>Fixed rare <code>IllegalAccessError</code> problem during interception when methods had (package) private parameters from different methods (<a href="https://issues.jboss.org/browse/WELD-2583" target="_blank" rel="noopener">WELD-2583</a>)</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Such methods are now automatically ignored when creating intercepted subclasses</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Attempted to fix a race condition that could happen when trying to concurrently initiate conversation ID generator (<a href="https://issues.jboss.org/browse/WELD-2585" target="_blank" rel="noopener">WELD-2585</a>)</p>
-                  </li>
-                  <li>
-                  <p>Weld now correctly disregards synthetic methods when considering proxyability (<a href="https://issues.jboss.org/browse/WELD-2586" target="_blank" rel="noopener">WELD-2586</a>)</p>
-                  </li>
-                  <li>
-                  <p>Correction to <code>beans.xml</code> parses when using Weld namespace (<a href="https://issues.jboss.org/browse/WELD-2591" target="_blank" rel="noopener">WELD-2591</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Weld SE</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Improved classpath scanning to account for manifest file entries (<a href="https://issues.jboss.org/browse/WELD-2589" target="_blank" rel="noopener">WELD-2589</a>)</p>
-                  </li>
-                  <li>
-                  <p><code>javax.enterprise.inject.scan.implicit=true</code> and <code>org.jboss.weld.se.archive.isolation=false</code> now work together correctly (<a href="https://issues.jboss.org/browse/WELD-2590" target="_blank" rel="noopener">WELD-2590</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Weld Servlet</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Update Weld to new Jetty integration model prior to Jetty release (<a href="https://issues.jboss.org/browse/WELD-2587" target="_blank" rel="noopener">WELD-2587</a>)</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Weld 3.1.2.Final is ready to roll with to-be-released Jetty 9.4.x as well as Jetty 10.x</p>
-                  </li>
-                  <li>
-                  <p>Of course we also kept legacy support in place, so even older version will still run</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_wildfly_patch">WildFly Patch</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>This time around, the <a href="http://download.jboss.org/weld/3.1.2.Final/wildfly-17.0.1.Final-weld-3.1.2.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly 17.0.1.Final</a> is available.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>If you’re not familiar with patching WildFly, check the <a href="/documentation/#12">FAQ</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>&#91; <a href="/download/">Download</a> &#93;
-                  &#91; <a href="http://docs.jboss.org/weld/reference/3.1.2.Final/en-US/html/" target="_blank" rel="noopener">Documentation</a> &#93;
-                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12341958" target="_blank" rel="noopener">Release notes</a> &#93;</p>
-                  </div>
-                  </div>
-                  </div>
-                </div>
-                <hr>
-              </div>
               <div class="pagination-links"><a href="/news/page/4.html" class="previous-link">Previous</a> <a href="/news/" class="page-link">1</a> <a href="/news/page/2.html" class="page-link">2</a> <span class="skip">...</span><a href="/news/page/4.html" class="page-link">4</a> <span class="current-page">5</span> <a href="/news/page/6.html" class="page-link">6</a> <span class="skip">...</span><a href="/news/page/17.html" class="page-link">17</a> <a href="/news/page/18.html" class="page-link">18</a> <a href="/news/page/6.html" class="next-link">Next</a> </div>
               <hr>
               <div>
diff --git a/news/page/6.html b/news/page/6.html
index f784b3b1..c5cfb410 100644
--- a/news/page/6.html
+++ b/news/page/6.html
@@ -141,6 +141,133 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2019/08/06/weld-312Final/">Weld 3.1.2.Final</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2019-8-6
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/release">release</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Matej Novotny
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>Weld 3.1.2.Final is coming along with Weld API 3.1.SP1. It is another small release bringing in mainly bugfixes.
+                  One notable thing is that thanks to guys from Jetty, Weld 3.1.2.Final is ready to operate with lastest Jetty 9 as well as upcoming Jetty 10.
+                  Other than that we have tried to address some dodgy issues with possible race conditions and leaks - see for yourself!</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Fixes and improvements:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Weld API/SPI</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Fixed possible leak in Jandex index through <code>SimpleServiceRegistry</code> (<a href="https://issues.jboss.org/browse/WELD-2592" target="_blank" rel="noopener">WELD-2592</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>This could only happen on application server supporting Jandex index and was only noticeable with a lot of application deployed at the same time</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Weld Core</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Fixed a case where some context event notification wouldn&#8217;t trigger observers due to race condition (<a href="https://issues.jboss.org/browse/WELD-2557" target="_blank" rel="noopener">WELD-2557</a>)</p>
+                  </li>
+                  <li>
+                  <p>Fixed rare <code>IllegalAccessError</code> problem during interception when methods had (package) private parameters from different methods (<a href="https://issues.jboss.org/browse/WELD-2583" target="_blank" rel="noopener">WELD-2583</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Such methods are now automatically ignored when creating intercepted subclasses</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Attempted to fix a race condition that could happen when trying to concurrently initiate conversation ID generator (<a href="https://issues.jboss.org/browse/WELD-2585" target="_blank" rel="noopener">WELD-2585</a>)</p>
+                  </li>
+                  <li>
+                  <p>Weld now correctly disregards synthetic methods when considering proxyability (<a href="https://issues.jboss.org/browse/WELD-2586" target="_blank" rel="noopener">WELD-2586</a>)</p>
+                  </li>
+                  <li>
+                  <p>Correction to <code>beans.xml</code> parses when using Weld namespace (<a href="https://issues.jboss.org/browse/WELD-2591" target="_blank" rel="noopener">WELD-2591</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Weld SE</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Improved classpath scanning to account for manifest file entries (<a href="https://issues.jboss.org/browse/WELD-2589" target="_blank" rel="noopener">WELD-2589</a>)</p>
+                  </li>
+                  <li>
+                  <p><code>javax.enterprise.inject.scan.implicit=true</code> and <code>org.jboss.weld.se.archive.isolation=false</code> now work together correctly (<a href="https://issues.jboss.org/browse/WELD-2590" target="_blank" rel="noopener">WELD-2590</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Weld Servlet</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Update Weld to new Jetty integration model prior to Jetty release (<a href="https://issues.jboss.org/browse/WELD-2587" target="_blank" rel="noopener">WELD-2587</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Weld 3.1.2.Final is ready to roll with to-be-released Jetty 9.4.x as well as Jetty 10.x</p>
+                  </li>
+                  <li>
+                  <p>Of course we also kept legacy support in place, so even older version will still run</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_wildfly_patch">WildFly Patch</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>This time around, the <a href="http://download.jboss.org/weld/3.1.2.Final/wildfly-17.0.1.Final-weld-3.1.2.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly 17.0.1.Final</a> is available.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>If you’re not familiar with patching WildFly, check the <a href="/documentation/#12">FAQ</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="/download/">Download</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/3.1.2.Final/en-US/html/" target="_blank" rel="noopener">Documentation</a> &#93;
+                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12341958" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2019/05/07/weld-311Final/">Weld 3.1.1.Final</a>
@@ -746,47 +873,6 @@ <h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2018/07/10/weld-team-changes/">Weld team changes</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2018-7-10
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/team">team</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Martin Kouba
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>I&#8217;m pleased to announce a couple of changes coming to the Weld team.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>First of all, <a href="https://github.com/manovotn">Matěj Novotný</a> will be taking over the leadership of the project.
-                  Matěj has proven himself to be an excellent engineer, contributing not only to Weld projects but also to the CDI specification and TCK development.
-                  I&#8217;m really happy that I can hand over the leadership to this guy!</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Matěj&#8217;s primary task is leading the project towards "Java 11 world" and to meet the other challenges such as reactive programming model enhancements.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Secondly, <a href="https://github.com/nziakova">Nikoleta Žiaková</a> is joining the team as a quality engineer.
-                  She’s going to work on expanding our testsuites and improving our continuous integration.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Last but not least, I&#8217;m not going to leave the project but stay as a contributor focused on related technologies such as <a href="http://wildfly.org/">WildFly</a>, <a href="https://github.com/thorntail/thorntail">Thorntail</a> and MicroProfile.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Martin</p>
-                  </div>
-                </div>
-                <hr>
-              </div>
               <div class="pagination-links"><a href="/news/page/5.html" class="previous-link">Previous</a> <a href="/news/" class="page-link">1</a> <a href="/news/page/2.html" class="page-link">2</a> <span class="skip">...</span><a href="/news/page/5.html" class="page-link">5</a> <span class="current-page">6</span> <a href="/news/page/7.html" class="page-link">7</a> <span class="skip">...</span><a href="/news/page/17.html" class="page-link">17</a> <a href="/news/page/18.html" class="page-link">18</a> <a href="/news/page/7.html" class="next-link">Next</a> </div>
               <hr>
               <div>
diff --git a/news/page/7.html b/news/page/7.html
index 4c10699a..cfdf1ead 100644
--- a/news/page/7.html
+++ b/news/page/7.html
@@ -141,6 +141,47 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2018/07/10/weld-team-changes/">Weld team changes</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2018-7-10
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/team">team</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Martin Kouba
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>I&#8217;m pleased to announce a couple of changes coming to the Weld team.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>First of all, <a href="https://github.com/manovotn">Matěj Novotný</a> will be taking over the leadership of the project.
+                  Matěj has proven himself to be an excellent engineer, contributing not only to Weld projects but also to the CDI specification and TCK development.
+                  I&#8217;m really happy that I can hand over the leadership to this guy!</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Matěj&#8217;s primary task is leading the project towards "Java 11 world" and to meet the other challenges such as reactive programming model enhancements.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Secondly, <a href="https://github.com/nziakova">Nikoleta Žiaková</a> is joining the team as a quality engineer.
+                  She’s going to work on expanding our testsuites and improving our continuous integration.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Last but not least, I&#8217;m not going to leave the project but stay as a contributor focused on related technologies such as <a href="http://wildfly.org/">WildFly</a>, <a href="https://github.com/thorntail/thorntail">Thorntail</a> and MicroProfile.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Martin</p>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2018/04/26/weld-304Final/">Weld 3.0.4.Final</a>
@@ -709,136 +750,6 @@ <h2 id="_what_if_i_would_like_to">What If I Would Like To&#8230;&#8203;</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2017/12/18/weld-246Final/">Weld 2.4.6.Final</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2017-12-18
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/release">release</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Matej Novotny
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>Time has come for another round of Weld 2.4 bugfix release.
-                  But that&#8217;s not all - this time there is also new API to go along with this release - Weld API 2.4.SP2.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Among other things you can now obtain interceptor binding from <code>javax.interceptor.InvocationContext</code>, use enriched version of <code>javax.enterprise.event.Event</code> or select <code>javax.enterprise.inject.Instance</code> based on <code>java.lang.reflect.Type</code>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Notable fixes and improvements:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Weld Core:</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Improved subclass generation mechanism for generic interceptors (<a href="https://issues.jboss.org/browse/WELD-2414" target="_blank" rel="noopener">WELD-2414</a>)</p>
-                  </li>
-                  <li>
-                  <p>Corrected proxy creation for signed classes (<a href="https://issues.jboss.org/browse/WELD-2425" target="_blank" rel="noopener">WELD-2425</a>)</p>
-                  </li>
-                  <li>
-                  <p>Correct <code>InjectionPoint</code> bean behaviour when used within <code>AfterBeanDiscovery</code> observer (<a href="https://issues.jboss.org/browse/WELD-2429" target="_blank" rel="noopener">WELD-2429</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Weld SE</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>There are now multiple convenient error-proof methods to quickly configure SE container (<a href="https://issues.jboss.org/browse/WELD-2426" target="_blank" rel="noopener">WELD-2426</a>)</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p><code>Weld.enableDevMode()</code>, <code>Weld.scanClasspathEntries()</code>, &#8230;&#8203;</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Weld API/SPI</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p><code>WeldInstance</code> has several improvements</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>It now allows you to <code>select()</code> beans based on <code>java.lang.reflect.Type</code> (<a href="https://issues.jboss.org/browse/WELD-2427" target="_blank" rel="noopener">WELD-2427</a>)</p>
-                  </li>
-                  <li>
-                  <p><code>WeldInstance.Handler</code> had become lazy which means you can now iterate/filter/sort <code>WeldInstance</code> without actually instantiating beans (<a href="https://issues.jboss.org/browse/WELD-2258" target="_blank" rel="noopener">WELD-2258</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>There is new interface in the API - <code>WeldEvent</code> - which can be used in place of well known <code>Event</code> but allows you narrow down event type by using <code>select()</code> with <code>java.lang.reflect.Type</code> (<a href="https://issues.jboss.org/browse/WELD-2427" target="_blank" rel="noopener">WELD-2427</a>)</p>
-                  </li>
-                  <li>
-                  <p>API now contains <code>WeldInvocationContext</code>, an enriched version of <code>javax.interceptor.InvocationContext</code> which allows to obtain interceptor binding (<a href="https://issues.jboss.org/browse/WELD-2433" target="_blank" rel="noopener">WELD-2433</a>)</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>There is also a <code>String</code> key used to obtain interceptors binding directly from <code>InvocationContext</code> (<a href="https://issues.jboss.org/browse/WELD-2436" target="_blank" rel="noopener">WELD-2436</a>)</p>
-                  </li>
-                  <li>
-                  <p>In order to learn more, please refer to (<a href="http://docs.jboss.org/weld/reference/latest/en-US/html_single/#_enhanced_version_of_literal_javax_interceptor_invocationcontext_literal" target="_blank" rel="noopener">our documentation</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Other</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Probe - fixed NPE which might occur when bean had <code>@Priority</code> but no other annotation (<a href="https://issues.jboss.org/browse/WELD-2432" target="_blank" rel="noopener">WELD-2432</a>)</p>
-                  </li>
-                  <li>
-                  <p>All the API changes should now be documented within Weld docs</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_wildfly_patch">WildFly Patch</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>As usual, a <a href="http://download.jboss.org/weld/2.4.6.Final/wildfly-11.0.0.Final-weld-2.4.6.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly 11.0.0.Final</a> is available.
-                  If you’re not familiar with patching WildFly, check the <a href="/documentation/#12">FAQ</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>&#91; <a href="/download/">Download</a> &#93;
-                  &#91; <a href="http://docs.jboss.org/weld/reference/2.4.6.Final/en-US/html/" target="_blank" rel="noopener">Documentation</a> &#93;
-                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?version=12334958&amp;styleName=Html&amp;projectId=12310891" target="_blank" rel="noopener">Release notes</a> &#93;</p>
-                  </div>
-                  </div>
-                  </div>
-                </div>
-                <hr>
-              </div>
               <div class="pagination-links"><a href="/news/page/6.html" class="previous-link">Previous</a> <a href="/news/" class="page-link">1</a> <a href="/news/page/2.html" class="page-link">2</a> <span class="skip">...</span><a href="/news/page/6.html" class="page-link">6</a> <span class="current-page">7</span> <a href="/news/page/8.html" class="page-link">8</a> <span class="skip">...</span><a href="/news/page/17.html" class="page-link">17</a> <a href="/news/page/18.html" class="page-link">18</a> <a href="/news/page/8.html" class="next-link">Next</a> </div>
               <hr>
               <div>
diff --git a/news/page/8.html b/news/page/8.html
index 5d29fa84..500f7f3e 100644
--- a/news/page/8.html
+++ b/news/page/8.html
@@ -141,6 +141,136 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2017/12/18/weld-246Final/">Weld 2.4.6.Final</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2017-12-18
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/release">release</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Matej Novotny
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>Time has come for another round of Weld 2.4 bugfix release.
+                  But that&#8217;s not all - this time there is also new API to go along with this release - Weld API 2.4.SP2.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Among other things you can now obtain interceptor binding from <code>javax.interceptor.InvocationContext</code>, use enriched version of <code>javax.enterprise.event.Event</code> or select <code>javax.enterprise.inject.Instance</code> based on <code>java.lang.reflect.Type</code>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Notable fixes and improvements:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Weld Core:</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Improved subclass generation mechanism for generic interceptors (<a href="https://issues.jboss.org/browse/WELD-2414" target="_blank" rel="noopener">WELD-2414</a>)</p>
+                  </li>
+                  <li>
+                  <p>Corrected proxy creation for signed classes (<a href="https://issues.jboss.org/browse/WELD-2425" target="_blank" rel="noopener">WELD-2425</a>)</p>
+                  </li>
+                  <li>
+                  <p>Correct <code>InjectionPoint</code> bean behaviour when used within <code>AfterBeanDiscovery</code> observer (<a href="https://issues.jboss.org/browse/WELD-2429" target="_blank" rel="noopener">WELD-2429</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Weld SE</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>There are now multiple convenient error-proof methods to quickly configure SE container (<a href="https://issues.jboss.org/browse/WELD-2426" target="_blank" rel="noopener">WELD-2426</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p><code>Weld.enableDevMode()</code>, <code>Weld.scanClasspathEntries()</code>, &#8230;&#8203;</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Weld API/SPI</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p><code>WeldInstance</code> has several improvements</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>It now allows you to <code>select()</code> beans based on <code>java.lang.reflect.Type</code> (<a href="https://issues.jboss.org/browse/WELD-2427" target="_blank" rel="noopener">WELD-2427</a>)</p>
+                  </li>
+                  <li>
+                  <p><code>WeldInstance.Handler</code> had become lazy which means you can now iterate/filter/sort <code>WeldInstance</code> without actually instantiating beans (<a href="https://issues.jboss.org/browse/WELD-2258" target="_blank" rel="noopener">WELD-2258</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>There is new interface in the API - <code>WeldEvent</code> - which can be used in place of well known <code>Event</code> but allows you narrow down event type by using <code>select()</code> with <code>java.lang.reflect.Type</code> (<a href="https://issues.jboss.org/browse/WELD-2427" target="_blank" rel="noopener">WELD-2427</a>)</p>
+                  </li>
+                  <li>
+                  <p>API now contains <code>WeldInvocationContext</code>, an enriched version of <code>javax.interceptor.InvocationContext</code> which allows to obtain interceptor binding (<a href="https://issues.jboss.org/browse/WELD-2433" target="_blank" rel="noopener">WELD-2433</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>There is also a <code>String</code> key used to obtain interceptors binding directly from <code>InvocationContext</code> (<a href="https://issues.jboss.org/browse/WELD-2436" target="_blank" rel="noopener">WELD-2436</a>)</p>
+                  </li>
+                  <li>
+                  <p>In order to learn more, please refer to (<a href="http://docs.jboss.org/weld/reference/latest/en-US/html_single/#_enhanced_version_of_literal_javax_interceptor_invocationcontext_literal" target="_blank" rel="noopener">our documentation</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Other</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Probe - fixed NPE which might occur when bean had <code>@Priority</code> but no other annotation (<a href="https://issues.jboss.org/browse/WELD-2432" target="_blank" rel="noopener">WELD-2432</a>)</p>
+                  </li>
+                  <li>
+                  <p>All the API changes should now be documented within Weld docs</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_wildfly_patch">WildFly Patch</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>As usual, a <a href="http://download.jboss.org/weld/2.4.6.Final/wildfly-11.0.0.Final-weld-2.4.6.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly 11.0.0.Final</a> is available.
+                  If you’re not familiar with patching WildFly, check the <a href="/documentation/#12">FAQ</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="/download/">Download</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/2.4.6.Final/en-US/html/" target="_blank" rel="noopener">Documentation</a> &#93;
+                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?version=12334958&amp;styleName=Html&amp;projectId=12310891" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2017/11/23/weld-302Final/">Weld 3.0.2.Final</a>
@@ -694,124 +824,6 @@ <h2 id="_future_and_plans">Future and Plans</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2017/06/14/weld-244Final/">Weld 2.4.4.Final</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2017-6-14
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/release">release</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Matej Novotny
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>We have been busy chasing down some annoying little bugs and it&#8217;s high time you got the fruits of those efforts into your hands.
-                  Say hello to Weld 2.4.4.Final.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Notable fixes and improvements:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Weld Core</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Fixed bean discovery event ordering when processing producers (<a href="https://issues.jboss.org/browse/WELD-2393" target="_blank" rel="noopener">WELD-2393</a>)</p>
-                  </li>
-                  <li>
-                  <p>Eliminated an NPE for a corner case with abstract decorator (<a href="https://issues.jboss.org/browse/WELD-2273" target="_blank" rel="noopener">WELD-2273</a>)</p>
-                  </li>
-                  <li>
-                  <p>Corrected <code>@Initialized(RequestScoped.class)</code> event firing in <code>@PostConstruct</code> callbacks (<a href="https://issues.jboss.org/browse/WELD-2372" target="_blank" rel="noopener">WELD-2372</a>)</p>
-                  </li>
-                  <li>
-                  <p>Fixed <code>BeanManager.isStereotype()</code> behavior when checking a qualifier annotated with yet another qualifier (<a href="https://issues.jboss.org/browse/WELD-2390" target="_blank" rel="noopener">WELD-2390</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Weld SE</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Added a convenience static method <code>WeldContainer.current()</code>, a shortcut for <code>CDI.current()</code> with no need to cast the result (<a href="https://issues.jboss.org/browse/WELD-2399" target="_blank" rel="noopener">WELD-2399</a>)</p>
-                  </li>
-                  <li>
-                  <p>Allowed to specify bean discovery mode for synthetic archives (<a href="https://issues.jboss.org/browse/WELD-2386" target="_blank" rel="noopener">WELD-2386</a>)</p>
-                  </li>
-                  <li>
-                  <p>Fixed bean class discovery problem when adding whole packages (<a href="https://issues.jboss.org/browse/WELD-2395" target="_blank" rel="noopener">WELD-2395</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Weld Servlet</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Improved logging and make checks more lenient in case the container is not yet bootstrapped (<a href="https://issues.jboss.org/browse/WELD-2382" target="_blank" rel="noopener">WELD-2382</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Configuration options</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>In SE and Servlet environments, Jandex can now be forcibly prohibited from processing your archives. This is useful when a third-party dependecy brings in some unsupported Jandex version (<a href="https://issues.jboss.org/browse/WELD-2374" target="_blank" rel="noopener">WELD-2374</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Development tools</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>If a deployment validation fails and the development mode is enabled, a simple <strong>validation HTML report</strong> (which contains a lot of useful information) is generated</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Users are encouraged to always attach this report when asking a question on the mailing list or any other communication channel</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_wildfly_patch">WildFly Patch</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>As usual, a <a href="http://download.jboss.org/weld/2.4.4.Final/wildfly-10.1.0.Final-weld-2.4.4.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly</a> is available.
-                  Target platform is <strong>WildFly 10.1.0.Final</strong>.
-                  If you’re not familiar with patching WildFly, check the <a href="/documentation/#12">FAQ</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>&#91; <a href="/download/">Download</a> &#93;
-                  &#91; <a href="http://docs.jboss.org/weld/reference/2.4.4.Final/en-US/html/" target="_blank" rel="noopener">Documentation</a> &#93;
-                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?version=12334296&amp;styleName=Html&amp;projectId=12310891" target="_blank" rel="noopener">Release notes</a> &#93;</p>
-                  </div>
-                  </div>
-                  </div>
-                </div>
-                <hr>
-              </div>
               <div class="pagination-links"><a href="/news/page/7.html" class="previous-link">Previous</a> <a href="/news/" class="page-link">1</a> <a href="/news/page/2.html" class="page-link">2</a> <span class="skip">...</span><a href="/news/page/7.html" class="page-link">7</a> <span class="current-page">8</span> <a href="/news/page/9.html" class="page-link">9</a> <span class="skip">...</span><a href="/news/page/17.html" class="page-link">17</a> <a href="/news/page/18.html" class="page-link">18</a> <a href="/news/page/9.html" class="next-link">Next</a> </div>
               <hr>
               <div>
diff --git a/news/page/9.html b/news/page/9.html
index 77272ebd..9ccb6b9d 100644
--- a/news/page/9.html
+++ b/news/page/9.html
@@ -141,6 +141,124 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2017/06/14/weld-244Final/">Weld 2.4.4.Final</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2017-6-14
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/release">release</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Matej Novotny
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>We have been busy chasing down some annoying little bugs and it&#8217;s high time you got the fruits of those efforts into your hands.
+                  Say hello to Weld 2.4.4.Final.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Notable fixes and improvements:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Weld Core</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Fixed bean discovery event ordering when processing producers (<a href="https://issues.jboss.org/browse/WELD-2393" target="_blank" rel="noopener">WELD-2393</a>)</p>
+                  </li>
+                  <li>
+                  <p>Eliminated an NPE for a corner case with abstract decorator (<a href="https://issues.jboss.org/browse/WELD-2273" target="_blank" rel="noopener">WELD-2273</a>)</p>
+                  </li>
+                  <li>
+                  <p>Corrected <code>@Initialized(RequestScoped.class)</code> event firing in <code>@PostConstruct</code> callbacks (<a href="https://issues.jboss.org/browse/WELD-2372" target="_blank" rel="noopener">WELD-2372</a>)</p>
+                  </li>
+                  <li>
+                  <p>Fixed <code>BeanManager.isStereotype()</code> behavior when checking a qualifier annotated with yet another qualifier (<a href="https://issues.jboss.org/browse/WELD-2390" target="_blank" rel="noopener">WELD-2390</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Weld SE</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Added a convenience static method <code>WeldContainer.current()</code>, a shortcut for <code>CDI.current()</code> with no need to cast the result (<a href="https://issues.jboss.org/browse/WELD-2399" target="_blank" rel="noopener">WELD-2399</a>)</p>
+                  </li>
+                  <li>
+                  <p>Allowed to specify bean discovery mode for synthetic archives (<a href="https://issues.jboss.org/browse/WELD-2386" target="_blank" rel="noopener">WELD-2386</a>)</p>
+                  </li>
+                  <li>
+                  <p>Fixed bean class discovery problem when adding whole packages (<a href="https://issues.jboss.org/browse/WELD-2395" target="_blank" rel="noopener">WELD-2395</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Weld Servlet</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Improved logging and make checks more lenient in case the container is not yet bootstrapped (<a href="https://issues.jboss.org/browse/WELD-2382" target="_blank" rel="noopener">WELD-2382</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Configuration options</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>In SE and Servlet environments, Jandex can now be forcibly prohibited from processing your archives. This is useful when a third-party dependecy brings in some unsupported Jandex version (<a href="https://issues.jboss.org/browse/WELD-2374" target="_blank" rel="noopener">WELD-2374</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Development tools</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>If a deployment validation fails and the development mode is enabled, a simple <strong>validation HTML report</strong> (which contains a lot of useful information) is generated</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Users are encouraged to always attach this report when asking a question on the mailing list or any other communication channel</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_wildfly_patch">WildFly Patch</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>As usual, a <a href="http://download.jboss.org/weld/2.4.4.Final/wildfly-10.1.0.Final-weld-2.4.4.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly</a> is available.
+                  Target platform is <strong>WildFly 10.1.0.Final</strong>.
+                  If you’re not familiar with patching WildFly, check the <a href="/documentation/#12">FAQ</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="/download/">Download</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/2.4.4.Final/en-US/html/" target="_blank" rel="noopener">Documentation</a> &#93;
+                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?version=12334296&amp;styleName=Html&amp;projectId=12310891" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2017/05/19/tour-around-weld-3/">Tour around Weld 3</a>
@@ -753,98 +871,6 @@ <h2 id="_wildfly_patch">WildFly Patch</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2017/02/02/weld-242Final/">Weld 2.4.2.Final</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2017-2-2
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/release">release</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Martin Kouba
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>As you may know, CDI 2 (JSR 365) is in Public Review phase.
-                  That&#8217;s great news for early adopters.
-                  But for now, I am very pleased to announce another production-ready version of <strong>Weld 2.4</strong> (CDI 1.2).
-                  See also <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12332808" target="_blank" rel="noopener">the release details</a>.
-                  Thanks to everyone involved in this release!</p>
-                  </div>
-                  <div class="admonitionblock warning">
-                  <table>
-                  <tr>
-                  <td class="icon">
-                  <div class="title">Warning</div>
-                  </td>
-                  <td class="content">
-                  There is a <a href="https://issues.jboss.org/browse/WELD-2328" target="_blank" rel="noopener">regression</a> in Weld <strong>2.4.2.Final</strong>. The problem only occurs if a <a href="https://docs.oracle.com/javase/tutorial/essential/environment/security.html" target="_blank" rel="noopener">Security Manager</a> is used. However, users are encouraged to upgrade to <strong>2.4.2.SP1</strong> which contains a fix for the issue.
-                  </td>
-                  </tr>
-                  </table>
-                  </div>
-                  <div class="paragraph">
-                  <p>Notable fixes and improvements:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Added <strong>trimmed bean archives</strong> support (CDI 2.0, <a href="https://issues.jboss.org/browse/WELD-2314" target="_blank" rel="noopener">WELD-2314</a>)</p>
-                  </li>
-                  <li>
-                  <p>Fixed Weld SE and Weld Servlet cooperation (<a href="https://issues.jboss.org/browse/WELD-2260" target="_blank" rel="noopener">WELD-2260</a> and <a href="https://issues.jboss.org/browse/WELD-2262" target="_blank" rel="noopener">WELD-2262</a>)</p>
-                  </li>
-                  <li>
-                  <p>Fixed <code>ActivateRequestContextInterceptor</code> - align the priority with CDI 2.0, fire <code>@Initialized</code> and <code>@Destroyed</code> events (CDI 2.0, <a href="https://issues.jboss.org/browse/WELD-2281" target="_blank" rel="noopener">WELD-2281</a>)</p>
-                  </li>
-                  <li>
-                  <p>Fixed JDK9 build problems (<a href="https://issues.jboss.org/browse/WELD-2303" target="_blank" rel="noopener">WELD-2303</a> and <a href="https://issues.jboss.org/browse/WELD-2301" target="_blank" rel="noopener">WELD-2301</a>)</p>
-                  </li>
-                  <li>
-                  <p>Validation - allow to use CDI 2 rules when validating selected alternatives in <code>bean.xml</code> (<a href="https://issues.jboss.org/browse/WELD-2313" target="_blank" rel="noopener">WELD-2313</a>)</p>
-                  </li>
-                  <li>
-                  <p>Performance improvements in <code>javax.enterprise.inject.Instance</code> implementation (CDI 2.0, <a href="https://issues.jboss.org/browse/WELD-2323" target="_blank" rel="noopener">WELD-2323</a>)</p>
-                  </li>
-                  <li>
-                  <p>Illegal bean types ignored for a session bean (<a href="https://issues.jboss.org/browse/WELD-2315" target="_blank" rel="noopener">WELD-2315</a>)</p>
-                  </li>
-                  <li>
-                  <p>Dependency upgrade - <code>jboss-classfilewriter</code> to 1.2.1.Final (enables interception of default methods, see also <a href="https://issues.jboss.org/browse/WELD-2093" target="_blank" rel="noopener">WELD-2093</a>)</p>
-                  </li>
-                  <li>
-                  <p>Weld SE - addded useful methods from <code>SeContainerInitializer</code> (CDI 2.0, <a href="https://issues.jboss.org/browse/WELD-2316" target="_blank" rel="noopener">WELD-2316</a>)</p>
-                  </li>
-                  <li>
-                  <p>Probe development tool - extended bean archive info</p>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_wildfly_patch">WildFly Patch</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>As usual, a <a href="http://download.jboss.org/weld/2.4.2.Final/wildfly-10.1.0.Final-weld-2.4.2.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly</a> is available.
-                  This time the target platform is <strong>WildFly 10.1.0.Final</strong>.
-                  If you’re not familiar with patching WildFly, check the <a href="/documentation/#12">FAQ</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>&#91; <a href="http://docs.jboss.org/cdi/api/1.2/" target="_blank" rel="noopener">CDI 1.2 API</a> &#93;
-                  &#91; <a href="/download/">Download</a> &#93;
-                  &#91; <a href="http://docs.jboss.org/weld/reference/2.4.0.Final/en-US/html/" target="_blank" rel="noopener">Documentation</a> &#93;
-                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12332808" target="_blank" rel="noopener">Release notes</a> &#93;</p>
-                  </div>
-                  </div>
-                  </div>
-                </div>
-                <hr>
-              </div>
               <div class="pagination-links"><a href="/news/page/8.html" class="previous-link">Previous</a> <a href="/news/" class="page-link">1</a> <a href="/news/page/2.html" class="page-link">2</a> <span class="skip">...</span><a href="/news/page/8.html" class="page-link">8</a> <span class="current-page">9</span> <a href="/news/page/10.html" class="page-link">10</a> <span class="skip">...</span><a href="/news/page/17.html" class="page-link">17</a> <a href="/news/page/18.html" class="page-link">18</a> <a href="/news/page/10.html" class="next-link">Next</a> </div>
               <hr>
               <div>
diff --git a/news/tags/release/index.html b/news/tags/release/index.html
index bcfd6e6e..0406222c 100644
--- a/news/tags/release/index.html
+++ b/news/tags/release/index.html
@@ -141,6 +141,120 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2023/10/26/weld-600Alpha1/">Weld 6.0.0.Alpha1</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2023-10-26
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/release">release</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Matej Novotny
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>Looking for a CDI 4.1 implementation? We&#8217;ve got you covered!
+                  Weld Core 6.0.0.Alpha1 is now available and comes along with CDI API 4.1.0.Alpha1.
+                  Note that this version also uses latest version (2.2.0-RC1) of the Jakarta Interceptors specification.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>CDI/CDI TCK related additions:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Create first implementation of CDI method invokers using <code>MethodHandles</code> (<a href="https://issues.redhat.com/browse/WELD-2764">WELD-2764</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>If you want to read up more about the original CDI API design and PR, take a look (<a href="https://github.com/jakartaee/cdi/pull/639">here</a>)</p>
+                  </li>
+                  <li>
+                  <p>Note that this feature is still being improved on both, CDI side and (<a href="https://issues.redhat.com/browse/WELD-2765">Weld side</a>) but the general shape of it is already carved out</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Support standardized means of getting interceptor bindings from <code>InvocationContext</code> (<a href="https://issues.redhat.com/browse/WELD-2756">WELD-2756</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>This was already possible via set of methods in <code>WeldInvocationContext</code> as well as the <code>String</code> key under which we stored these bindings in <code>InvocationContext</code></p>
+                  </li>
+                  <li>
+                  <p>Both of the above are no deprecated (but still working) and users are expected to use the standardized approach</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Support inspectable <code>CreationalContext</code> and <code>Contextual</code> in CDI TCK SPI (<a href="https://issues.redhat.com/browse/WELD-2757">WELD-2757</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>Other bugfixes and project QoL features:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Fix proxy creation for beans using <code>@Typed</code> and having package-protected types split across packages (<a href="https://issues.redhat.com/browse/WELD-2758">WELD-2758</a>)</p>
+                  </li>
+                  <li>
+                  <p>Correct how we determine proxy package for beans with unassignable types in their bean type set (<a href="https://issues.redhat.com/browse/WELD-2763">WELD-2763</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>This  was only problematic in environments using <code>WeldDefaultProxyServices</code> to define their proxies (such as Weld SE)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p><code>WeldManager#getContexts</code> now correctly returns an empty set when there are no contexts for given scope (<a href="https://issues.redhat.com/browse/WELD-2761">WELD-2761</a>)</p>
+                  </li>
+                  <li>
+                  <p>Fix possible memory leak with repetitive thread group creation (<a href="https://issues.redhat.com/browse/WELD-2755">WELD-2755</a>)</p>
+                  </li>
+                  <li>
+                  <p><code>WeldInitialListener</code> can no longer throw NPE is application fails to start (<a href="https://issues.redhat.com/browse/WELD-2752">WELD-2752</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Only possible in some EE containers on repeated re-deployment of Weld applications</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p><code>LazySessionBeanStore</code> no longer swallows exceptions happening when attempting to initiate HTTP session (<a href="https://issues.redhat.com/browse/WELD-2762">WELD-2762</a>)</p>
+                  </li>
+                  <li>
+                  <p>Weld Core and Weld API are now using formatter plugin and impsort instead of checkstyle (<a href="https://issues.redhat.com/browse/WELD-2753">WELD-2753</a>)</p>
+                  </li>
+                  <li>
+                  <p>Jandex version was bumped to 3.x across the project (<a href="https://issues.redhat.com/browse/WELD-2754">WELD-2754</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>As always, if you find further issues with Weld 6, let us know and we&#8217;ll try to help.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="/download/">Download</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/6.0.0.Alpha1/en-US/html_single/" target="_blank" rel="noopener">Documentation</a> &#93;
+                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12413485" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2023/10/05/weld-512Final/">Weld 5.1.2.Final</a>
@@ -647,42 +761,6 @@ <h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2022/03/23/weld-500CR2/">Weld 5.0.0.CR2</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2022-3-23
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/release">release</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Matej Novotny
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>Final ballot of CDI 4 has uncovered untested and unimplemented area in the newly added <code>Startup</code> and <code>Shutdown</code> events.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Our previous release was guilty of not supporting this properly, hence here comes Weld API 5.0.CR2 and Weld Core 5.0.0.CR2.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Weld now automatically fires these events and the JIRA issue for this can be seen <a href="https://issues.jboss.org/browse/WELD-2709" target="_blank" rel="noopener">here (WELD-2709)</a>.
-                  However, integrators can choose to override this behavior and fire both events themselves in case there is more bootstrapping logic that needs to come together before the container is deemed ready.
-                  The API interface <a href="https://github.com/weld/api/blob/5.0.CR2/weld-spi/src/main/java/org/jboss/weld/bootstrap/api/Environment.java#L48-L70"><code>org.jboss.weld.bootstrap.api.Environment</code></a> allows implementors to override a specific method which will then prevent Weld from handling these events.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>&#91; <a href="/download/">Download</a> &#93;
-                  &#91; <a href="http://docs.jboss.org/weld/reference/5.0.0.CR2/en-US/html_single/" target="_blank" rel="noopener">Documentation</a> &#93;
-                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12382781" target="_blank" rel="noopener">Release notes</a> &#93;</p>
-                  </div>
-                </div>
-                <hr>
-              </div>
               <div class="pagination-links"><span class="current-page">1</span> <a href="/news/tags/release/page/2.html" class="page-link">2</a> <span class="skip">...</span><a href="/news/tags/release/page/5.html" class="page-link">5</a> <a href="/news/tags/release/page/6.html" class="page-link">6</a> <a href="/news/tags/release/page/2.html" class="next-link">Next</a> </div>
               <hr>
               <div>
diff --git a/news/tags/release/page/2.html b/news/tags/release/page/2.html
index 878c712a..c7282c27 100644
--- a/news/tags/release/page/2.html
+++ b/news/tags/release/page/2.html
@@ -141,6 +141,42 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2022/03/23/weld-500CR2/">Weld 5.0.0.CR2</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2022-3-23
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/release">release</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Matej Novotny
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>Final ballot of CDI 4 has uncovered untested and unimplemented area in the newly added <code>Startup</code> and <code>Shutdown</code> events.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Our previous release was guilty of not supporting this properly, hence here comes Weld API 5.0.CR2 and Weld Core 5.0.0.CR2.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Weld now automatically fires these events and the JIRA issue for this can be seen <a href="https://issues.jboss.org/browse/WELD-2709" target="_blank" rel="noopener">here (WELD-2709)</a>.
+                  However, integrators can choose to override this behavior and fire both events themselves in case there is more bootstrapping logic that needs to come together before the container is deemed ready.
+                  The API interface <a href="https://github.com/weld/api/blob/5.0.CR2/weld-spi/src/main/java/org/jboss/weld/bootstrap/api/Environment.java#L48-L70"><code>org.jboss.weld.bootstrap.api.Environment</code></a> allows implementors to override a specific method which will then prevent Weld from handling these events.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="/download/">Download</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/5.0.0.CR2/en-US/html_single/" target="_blank" rel="noopener">Documentation</a> &#93;
+                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12382781" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2022/02/23/weld-500CR1/">Weld 5.0.0.CR1</a>
@@ -1093,104 +1129,6 @@ <h2 id="_wildfly_patch">WildFly Patch</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2020/09/18/weld-400Beta1/">Weld 4.0.0.Beta1</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2020-9-18
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/release">release</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Matej Novotny
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>A new Weld 4 release is now available!
-                  Latest core version is now 4.0.0.Beta1 and Weld API that ships with it is 4.0.Beta1.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>I will not be listing links to issues as usual, because I think more important work was done outside of JIRA tracking this time (although you can check the issues <a href="https://issues.redhat.com/projects/WELD/versions/12346364">here</a>).
-                  Instead, let me sum it up in a short list of noticeable changes:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>All Weld bits are now present in Maven Central</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Including servlet core (and shaded) which had to be left out last time</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>We are able to execute CDI TCKs in EE 9 environment once again and it&#8217;s all passing</p>
-                  </li>
-                  <li>
-                  <p>We are now able to test servlets with Tomcats and Undertow</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Jetty testing is not possible yet because there is no <a href="https://github.com/arquillian/arquillian-container-jetty/issues/43">Arquillian adapter</a> for it yet</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Reworked documentation generation tooling</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Weld docs now have similar look to those of CDI and are distributed in either PDF or single page HTML format</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Did some updates on Javadoc generation in API and Core if generated with JDK 11</p>
-                  </li>
-                  <li>
-                  <p>Big update pass on tooling and dependencies</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>We are now using Dependabot and have bumped almost every dependency and tooling in the project</p>
-                  </li>
-                  <li>
-                  <p>Which also led to nice cleanup and fixing of several issues</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>On top of that, every bugfix that would go into Weld 3 is of course being added to Weld 4 as well so those aren&#8217;t missing either!</p>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_wildfly_patch">WildFly Patch</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>Sadly we cannot provide a patch for WildFly as there is not yet any official release that would support EE 9.
-                  As soon as there is one, we will surely follow up with Weld patch!</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>&#91; <a href="/download/">Download</a> &#93;
-                  &#91; <a href="http://docs.jboss.org/weld/reference/4.0.0.Beta1/en-US/html_single/" target="_blank" rel="noopener">Documentation</a> &#93;
-                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12346364" target="_blank" rel="noopener">Release notes</a> &#93;</p>
-                  </div>
-                  </div>
-                  </div>
-                </div>
-                <hr>
-              </div>
               <div class="pagination-links"><a href="/news/tags/release/" class="previous-link">Previous</a> <a href="/news/tags/release/" class="page-link">1</a> <span class="current-page">2</span> <a href="/news/tags/release/page/3.html" class="page-link">3</a> <span class="skip">...</span><a href="/news/tags/release/page/5.html" class="page-link">5</a> <a href="/news/tags/release/page/6.html" class="page-link">6</a> <a href="/news/tags/release/page/3.html" class="next-link">Next</a> </div>
               <hr>
               <div>
diff --git a/news/tags/release/page/3.html b/news/tags/release/page/3.html
index af1c60be..e613d69c 100644
--- a/news/tags/release/page/3.html
+++ b/news/tags/release/page/3.html
@@ -141,6 +141,104 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2020/09/18/weld-400Beta1/">Weld 4.0.0.Beta1</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2020-9-18
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/release">release</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Matej Novotny
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>A new Weld 4 release is now available!
+                  Latest core version is now 4.0.0.Beta1 and Weld API that ships with it is 4.0.Beta1.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>I will not be listing links to issues as usual, because I think more important work was done outside of JIRA tracking this time (although you can check the issues <a href="https://issues.redhat.com/projects/WELD/versions/12346364">here</a>).
+                  Instead, let me sum it up in a short list of noticeable changes:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>All Weld bits are now present in Maven Central</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Including servlet core (and shaded) which had to be left out last time</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>We are able to execute CDI TCKs in EE 9 environment once again and it&#8217;s all passing</p>
+                  </li>
+                  <li>
+                  <p>We are now able to test servlets with Tomcats and Undertow</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Jetty testing is not possible yet because there is no <a href="https://github.com/arquillian/arquillian-container-jetty/issues/43">Arquillian adapter</a> for it yet</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Reworked documentation generation tooling</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Weld docs now have similar look to those of CDI and are distributed in either PDF or single page HTML format</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Did some updates on Javadoc generation in API and Core if generated with JDK 11</p>
+                  </li>
+                  <li>
+                  <p>Big update pass on tooling and dependencies</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>We are now using Dependabot and have bumped almost every dependency and tooling in the project</p>
+                  </li>
+                  <li>
+                  <p>Which also led to nice cleanup and fixing of several issues</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>On top of that, every bugfix that would go into Weld 3 is of course being added to Weld 4 as well so those aren&#8217;t missing either!</p>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_wildfly_patch">WildFly Patch</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>Sadly we cannot provide a patch for WildFly as there is not yet any official release that would support EE 9.
+                  As soon as there is one, we will surely follow up with Weld patch!</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="/download/">Download</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/4.0.0.Beta1/en-US/html_single/" target="_blank" rel="noopener">Documentation</a> &#93;
+                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12346364" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2020/08/12/weld-315Final/">Weld 3.1.5.Final</a>
@@ -1307,199 +1405,6 @@ <h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2018/04/26/weld-304Final/">Weld 3.0.4.Final</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2018-4-26
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/release">release</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Matej Novotny
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>Weld 3.0.4.Final is here along with Weld API 3.0.SP3 - make sure you update both.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>In this release we took first steps towards eliminating illegal access in JDK 10+.
-                  The good news is, Weld should now be able to run with <code>--illegal-access=deny</code>.
-                  The project and CI infrastructure around it went through a lot of changes to be able to build and execute on JDK 10 and there is still more to come.
-                  There are also numerous optimizations - <code>beans.xml</code> parsing, AT identifier representation, optional memory savings.
-                  And of course, bug fixes, so let us take a look at all of it.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Noticeable amount of reports, suggestions and even fixes came from the community - for that you have our thanks (and a new version of Weld of course)!</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Fixes and improvements:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Weld Core</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Correct proxy generation for class hierarchy with abstract class and generics (<a href="https://issues.jboss.org/browse/WELD-2470" target="_blank" rel="noopener">WELD-2470</a>)</p>
-                  </li>
-                  <li>
-                  <p>Opt-in enhancement in HTTP session replication, more eager approach (<a href="https://issues.jboss.org/browse/WELD-1130" target="_blank" rel="noopener">WELD-1130</a>)</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Note that WildFly does not need or use this</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Fix NPE which could occur with <code>SecurityManager</code> if <code>getPermissions()</code> returned <code>null</code> (<a href="https://issues.jboss.org/browse/WELD-2464" target="_blank" rel="noopener">WELD-2464</a>)</p>
-                  </li>
-                  <li>
-                  <p>Relax bean type check in <code>BeanManager.getInjectableReference()</code> (<a href="https://issues.jboss.org/browse/WELD-2466" target="_blank" rel="noopener">WELD-2466</a>)</p>
-                  </li>
-                  <li>
-                  <p><code>AfterTypeDiscovery</code> did not allow to remove declared interceptors/decorators/alternatives correctly (<a href="https://issues.jboss.org/browse/WELD-2479" target="_blank" rel="noopener">WELD-2479</a>)</p>
-                  </li>
-                  <li>
-                  <p>Two globally selected alternatives with the same priority should result in ambiguous dependency (<a href="https://issues.jboss.org/browse/WELD-2482" target="_blank" rel="noopener">WELD-2482</a>)</p>
-                  </li>
-                  <li>
-                  <p><code>Configurator</code> SPI now uses sensible <code>toString()</code> so that user can tell what went wrong (<a href="https://issues.jboss.org/browse/WELD-2484" target="_blank" rel="noopener">WELD-2484</a>)</p>
-                  </li>
-                  <li>
-                  <p>Improve performance of <code>beans.xml</code> parsing (<a href="https://issues.jboss.org/browse/WELD-2469" target="_blank" rel="noopener">WELD-2469</a>)</p>
-                  </li>
-                  <li>
-                  <p>Introduce an optional configuration allowing Weld to perform cleanup after boot (<a href="https://issues.jboss.org/browse/WELD-2457" target="_blank" rel="noopener">WELD-2457</a> and <a href="https://issues.jboss.org/browse/WELD-2475" target="_blank" rel="noopener">WELD-2475</a>)</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>In EE servers, if integrators meet certain conditions and allow for this, Weld can them drop metadata from some beans which will not be used in runtime</p>
-                  </li>
-                  <li>
-                  <p>See <em>Docs</em> section for links</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Optimise <code>String</code> representation of <code>AnnotatedTypeIdentifier</code> (<a href="https://issues.jboss.org/browse/WELD-2477" target="_blank" rel="noopener">WELD-2477</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Weld SE</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Fix NPE which could occur if trying to intercept a method called by constructor (<a href="https://issues.jboss.org/browse/WELD-2478" target="_blank" rel="noopener">WELD-2478</a> and <a href="https://issues.jboss.org/browse/WELD-2473" target="_blank" rel="noopener">WELD-2473</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>JDK 9/10 and onwards (<a href="https://issues.jboss.org/browse/WELD-2460" target="_blank" rel="noopener">WELD-2460</a>)</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Weld uses JDK&#8217;s internal BCEL classes (<a href="https://issues.jboss.org/browse/WELD-2490" target="_blank" rel="noopener">WELD-2490</a>)</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>This is only used to report errors in generated bytecode on proxies/subclasses</p>
-                  </li>
-                  <li>
-                  <p>We added a dependency on <code>org.apache.bcel:bcel</code> which enables this functionality without reflective access to internal libraries</p>
-                  </li>
-                  <li>
-                  <p>In order to keep Weld&#8217;s footprint minimal, this dependency is optional only</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Upgrade JBoss Classfilewriter to 1.2.2.Final (<a href="https://issues.jboss.org/browse/WELD-2487" target="_blank" rel="noopener">WELD-2487</a>)</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Eliminates another bunch of illegal access problems</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Probe development tool</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Probe now uses JDK-agnostic <code>Annotation.toString()</code> version (<a href="https://issues.jboss.org/browse/WELD-2463" target="_blank" rel="noopener">WELD-2463</a>)</p>
-                  </li>
-                  <li>
-                  <p>Correction to licences in Probe (<a href="https://issues.jboss.org/browse/WELD-2480" target="_blank" rel="noopener">WELD-2480</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Docs</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p><code>WeldTerminalListener</code> had wrong FQCN in our documentation which resulted in errors when trying to use it in Tomcat (<a href="https://issues.jboss.org/browse/WELD-2486" target="_blank" rel="noopener">WELD-2486</a>)</p>
-                  </li>
-                  <li>
-                  <p>Newly added memory-saving option <code>ConfigurationKey.ALLOW_OPTIMIZED_CLEANUP</code> is documented (<a href="https://issues.jboss.org/browse/WELD-2472" target="_blank" rel="noopener">WELD-2472</a>)</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>If you wish to learn more, please glance <a href="http://docs.jboss.org/weld/reference/3.0.4.Final/en-US/html_single/#remove-unused-beans" target="_blank" rel="noopener">here</a></p>
-                  </li>
-                  <li>
-                  <p>Please note that integrator has to allow for this optimization, otherwise your settings won&#8217;t count (<em>psst, WildFly 12 allows this!</em>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_wildfly_patch">WildFly Patch</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>As usual, a <a href="http://download.jboss.org/weld/3.0.4.Final/wildfly-12.0.0.Final-weld-3.0.4.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly 12.0.0.Final</a> is available.
-                  Please note that Weld 3.0.4.Final will still allow you to boot up WildFly in either EE 7 or EE 8 mode, whichever you prefer.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>If this is the first time you hear about EE 8 mode for WildFly, check <a href="http://wildfly.org/news/2018/02/28/WildFly12-Final-Released" target="_blank" rel="noopener">this post</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>If you’re not familiar with patching WildFly, check the <a href="/documentation/#12">FAQ</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>&#91; <a href="/download/">Download</a> &#93;
-                  &#91; <a href="http://docs.jboss.org/weld/reference/3.0.4.Final/en-US/html/" target="_blank" rel="noopener">Documentation</a> &#93;
-                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12336871" target="_blank" rel="noopener">Release notes</a> &#93;</p>
-                  </div>
-                  </div>
-                  </div>
-                </div>
-                <hr>
-              </div>
               <div class="pagination-links"><a href="/news/tags/release/page/2.html" class="previous-link">Previous</a> <a href="/news/tags/release/" class="page-link">1</a> <a href="/news/tags/release/page/2.html" class="page-link">2</a> <span class="current-page">3</span> <a href="/news/tags/release/page/4.html" class="page-link">4</a> <a href="/news/tags/release/page/5.html" class="page-link">5</a> <a href="/news/tags/release/page/6.html" class="page-link">6</a> <a href="/news/tags/release/page/4.html" class="next-link">Next</a> </div>
               <hr>
               <div>
diff --git a/news/tags/release/page/4.html b/news/tags/release/page/4.html
index 7f5688c7..84ba1cca 100644
--- a/news/tags/release/page/4.html
+++ b/news/tags/release/page/4.html
@@ -141,6 +141,199 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2018/04/26/weld-304Final/">Weld 3.0.4.Final</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2018-4-26
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/release">release</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Matej Novotny
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>Weld 3.0.4.Final is here along with Weld API 3.0.SP3 - make sure you update both.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>In this release we took first steps towards eliminating illegal access in JDK 10+.
+                  The good news is, Weld should now be able to run with <code>--illegal-access=deny</code>.
+                  The project and CI infrastructure around it went through a lot of changes to be able to build and execute on JDK 10 and there is still more to come.
+                  There are also numerous optimizations - <code>beans.xml</code> parsing, AT identifier representation, optional memory savings.
+                  And of course, bug fixes, so let us take a look at all of it.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Noticeable amount of reports, suggestions and even fixes came from the community - for that you have our thanks (and a new version of Weld of course)!</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Fixes and improvements:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Weld Core</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Correct proxy generation for class hierarchy with abstract class and generics (<a href="https://issues.jboss.org/browse/WELD-2470" target="_blank" rel="noopener">WELD-2470</a>)</p>
+                  </li>
+                  <li>
+                  <p>Opt-in enhancement in HTTP session replication, more eager approach (<a href="https://issues.jboss.org/browse/WELD-1130" target="_blank" rel="noopener">WELD-1130</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Note that WildFly does not need or use this</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Fix NPE which could occur with <code>SecurityManager</code> if <code>getPermissions()</code> returned <code>null</code> (<a href="https://issues.jboss.org/browse/WELD-2464" target="_blank" rel="noopener">WELD-2464</a>)</p>
+                  </li>
+                  <li>
+                  <p>Relax bean type check in <code>BeanManager.getInjectableReference()</code> (<a href="https://issues.jboss.org/browse/WELD-2466" target="_blank" rel="noopener">WELD-2466</a>)</p>
+                  </li>
+                  <li>
+                  <p><code>AfterTypeDiscovery</code> did not allow to remove declared interceptors/decorators/alternatives correctly (<a href="https://issues.jboss.org/browse/WELD-2479" target="_blank" rel="noopener">WELD-2479</a>)</p>
+                  </li>
+                  <li>
+                  <p>Two globally selected alternatives with the same priority should result in ambiguous dependency (<a href="https://issues.jboss.org/browse/WELD-2482" target="_blank" rel="noopener">WELD-2482</a>)</p>
+                  </li>
+                  <li>
+                  <p><code>Configurator</code> SPI now uses sensible <code>toString()</code> so that user can tell what went wrong (<a href="https://issues.jboss.org/browse/WELD-2484" target="_blank" rel="noopener">WELD-2484</a>)</p>
+                  </li>
+                  <li>
+                  <p>Improve performance of <code>beans.xml</code> parsing (<a href="https://issues.jboss.org/browse/WELD-2469" target="_blank" rel="noopener">WELD-2469</a>)</p>
+                  </li>
+                  <li>
+                  <p>Introduce an optional configuration allowing Weld to perform cleanup after boot (<a href="https://issues.jboss.org/browse/WELD-2457" target="_blank" rel="noopener">WELD-2457</a> and <a href="https://issues.jboss.org/browse/WELD-2475" target="_blank" rel="noopener">WELD-2475</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>In EE servers, if integrators meet certain conditions and allow for this, Weld can them drop metadata from some beans which will not be used in runtime</p>
+                  </li>
+                  <li>
+                  <p>See <em>Docs</em> section for links</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Optimise <code>String</code> representation of <code>AnnotatedTypeIdentifier</code> (<a href="https://issues.jboss.org/browse/WELD-2477" target="_blank" rel="noopener">WELD-2477</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Weld SE</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Fix NPE which could occur if trying to intercept a method called by constructor (<a href="https://issues.jboss.org/browse/WELD-2478" target="_blank" rel="noopener">WELD-2478</a> and <a href="https://issues.jboss.org/browse/WELD-2473" target="_blank" rel="noopener">WELD-2473</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>JDK 9/10 and onwards (<a href="https://issues.jboss.org/browse/WELD-2460" target="_blank" rel="noopener">WELD-2460</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Weld uses JDK&#8217;s internal BCEL classes (<a href="https://issues.jboss.org/browse/WELD-2490" target="_blank" rel="noopener">WELD-2490</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>This is only used to report errors in generated bytecode on proxies/subclasses</p>
+                  </li>
+                  <li>
+                  <p>We added a dependency on <code>org.apache.bcel:bcel</code> which enables this functionality without reflective access to internal libraries</p>
+                  </li>
+                  <li>
+                  <p>In order to keep Weld&#8217;s footprint minimal, this dependency is optional only</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Upgrade JBoss Classfilewriter to 1.2.2.Final (<a href="https://issues.jboss.org/browse/WELD-2487" target="_blank" rel="noopener">WELD-2487</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Eliminates another bunch of illegal access problems</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Probe development tool</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Probe now uses JDK-agnostic <code>Annotation.toString()</code> version (<a href="https://issues.jboss.org/browse/WELD-2463" target="_blank" rel="noopener">WELD-2463</a>)</p>
+                  </li>
+                  <li>
+                  <p>Correction to licences in Probe (<a href="https://issues.jboss.org/browse/WELD-2480" target="_blank" rel="noopener">WELD-2480</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Docs</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p><code>WeldTerminalListener</code> had wrong FQCN in our documentation which resulted in errors when trying to use it in Tomcat (<a href="https://issues.jboss.org/browse/WELD-2486" target="_blank" rel="noopener">WELD-2486</a>)</p>
+                  </li>
+                  <li>
+                  <p>Newly added memory-saving option <code>ConfigurationKey.ALLOW_OPTIMIZED_CLEANUP</code> is documented (<a href="https://issues.jboss.org/browse/WELD-2472" target="_blank" rel="noopener">WELD-2472</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>If you wish to learn more, please glance <a href="http://docs.jboss.org/weld/reference/3.0.4.Final/en-US/html_single/#remove-unused-beans" target="_blank" rel="noopener">here</a></p>
+                  </li>
+                  <li>
+                  <p>Please note that integrator has to allow for this optimization, otherwise your settings won&#8217;t count (<em>psst, WildFly 12 allows this!</em>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_wildfly_patch">WildFly Patch</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>As usual, a <a href="http://download.jboss.org/weld/3.0.4.Final/wildfly-12.0.0.Final-weld-3.0.4.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly 12.0.0.Final</a> is available.
+                  Please note that Weld 3.0.4.Final will still allow you to boot up WildFly in either EE 7 or EE 8 mode, whichever you prefer.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>If this is the first time you hear about EE 8 mode for WildFly, check <a href="http://wildfly.org/news/2018/02/28/WildFly12-Final-Released" target="_blank" rel="noopener">this post</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>If you’re not familiar with patching WildFly, check the <a href="/documentation/#12">FAQ</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="/download/">Download</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/3.0.4.Final/en-US/html/" target="_blank" rel="noopener">Documentation</a> &#93;
+                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12336871" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2018/03/20/weld-247Final/">Weld 2.4.7.Final</a>
@@ -1247,112 +1440,6 @@ <h2 id="_wildfly_patch">WildFly Patch</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2017/03/03/weld-300CR2/">Weld 3.0.0.CR2</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2017-3-3
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/release">release</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Martin Kouba
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>I am very pleased to announce the release of Weld <strong>3.0.0.CR2</strong> (<strong>CDI 2.0-PFD</strong>).
-                  The intention is to provide the latest updates so that early adopters and reviewers can work with up-to-date reference implementation during the JCP review process.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Notable fixes and improvements:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p><code>InterceptionFactory</code> handles interface correctly (<a href="https://issues.jboss.org/browse/WELD-2335" target="_blank" rel="noopener">WELD-2335</a>)</p>
-                  </li>
-                  <li>
-                  <p>Enable to obtain <code>InjectionPoint</code> metadata from within <code>BeanConfigurator#produceWith()</code> (<a href="https://issues.jboss.org/browse/WELD-2333" target="_blank" rel="noopener">WELD-2333</a>)</p>
-                  </li>
-                  <li>
-                  <p><code>ObserverMethodConfigurator.beanClass()</code> should be preset to the extension class (<a href="https://issues.jboss.org/browse/WELD-2324" target="_blank" rel="noopener">WELD-2324</a>)</p>
-                  </li>
-                  <li>
-                  <p>Performance improvements in <code>javax.enterprise.inject.Instance</code> implementation (<a href="https://issues.jboss.org/browse/WELD-2322" target="_blank" rel="noopener">WELD-2322</a> and <a href="https://issues.jboss.org/browse/WELD-2323" target="_blank" rel="noopener">WELD-2323</a>)</p>
-                  </li>
-                  <li>
-                  <p>Don&#8217;t include built-in session and conversation scoped beans in the bean identifier index (<a href="https://issues.jboss.org/browse/WELD-2343" target="_blank" rel="noopener">WELD-2343</a>)</p>
-                  </li>
-                  <li>
-                  <p>Support <code>InjectionPoint</code> metadata injected into dependent singleton session bean (<a href="https://issues.jboss.org/browse/WELD-2341" target="_blank" rel="noopener">WELD-2341</a>)</p>
-                  </li>
-                  <li>
-                  <p>Logging</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Log DEBUG info about important phases during bootstrap (<a href="https://issues.jboss.org/browse/WELD-2336" target="_blank" rel="noopener">WELD-2336</a>)</p>
-                  </li>
-                  <li>
-                  <p>Fix the error message when an extension observer method is static (<a href="https://issues.jboss.org/browse/WELD-2331" target="_blank" rel="noopener">WELD-2331</a>)</p>
-                  </li>
-                  <li>
-                  <p>Improved transactional observer methods logging in case of failure (<a href="https://issues.jboss.org/browse/WELD-2330" target="_blank" rel="noopener">WELD-2330</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Weld SE - <code>ContainerInitialized</code> should be fired after the container is initialized and shutdown hook is registered (<a href="https://issues.jboss.org/browse/WELD-2340" target="_blank" rel="noopener">WELD-2340</a>)</p>
-                  </li>
-                  <li>
-                  <p>Probe development tool</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Extended bean archive info</p>
-                  </li>
-                  <li>
-                  <p>Monitor bean instance creation</p>
-                  </li>
-                  <li>
-                  <p>Do not mark a bean as unused if only injected into an observer method or disposer method</p>
-                  </li>
-                  <li>
-                  <p><code>org.jboss.weld.probe</code> package is vetoed</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>See also <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12333159" target="_blank" rel="noopener">the release details</a>.
-                  Thanks to everyone involved in this release!</p>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_wildfly_patch">WildFly Patch</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>As usual, a <a href="http://download.jboss.org/weld/3.0.0.CR2/wildfly-10.1.0.Final-weld-3.0.0.CR2-patch.zip" target="_blank" rel="noopener">patch for WildFly</a> is available.
-                  This time the target platform is <strong>WildFly 10.1.0.Final</strong>.
-                  If you’re not familiar with patching WildFly, check the <a href="/documentation/#12">FAQ</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>&#91; <a href="/download/">Download</a> &#93;
-                  &#91; <a href="http://docs.jboss.org/weld/reference/3.0.0.CR2/en-US/html/" target="_blank" rel="noopener">Documentation</a> &#93;
-                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12333159" target="_blank" rel="noopener">Release notes</a> &#93;</p>
-                  </div>
-                  </div>
-                  </div>
-                </div>
-                <hr>
-              </div>
               <div class="pagination-links"><a href="/news/tags/release/page/3.html" class="previous-link">Previous</a> <a href="/news/tags/release/" class="page-link">1</a> <a href="/news/tags/release/page/2.html" class="page-link">2</a> <a href="/news/tags/release/page/3.html" class="page-link">3</a> <span class="current-page">4</span> <a href="/news/tags/release/page/5.html" class="page-link">5</a> <a href="/news/tags/release/page/6.html" class="page-link">6</a> <a href="/news/tags/release/page/5.html" class="next-link">Next</a> </div>
               <hr>
               <div>
diff --git a/news/tags/release/page/5.html b/news/tags/release/page/5.html
index 17a2edbb..ced5621f 100644
--- a/news/tags/release/page/5.html
+++ b/news/tags/release/page/5.html
@@ -141,6 +141,112 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2017/03/03/weld-300CR2/">Weld 3.0.0.CR2</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2017-3-3
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/release">release</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Martin Kouba
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>I am very pleased to announce the release of Weld <strong>3.0.0.CR2</strong> (<strong>CDI 2.0-PFD</strong>).
+                  The intention is to provide the latest updates so that early adopters and reviewers can work with up-to-date reference implementation during the JCP review process.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Notable fixes and improvements:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p><code>InterceptionFactory</code> handles interface correctly (<a href="https://issues.jboss.org/browse/WELD-2335" target="_blank" rel="noopener">WELD-2335</a>)</p>
+                  </li>
+                  <li>
+                  <p>Enable to obtain <code>InjectionPoint</code> metadata from within <code>BeanConfigurator#produceWith()</code> (<a href="https://issues.jboss.org/browse/WELD-2333" target="_blank" rel="noopener">WELD-2333</a>)</p>
+                  </li>
+                  <li>
+                  <p><code>ObserverMethodConfigurator.beanClass()</code> should be preset to the extension class (<a href="https://issues.jboss.org/browse/WELD-2324" target="_blank" rel="noopener">WELD-2324</a>)</p>
+                  </li>
+                  <li>
+                  <p>Performance improvements in <code>javax.enterprise.inject.Instance</code> implementation (<a href="https://issues.jboss.org/browse/WELD-2322" target="_blank" rel="noopener">WELD-2322</a> and <a href="https://issues.jboss.org/browse/WELD-2323" target="_blank" rel="noopener">WELD-2323</a>)</p>
+                  </li>
+                  <li>
+                  <p>Don&#8217;t include built-in session and conversation scoped beans in the bean identifier index (<a href="https://issues.jboss.org/browse/WELD-2343" target="_blank" rel="noopener">WELD-2343</a>)</p>
+                  </li>
+                  <li>
+                  <p>Support <code>InjectionPoint</code> metadata injected into dependent singleton session bean (<a href="https://issues.jboss.org/browse/WELD-2341" target="_blank" rel="noopener">WELD-2341</a>)</p>
+                  </li>
+                  <li>
+                  <p>Logging</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Log DEBUG info about important phases during bootstrap (<a href="https://issues.jboss.org/browse/WELD-2336" target="_blank" rel="noopener">WELD-2336</a>)</p>
+                  </li>
+                  <li>
+                  <p>Fix the error message when an extension observer method is static (<a href="https://issues.jboss.org/browse/WELD-2331" target="_blank" rel="noopener">WELD-2331</a>)</p>
+                  </li>
+                  <li>
+                  <p>Improved transactional observer methods logging in case of failure (<a href="https://issues.jboss.org/browse/WELD-2330" target="_blank" rel="noopener">WELD-2330</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Weld SE - <code>ContainerInitialized</code> should be fired after the container is initialized and shutdown hook is registered (<a href="https://issues.jboss.org/browse/WELD-2340" target="_blank" rel="noopener">WELD-2340</a>)</p>
+                  </li>
+                  <li>
+                  <p>Probe development tool</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Extended bean archive info</p>
+                  </li>
+                  <li>
+                  <p>Monitor bean instance creation</p>
+                  </li>
+                  <li>
+                  <p>Do not mark a bean as unused if only injected into an observer method or disposer method</p>
+                  </li>
+                  <li>
+                  <p><code>org.jboss.weld.probe</code> package is vetoed</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>See also <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12333159" target="_blank" rel="noopener">the release details</a>.
+                  Thanks to everyone involved in this release!</p>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_wildfly_patch">WildFly Patch</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>As usual, a <a href="http://download.jboss.org/weld/3.0.0.CR2/wildfly-10.1.0.Final-weld-3.0.0.CR2-patch.zip" target="_blank" rel="noopener">patch for WildFly</a> is available.
+                  This time the target platform is <strong>WildFly 10.1.0.Final</strong>.
+                  If you’re not familiar with patching WildFly, check the <a href="/documentation/#12">FAQ</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="/download/">Download</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/3.0.0.CR2/en-US/html/" target="_blank" rel="noopener">Documentation</a> &#93;
+                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12333159" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2017/02/02/weld-242Final/">Weld 2.4.2.Final</a>
@@ -1071,88 +1177,6 @@ <h2 id="_wildfly_patch">WildFly Patch</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2016/02/12/weld-233Final/">Weld 2.3.3.Final</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2016-2-12
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/release">release</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Martin Kouba
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>Weld 2.3.3.Final the next bug-fix version of the stable 2.3 branch has been released!
-                  See also <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12328954" target="_blank" rel="noopener">the release details</a>.
-                  Thanks to everyone involved in this release!
-                  Notable improvements:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>allow to proxy classes with non-static non-private final methods</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>this is a non-portable way to get around the <a href="http://docs.jboss.org/cdi/spec/1.2/cdi-spec.html#unproxyable" target="_blank" rel="noopener">CDI spec restrictions</a>, see also <a href="http://docs.jboss.org/weld/reference/2.3.3.Final/en-US/html/configure.html#_proxying_classes_with_final_methods" target="_blank" rel="noopener">Proxying classes with final methods</a> and <a href="https://issues.jboss.org/browse/CDI-527" target="_blank" rel="noopener">CDI-527</a></p>
-                  </li>
-                  <li>
-                  <p><strong>use with caution!</strong></p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>other enhancements and bug-fixes around proxies:</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>better support for DeltaSpike partial beans (<a href="https://issues.jboss.org/browse/WELD-2084" target="_blank" rel="noopener">WELD-2084</a>)</p>
-                  </li>
-                  <li>
-                  <p>better support for Camel CDI (<a href="https://issues.jboss.org/browse/WELD-2089" target="_blank" rel="noopener">WELD-2089</a>)</p>
-                  </li>
-                  <li>
-                  <p>better support for proxies with non public classes (<a href="https://issues.jboss.org/browse/WELD-2091" target="_blank" rel="noopener">WELD-2091</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Weld Probe has a slightly redesigned menu and a new Dashboard view with some basic stats</p>
-                  </li>
-                  <li>
-                  <p>the decorator validation was improved (<a href="https://issues.jboss.org/browse/WELD-2085" target="_blank" rel="noopener">WELD-2085</a>, <a href="https://issues.jboss.org/browse/WELD-1811" target="_blank" rel="noopener">WELD-1811</a>, <a href="https://issues.jboss.org/browse/WELD-2039" target="_blank" rel="noopener">WELD-2039</a>)</p>
-                  </li>
-                  <li>
-                  <p>minor SPI cleanup was performed  (<a href="https://issues.jboss.org/browse/WELD-2077" target="_blank" rel="noopener">WELD-2077</a>, <a href="https://issues.jboss.org/browse/WELD-2079" target="_blank" rel="noopener">WELD-2079</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_wildfly_patch">WildFly Patch</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>As usual, a <a href="http://download.jboss.org/weld/2.3.3.Final/wildfly-10.0.0.Final-weld-2.3.3.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly</a> is available. This time the target platform is <strong>WildFly 10.0.0.Final</strong>.  If you’re not familiar with patching WildFly, check <a href="http://blog.eisele.net/2015/02/playing-with-weld-probe-see-all-of-your.html" target="_blank" rel="noopener">Markus&#8217;s tutorial</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>&#91; <a href="http://docs.jboss.org/cdi/api/1.2/" target="_blank" rel="noopener">CDI 1.2 API</a> &#93;
-                  &#91; <a href="/download/">Download</a> &#93;
-                  &#91; <a href="http://docs.jboss.org/weld/reference/2.3.3.Final/en-US/html/" target="_blank" rel="noopener">Documentation</a> &#93;
-                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12328954" target="_blank" rel="noopener">Release notes</a> &#93;</p>
-                  </div>
-                  </div>
-                  </div>
-                </div>
-                <hr>
-              </div>
               <div class="pagination-links"><a href="/news/tags/release/page/4.html" class="previous-link">Previous</a> <a href="/news/tags/release/" class="page-link">1</a> <a href="/news/tags/release/page/2.html" class="page-link">2</a> <span class="skip">...</span><a href="/news/tags/release/page/4.html" class="page-link">4</a> <span class="current-page">5</span> <a href="/news/tags/release/page/6.html" class="page-link">6</a> <a href="/news/tags/release/page/6.html" class="next-link">Next</a> </div>
               <hr>
               <div>
diff --git a/news/tags/release/page/6.html b/news/tags/release/page/6.html
index 51c41811..0c14d939 100644
--- a/news/tags/release/page/6.html
+++ b/news/tags/release/page/6.html
@@ -141,6 +141,88 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2016/02/12/weld-233Final/">Weld 2.3.3.Final</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2016-2-12
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/release">release</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Martin Kouba
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>Weld 2.3.3.Final the next bug-fix version of the stable 2.3 branch has been released!
+                  See also <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12328954" target="_blank" rel="noopener">the release details</a>.
+                  Thanks to everyone involved in this release!
+                  Notable improvements:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>allow to proxy classes with non-static non-private final methods</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>this is a non-portable way to get around the <a href="http://docs.jboss.org/cdi/spec/1.2/cdi-spec.html#unproxyable" target="_blank" rel="noopener">CDI spec restrictions</a>, see also <a href="http://docs.jboss.org/weld/reference/2.3.3.Final/en-US/html/configure.html#_proxying_classes_with_final_methods" target="_blank" rel="noopener">Proxying classes with final methods</a> and <a href="https://issues.jboss.org/browse/CDI-527" target="_blank" rel="noopener">CDI-527</a></p>
+                  </li>
+                  <li>
+                  <p><strong>use with caution!</strong></p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>other enhancements and bug-fixes around proxies:</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>better support for DeltaSpike partial beans (<a href="https://issues.jboss.org/browse/WELD-2084" target="_blank" rel="noopener">WELD-2084</a>)</p>
+                  </li>
+                  <li>
+                  <p>better support for Camel CDI (<a href="https://issues.jboss.org/browse/WELD-2089" target="_blank" rel="noopener">WELD-2089</a>)</p>
+                  </li>
+                  <li>
+                  <p>better support for proxies with non public classes (<a href="https://issues.jboss.org/browse/WELD-2091" target="_blank" rel="noopener">WELD-2091</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Weld Probe has a slightly redesigned menu and a new Dashboard view with some basic stats</p>
+                  </li>
+                  <li>
+                  <p>the decorator validation was improved (<a href="https://issues.jboss.org/browse/WELD-2085" target="_blank" rel="noopener">WELD-2085</a>, <a href="https://issues.jboss.org/browse/WELD-1811" target="_blank" rel="noopener">WELD-1811</a>, <a href="https://issues.jboss.org/browse/WELD-2039" target="_blank" rel="noopener">WELD-2039</a>)</p>
+                  </li>
+                  <li>
+                  <p>minor SPI cleanup was performed  (<a href="https://issues.jboss.org/browse/WELD-2077" target="_blank" rel="noopener">WELD-2077</a>, <a href="https://issues.jboss.org/browse/WELD-2079" target="_blank" rel="noopener">WELD-2079</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_wildfly_patch">WildFly Patch</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>As usual, a <a href="http://download.jboss.org/weld/2.3.3.Final/wildfly-10.0.0.Final-weld-2.3.3.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly</a> is available. This time the target platform is <strong>WildFly 10.0.0.Final</strong>.  If you’re not familiar with patching WildFly, check <a href="http://blog.eisele.net/2015/02/playing-with-weld-probe-see-all-of-your.html" target="_blank" rel="noopener">Markus&#8217;s tutorial</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="http://docs.jboss.org/cdi/api/1.2/" target="_blank" rel="noopener">CDI 1.2 API</a> &#93;
+                  &#91; <a href="/download/">Download</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/2.3.3.Final/en-US/html/" target="_blank" rel="noopener">Documentation</a> &#93;
+                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12328954" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2016/02/04/weld-300Alpha15/">Weld 3.0.0.Alpha15</a>
diff --git a/sitemap.xml b/sitemap.xml
index 75468cdd..9f778b6a 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -2,37 +2,37 @@
 <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
   <url>
     <loc>https://weld.cdi-spec.org/bug/</loc>
-    <lastmod>2023-10-05</lastmod>
+    <lastmod>2023-10-26</lastmod>
     <priority>0.5</priority>
     <changefreq>weekly</changefreq>
   </url>
   <url>
     <loc>https://weld.cdi-spec.org/community/</loc>
-    <lastmod>2023-10-05</lastmod>
+    <lastmod>2023-10-26</lastmod>
     <priority>0.5</priority>
     <changefreq>weekly</changefreq>
   </url>
   <url>
     <loc>https://weld.cdi-spec.org/dist/</loc>
-    <lastmod>2023-10-05</lastmod>
+    <lastmod>2023-10-26</lastmod>
     <priority>1</priority>
     <changefreq>daily</changefreq>
   </url>
   <url>
     <loc>https://weld.cdi-spec.org/documentation/</loc>
-    <lastmod>2023-10-05</lastmod>
+    <lastmod>2023-10-26</lastmod>
     <priority>0.5</priority>
     <changefreq>weekly</changefreq>
   </url>
   <url>
     <loc>https://weld.cdi-spec.org/download/</loc>
-    <lastmod>2023-10-05</lastmod>
+    <lastmod>2023-10-26</lastmod>
     <priority>0.5</priority>
     <changefreq>weekly</changefreq>
   </url>
   <url>
     <loc>https://weld.cdi-spec.org/</loc>
-    <lastmod>2023-10-05</lastmod>
+    <lastmod>2023-10-26</lastmod>
     <priority>0.5</priority>
     <changefreq>weekly</changefreq>
   </url>
@@ -564,9 +564,15 @@
     <priority>1</priority>
     <changefreq>weekly</changefreq>
   </url>
+  <url>
+    <loc>https://weld.cdi-spec.org/news/2023/10/26/weld-600Alpha1/</loc>
+    <lastmod>2023-10-26</lastmod>
+    <priority>1</priority>
+    <changefreq>weekly</changefreq>
+  </url>
   <url>
     <loc>https://weld.cdi-spec.org/news/</loc>
-    <lastmod>2023-10-05</lastmod>
+    <lastmod>2023-10-26</lastmod>
     <priority>1</priority>
     <changefreq>daily</changefreq>
   </url>