From a9187f2200d6e3f42f550c8ebb9e4db286895474 Mon Sep 17 00:00:00 2001
From: Matej Novotny <manovotn@redhat.com>
Date: Mon, 16 Dec 2024 12:44:24 +0000
Subject: [PATCH] Published master to GitHub pages.

---
 dist/index.html                          |  23 ++
 download/index.html                      |  48 ++--
 index.html                               |  30 +--
 news.atom                                | 317 +++++++++-------------
 news/2024/12/16/weld-514Final/index.html | 244 +++++++++++++++++
 news/index.html                          | 154 ++++-------
 news/page/10.html                        | 303 +++++++++++++--------
 news/page/11.html                        | 185 +++++++------
 news/page/12.html                        | 257 ++++++------------
 news/page/13.html                        | 329 ++++++++++++-----------
 news/page/14.html                        | 218 ++++++++++-----
 news/page/15.html                        | 128 ++++-----
 news/page/16.html                        | 215 +++++----------
 news/page/17.html                        | 210 +++++++++++----
 news/page/18.html                        | 168 ++++--------
 news/page/19.html                        | 112 ++++++++
 news/page/2.html                         | 163 ++++++-----
 news/page/3.html                         | 140 +++++-----
 news/page/4.html                         | 142 +++++-----
 news/page/5.html                         | 138 +++++-----
 news/page/6.html                         | 169 +++++-------
 news/page/7.html                         | 251 +++++++----------
 news/page/8.html                         | 284 ++++++++++---------
 news/page/9.html                         | 326 +++++++++-------------
 news/tags/release/index.html             | 117 ++++----
 news/tags/release/page/2.html            | 128 +++++----
 news/tags/release/page/3.html            | 161 +++++------
 news/tags/release/page/4.html            | 220 +++++++--------
 news/tags/release/page/5.html            | 203 ++++++++------
 news/tags/release/page/6.html            | 140 +++++-----
 news/tags/release/page/7.html            |  61 +++++
 sitemap.xml                              |  20 +-
 32 files changed, 2965 insertions(+), 2639 deletions(-)
 create mode 100644 news/2024/12/16/weld-514Final/index.html

diff --git a/dist/index.html b/dist/index.html
index 712c36c0..bc699659 100644
--- a/dist/index.html
+++ b/dist/index.html
@@ -157,6 +157,29 @@ <h1>Download - binary distribution archive</h1>
                     Download
                   </th>
                 </tr>
+                <tr>
+                  <td class="version">
+                    5.1.4.Final
+                  </td>
+                  <td>
+                    Final
+                  </td>
+                  <td>
+                  </td>
+                  <td>
+                    16.12.2024
+                  </td>
+                  <td>
+                    <a href="https://issues.redhat.com/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12432223">
+                      Changelog
+                    </a>
+                  </td>
+                  <td>
+                    <a href="http://download.jboss.org/weld/5.1.4.Final">
+                      Download
+                    </a>
+                  </td>
+                </tr>
                 <tr>
                   <td class="version">
                     6.0.0.CR2
diff --git a/download/index.html b/download/index.html
index 2228edf7..a233558c 100644
--- a/download/index.html
+++ b/download/index.html
@@ -207,6 +207,30 @@ <h2>Binary distribution</h2>
                     Download
                   </th>
                 </tr>
+                <tr>
+                  <td class="version">
+                    5.1.4.Final
+                  </td>
+                  <td>
+                    Final
+                  </td>
+                  <td>
+                    4.0
+                  </td>
+                  <td>
+                    16.12.2024
+                  </td>
+                  <td>
+                    <a href="https://issues.redhat.com/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12432223">
+                      Changelog
+                    </a>
+                  </td>
+                  <td>
+                    <a href="https://download.jboss.org/weld/5.1.4.Final">
+                      Download
+                    </a>
+                  </td>
+                </tr>
                 <tr>
                   <td class="version">
                     6.0.0.CR2
@@ -429,30 +453,6 @@ <h2>Binary distribution</h2>
                     </a>
                   </td>
                 </tr>
-                <tr>
-                  <td class="version">
-                    5.1.1.Final
-                  </td>
-                  <td>
-                    Final
-                  </td>
-                  <td>
-                    4.0
-                  </td>
-                  <td>
-                    12.06.2023
-                  </td>
-                  <td>
-                    <a href="https://issues.redhat.com/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12397581">
-                      Changelog
-                    </a>
-                  </td>
-                  <td>
-                    <a href="https://download.jboss.org/weld/5.1.1.Final">
-                      Download
-                    </a>
-                  </td>
-                </tr>
               </table>
               <p></p>
               <a href="/dist">
diff --git a/index.html b/index.html
index 962e2614..8d7a14d4 100644
--- a/index.html
+++ b/index.html
@@ -549,10 +549,10 @@ <h2>
                     <ul class="newsColumn">
                       <li>
                         <h3>
-                          <a href="/news/2024/11/28/weld-600CR2/">Weld 6.0.0.CR2</a>
+                          <a href="/news/2024/12/16/weld-514Final/">Weld 5.1.4.Final</a>
                         </h3>
                         <div class="news-date news-boxed">
-                          2024-11-28
+                          2024-12-16
                           &nbsp;
                           <span class="tags">
                             <i class="fa fa-tags"></i>
@@ -560,16 +560,16 @@ <h3>
                           </span>
                         </div>
                         <p>
-                          Weld 6.0.0.CR2 is now available
+                          Tiny update for Weld 5.1
                         </p>
                         <hr>
                       </li>
                       <li>
                         <h3>
-                          <a href="/news/2024/11/13/weld-600CR1/">Weld 6.0.0.CR1</a>
+                          <a href="/news/2024/11/28/weld-600CR2/">Weld 6.0.0.CR2</a>
                         </h3>
                         <div class="news-date news-boxed">
-                          2024-11-13
+                          2024-11-28
                           &nbsp;
                           <span class="tags">
                             <i class="fa fa-tags"></i>
@@ -577,16 +577,16 @@ <h3>
                           </span>
                         </div>
                         <p>
-                          Weld 6.0.0.CR1 is now available
+                          Weld 6.0.0.CR2 is now available
                         </p>
                         <hr>
                       </li>
                       <li>
                         <h3>
-                          <a href="/news/2024/08/27/weld-513Final/">Weld 5.1.3.Final</a>
+                          <a href="/news/2024/11/13/weld-600CR1/">Weld 6.0.0.CR1</a>
                         </h3>
                         <div class="news-date news-boxed">
-                          2024-8-27
+                          2024-11-13
                           &nbsp;
                           <span class="tags">
                             <i class="fa fa-tags"></i>
@@ -594,16 +594,16 @@ <h3>
                           </span>
                         </div>
                         <p>
-                          Squashing bugs with Weld 5.1.3.Final!
+                          Weld 6.0.0.CR1 is now available
                         </p>
                         <hr>
                       </li>
                       <li>
                         <h3>
-                          <a href="/news/2024/07/03/weld-600Beta4/">Weld 6.0.0.Beta4</a>
+                          <a href="/news/2024/08/27/weld-513Final/">Weld 5.1.3.Final</a>
                         </h3>
                         <div class="news-date news-boxed">
-                          2024-7-3
+                          2024-8-27
                           &nbsp;
                           <span class="tags">
                             <i class="fa fa-tags"></i>
@@ -611,16 +611,16 @@ <h3>
                           </span>
                         </div>
                         <p>
-                          Weld 6.0.0.Beta4 is now available
+                          Squashing bugs with Weld 5.1.3.Final!
                         </p>
                         <hr>
                       </li>
                       <li>
                         <h3>
-                          <a href="/news/2024/02/26/weld-600Beta1/">Weld 6.0.0.Beta1</a>
+                          <a href="/news/2024/07/03/weld-600Beta4/">Weld 6.0.0.Beta4</a>
                         </h3>
                         <div class="news-date news-boxed">
-                          2024-2-26
+                          2024-7-3
                           &nbsp;
                           <span class="tags">
                             <i class="fa fa-tags"></i>
@@ -628,7 +628,7 @@ <h3>
                           </span>
                         </div>
                         <p>
-                          Weld 6.0.0.Beta1 is now available
+                          Weld 6.0.0.Beta4 is now available
                         </p>
                         <hr>
                       </li>
diff --git a/news.atom b/news.atom
index 3c50ba03..1e5a829d 100644
--- a/news.atom
+++ b/news.atom
@@ -2,13 +2,94 @@
 <feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
   <id>https://weld.cdi-spec.org/</id>
   <title>Weld</title>
-  <updated>2024-11-28T10:19:02+00:00</updated>
+  <updated>2024-12-16T11:18:04+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/2024/12/16/weld-514Final/</id>
+    <title>Weld 5.1.4.Final</title>
+    <updated>2024-12-16T11:18:04+00:00</updated>
+    <published>2024-12-16T00:00:00+00:00</published>
+    <link href="https://weld.cdi-spec.org/news/2024/12/16/weld-514Final/" rel="alternate" type="text/html" />
+    <author>
+      <name>Matej Novotny</name>
+    </author>
+    <category term="release"></category>
+    <summary>
+      A small update for Weld 5.1 (5.1.4.Final) has been released.
+      
+      
+      List of changes from 5.1.3.Final version:
+      
+      
+      
+      
+      Fix resource injection into beans added via extensions (WELD-2798)
+      
+      
+      Prevent file leak in Weld&#8217;s ServiceLoader (WELD-2800)
+      
+      
+      
+      Note that most environments were unaffected by this; the only reported issue was for testing setup of GlassFish on Windows machines
+      
+      
+      
+      
+      
+      Deprecate WeldCrossContextFilter, to be removed in Weld 6 (WELD-2803)
+      
+      
+      Update custom TCK exclusion list used for relaxed mode testing (WELD-2806)
+      
+      
+      
+      
+      &#91; Download &#93;
+      &#91; Documentation &#93;
+      &#91; Release notes &#93;...
+    </summary>
+    <content type="html">
+      &lt;div class=&quot;paragraph&quot;&gt;
+      &lt;p&gt;A small update for Weld 5.1 (5.1.4.Final) has been released.&lt;/p&gt;
+      &lt;/div&gt;
+      &lt;div class=&quot;paragraph&quot;&gt;
+      &lt;p&gt;List of changes from 5.1.3.Final version:&lt;/p&gt;
+      &lt;/div&gt;
+      &lt;div class=&quot;ulist&quot;&gt;
+      &lt;ul&gt;
+      &lt;li&gt;
+      &lt;p&gt;Fix resource injection into beans added via extensions (&lt;a href=&quot;https://issues.redhat.com/browse/WELD-2798&quot;&gt;WELD-2798&lt;/a&gt;)&lt;/p&gt;
+      &lt;/li&gt;
+      &lt;li&gt;
+      &lt;p&gt;Prevent file leak in Weld’s &lt;code&gt;ServiceLoader&lt;/code&gt; (&lt;a href=&quot;https://issues.redhat.com/browse/WELD-2800&quot;&gt;WELD-2800&lt;/a&gt;)&lt;/p&gt;
+      &lt;div class=&quot;ulist&quot;&gt;
+      &lt;ul&gt;
+      &lt;li&gt;
+      &lt;p&gt;Note that most environments were unaffected by this; the only reported issue was for testing setup of GlassFish on Windows machines&lt;/p&gt;
+      &lt;/li&gt;
+      &lt;/ul&gt;
+      &lt;/div&gt;
+      &lt;/li&gt;
+      &lt;li&gt;
+      &lt;p&gt;Deprecate &lt;code&gt;WeldCrossContextFilter&lt;/code&gt;, to be removed in Weld 6 (&lt;a href=&quot;https://issues.redhat.com/browse/WELD-2803&quot;&gt;WELD-2803&lt;/a&gt;)&lt;/p&gt;
+      &lt;/li&gt;
+      &lt;li&gt;
+      &lt;p&gt;Update custom TCK exclusion list used for &lt;code&gt;relaxed mode&lt;/code&gt; testing (&lt;a href=&quot;https://issues.redhat.com/browse/WELD-2806&quot;&gt;WELD-2806&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;[ &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/5.1.4.Final/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=12432223&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/2024/11/28/weld-600CR2/</id>
     <title>Weld 6.0.0.CR2</title>
-    <updated>2024-11-28T10:19:02+00:00</updated>
+    <updated>2024-11-28T11:46:35+00:00</updated>
     <published>2024-11-28T00:00:00+00:00</published>
     <link href="https://weld.cdi-spec.org/news/2024/11/28/weld-600CR2/" rel="alternate" type="text/html" />
     <author>
@@ -71,7 +152,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2024/11/13/weld-600CR1/</id>
     <title>Weld 6.0.0.CR1</title>
-    <updated>2024-11-28T10:12:29+00:00</updated>
+    <updated>2024-11-28T11:46:27+00:00</updated>
     <published>2024-11-13T00:00:00+00:00</published>
     <link href="https://weld.cdi-spec.org/news/2024/11/13/weld-600CR1/" rel="alternate" type="text/html" />
     <author>
@@ -169,7 +250,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2024/08/27/weld-513Final/</id>
     <title>Weld 5.1.3.Final</title>
-    <updated>2024-11-28T10:12:26+00:00</updated>
+    <updated>2024-11-28T11:46:27+00:00</updated>
     <published>2024-08-27T00:00:00+00:00</published>
     <link href="https://weld.cdi-spec.org/news/2024/08/27/weld-513Final/" rel="alternate" type="text/html" />
     <author>
@@ -270,7 +351,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2024/07/03/weld-600Beta4/</id>
     <title>Weld 6.0.0.Beta4</title>
-    <updated>2024-11-28T10:12:26+00:00</updated>
+    <updated>2024-11-28T11:46:27+00:00</updated>
     <published>2024-07-03T00:00:00+00:00</published>
     <link href="https://weld.cdi-spec.org/news/2024/07/03/weld-600Beta4/" rel="alternate" type="text/html" />
     <author>
@@ -387,7 +468,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2024/02/26/weld-600Beta1/</id>
     <title>Weld 6.0.0.Beta1</title>
-    <updated>2024-11-28T10:12:26+00:00</updated>
+    <updated>2024-11-28T11:46:27+00:00</updated>
     <published>2024-02-26T00:00:00+00:00</published>
     <link href="https://weld.cdi-spec.org/news/2024/02/26/weld-600Beta1/" rel="alternate" type="text/html" />
     <author>
@@ -508,7 +589,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2023/10/26/weld-600Alpha1/</id>
     <title>Weld 6.0.0.Alpha1</title>
-    <updated>2024-11-28T10:12:26+00:00</updated>
+    <updated>2024-11-28T11:46:27+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>
@@ -645,7 +726,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2023/10/05/weld-512Final/</id>
     <title>Weld 5.1.2.Final</title>
-    <updated>2024-11-28T10:12:26+00:00</updated>
+    <updated>2024-11-28T11:46:27+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>
@@ -733,7 +814,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2023/08/09/weld-511SP2/</id>
     <title>Weld 5.1.1.SP2</title>
-    <updated>2024-11-28T10:12:26+00:00</updated>
+    <updated>2024-11-28T11:46:27+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>
@@ -776,7 +857,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2023/07/11/weld-511SP1/</id>
     <title>Weld 5.1.1.SP1</title>
-    <updated>2024-11-28T10:12:26+00:00</updated>
+    <updated>2024-11-28T11:46:27+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>
@@ -840,7 +921,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2023/06/12/weld-511Final/</id>
     <title>Weld 5.1.1.Final</title>
-    <updated>2024-11-28T10:12:26+00:00</updated>
+    <updated>2024-11-28T11:46:27+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>
@@ -929,7 +1010,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2022/10/03/weld-510Final/</id>
     <title>Weld 5.1.0.Final</title>
-    <updated>2024-11-28T10:12:26+00:00</updated>
+    <updated>2024-11-28T11:46:27+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>
@@ -1021,7 +1102,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2022/06/24/weld-501Final/</id>
     <title>Weld 5.0.1.Final</title>
-    <updated>2024-11-28T10:12:26+00:00</updated>
+    <updated>2024-11-28T11:46:27+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>
@@ -1096,7 +1177,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2022/06/08/weld-500SP2/</id>
     <title>Weld 5.0.0.SP2</title>
-    <updated>2024-11-28T10:12:26+00:00</updated>
+    <updated>2024-11-28T11:46:27+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>
@@ -1141,7 +1222,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2022/05/04/weld-500SP1/</id>
     <title>Weld 5.0.0.SP1</title>
-    <updated>2024-11-28T10:12:26+00:00</updated>
+    <updated>2024-11-28T11:46:27+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>
@@ -1186,7 +1267,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2022/04/29/weld-500Final/</id>
     <title>Weld 5.0.0.Final</title>
-    <updated>2024-11-28T10:12:26+00:00</updated>
+    <updated>2024-11-28T11:46:27+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>
@@ -1269,7 +1350,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2022/03/23/weld-500CR2/</id>
     <title>Weld 5.0.0.CR2</title>
-    <updated>2024-11-28T10:12:26+00:00</updated>
+    <updated>2024-11-28T11:46:27+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>
@@ -1309,7 +1390,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2022/02/23/weld-500CR1/</id>
     <title>Weld 5.0.0.CR1</title>
-    <updated>2024-11-28T10:12:26+00:00</updated>
+    <updated>2024-11-28T11:46:27+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>
@@ -1378,7 +1459,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>2024-11-28T10:12:26+00:00</updated>
+    <updated>2024-11-28T11:46:27+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>
@@ -1475,7 +1556,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2022/01/24/weld-500Beta1/</id>
     <title>Weld 5.0.0.Beta1</title>
-    <updated>2024-11-28T10:12:26+00:00</updated>
+    <updated>2024-11-28T11:46:27+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>
@@ -1786,7 +1867,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>2024-11-28T10:12:26+00:00</updated>
+    <updated>2024-11-28T11:46:27+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>
@@ -1867,7 +1948,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>2024-11-28T10:12:26+00:00</updated>
+    <updated>2024-11-28T11:46:27+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>
@@ -1947,7 +2028,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2021/03/22/weld-401Final/</id>
     <title>Weld 4.0.1.Final</title>
-    <updated>2024-11-28T10:12:26+00:00</updated>
+    <updated>2024-11-28T11:46:27+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>
@@ -2066,7 +2147,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2021/03/18/weld-317Final/</id>
     <title>Weld 3.1.7.Final</title>
-    <updated>2024-11-28T10:12:26+00:00</updated>
+    <updated>2024-11-28T11:46:27+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>
@@ -2180,7 +2261,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2021/01/13/weld-316Final/</id>
     <title>Weld 3.1.6.Final</title>
-    <updated>2024-11-28T10:12:26+00:00</updated>
+    <updated>2024-11-28T11:46:27+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>
@@ -2338,7 +2419,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2020/12/16/weld-400Final/</id>
     <title>Weld 4.0.0.Final</title>
-    <updated>2024-11-28T10:12:26+00:00</updated>
+    <updated>2024-11-28T11:46:27+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>
@@ -2416,7 +2497,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2020/09/18/weld-400Beta1/</id>
     <title>Weld 4.0.0.Beta1</title>
-    <updated>2024-11-28T10:12:26+00:00</updated>
+    <updated>2024-11-28T11:46:27+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>
@@ -2533,7 +2614,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2020/08/12/weld-315Final/</id>
     <title>Weld 3.1.5.Final</title>
-    <updated>2024-11-28T10:12:26+00:00</updated>
+    <updated>2024-11-28T11:46:27+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>
@@ -2671,7 +2752,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>2024-11-28T10:12:26+00:00</updated>
+    <updated>2024-11-28T11:46:27+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>
@@ -2810,7 +2891,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2020/03/28/weld-314Final/</id>
     <title>Weld 3.1.4.Final</title>
-    <updated>2024-11-28T10:12:26+00:00</updated>
+    <updated>2024-11-28T11:46:27+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>
@@ -2922,7 +3003,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2019/11/28/weld-313Final/</id>
     <title>Weld 3.1.3.Final</title>
-    <updated>2024-11-28T10:12:26+00:00</updated>
+    <updated>2024-11-28T11:46:27+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>
@@ -3056,7 +3137,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2019/08/06/weld-312Final/</id>
     <title>Weld 3.1.2.Final</title>
-    <updated>2024-11-28T10:12:26+00:00</updated>
+    <updated>2024-11-28T11:46:27+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>
@@ -3210,7 +3291,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2019/05/07/weld-311Final/</id>
     <title>Weld 3.1.1.Final</title>
-    <updated>2024-11-28T10:12:26+00:00</updated>
+    <updated>2024-11-28T11:46:27+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>
@@ -3343,7 +3424,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2019/02/06/weld-310Final/</id>
     <title>Weld 3.1.0.Final</title>
-    <updated>2024-11-28T10:12:26+00:00</updated>
+    <updated>2024-11-28T11:46:27+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>
@@ -3595,7 +3676,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2018/09/26/weld-248Final/</id>
     <title>Weld 2.4.8.Final</title>
-    <updated>2024-11-28T10:12:26+00:00</updated>
+    <updated>2024-11-28T11:46:27+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>
@@ -3732,7 +3813,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2018/07/26/weld-305Final/</id>
     <title>Weld 3.0.5.Final</title>
-    <updated>2024-11-28T10:12:26+00:00</updated>
+    <updated>2024-11-28T11:46:27+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>
@@ -3896,7 +3977,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2018/07/10/weld-team-changes/</id>
     <title>Weld team changes</title>
-    <updated>2024-11-28T10:12:26+00:00</updated>
+    <updated>2024-11-28T11:46:27+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>
@@ -3945,7 +4026,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2018/04/26/weld-304Final/</id>
     <title>Weld 3.0.4.Final</title>
-    <updated>2024-11-28T10:12:26+00:00</updated>
+    <updated>2024-11-28T11:46:27+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>
@@ -4144,7 +4225,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2018/03/20/weld-247Final/</id>
     <title>Weld 2.4.7.Final</title>
-    <updated>2024-11-28T10:12:26+00:00</updated>
+    <updated>2024-11-28T11:46:27+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>
@@ -4327,7 +4408,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2018/02/09/weld-303Final/</id>
     <title>Weld 3.0.3.Final</title>
-    <updated>2024-11-28T10:12:26+00:00</updated>
+    <updated>2024-11-28T11:46:27+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>
@@ -4462,7 +4543,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2017/12/19/weld-meets-junit5/</id>
     <title>Weld meets JUnit 5</title>
-    <updated>2024-11-28T10:12:26+00:00</updated>
+    <updated>2024-11-28T11:46:27+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>
@@ -4639,7 +4720,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2017/12/18/weld-246Final/</id>
     <title>Weld 2.4.6.Final</title>
-    <updated>2024-11-28T10:12:26+00:00</updated>
+    <updated>2024-11-28T11:46:27+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>
@@ -4818,7 +4899,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2017/11/23/weld-302Final/</id>
     <title>Weld 3.0.2.Final</title>
-    <updated>2024-11-28T10:12:26+00:00</updated>
+    <updated>2024-11-28T11:46:27+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>
@@ -4993,7 +5074,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2017/09/11/weld-245Final/</id>
     <title>Weld 2.4.5.Final</title>
-    <updated>2024-11-28T10:12:26+00:00</updated>
+    <updated>2024-11-28T11:46:27+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>
@@ -5110,7 +5191,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2017/08/25/weld-301Final/</id>
     <title>Weld 3.0.1.Final</title>
-    <updated>2024-11-28T10:12:26+00:00</updated>
+    <updated>2024-11-28T11:46:27+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>
@@ -5261,7 +5342,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2017/08/07/weld-vertx-next/</id>
     <title>Weld Vert.x Next?</title>
-    <updated>2024-11-28T10:12:26+00:00</updated>
+    <updated>2024-11-28T11:46:27+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>
@@ -5520,7 +5601,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2017/06/14/weld-244Final/</id>
     <title>Weld 2.4.4.Final</title>
-    <updated>2024-11-28T10:12:26+00:00</updated>
+    <updated>2024-11-28T11:46:27+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>
@@ -5672,7 +5753,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2017/05/19/tour-around-weld-3/</id>
     <title>Tour around Weld 3</title>
-    <updated>2024-11-28T10:12:26+00:00</updated>
+    <updated>2024-11-28T11:46:27+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>
@@ -5990,7 +6071,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>2024-11-28T10:12:26+00:00</updated>
+    <updated>2024-11-28T11:46:27+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>
@@ -6168,7 +6249,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2017/04/07/weld-243Final/</id>
     <title>Weld 2.4.3.Final</title>
-    <updated>2024-11-28T10:12:26+00:00</updated>
+    <updated>2024-11-28T11:46:27+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>
@@ -6293,140 +6374,4 @@
       &lt;/div&gt;
     </content>
   </entry>
-  <entry>
-    <id>https://weld.cdi-spec.org/news/2017/03/03/weld-300CR2/</id>
-    <title>Weld 3.0.0.CR2</title>
-    <updated>2024-11-28T10:12:26+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>
-      <name>Martin Kouba</name>
-    </author>
-    <category term="release"></category>
-    <summary>
-      I am very pleased to announce the release of Weld 3.0.0.CR2 (CDI 2.0-PFD).
-      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.
-      
-      
-      Notable fixes and improvements:
-      
-      
-      
-      
-      InterceptionFactory handles interface correctly (WELD-2335)
-      
-      
-      Enable to obtain InjectionPoint metadata from within BeanConfigurator#produceWith() (WELD-2333)
-      
-      
-      ObserverMethodConfigurator.beanClass() should be preset to the extension class (WELD-2324)
-      
-      
-      Performance improvements in javax.enterprise.inject.Instance implementation (WELD-2322 and WELD-2323)
-      
-      
-      Don&#8217;t include built-in session and conversation scoped beans in the bean identifier index (WELD-2343)
-      
-      
-      Support InjectionPoint metadata injected into dependent singleton session bean (WELD-2341)
-      
-      
-      Logging
-      
-      
-      
-      Log DEBUG info about important phases during bootstrap (WELD-2336)
-      
-      
-      Fix the error message...
-    </summary>
-    <content type="html">
-      &lt;div class=&quot;paragraph&quot;&gt;
-      &lt;p&gt;I am very pleased to announce the release of Weld &lt;strong&gt;3.0.0.CR2&lt;/strong&gt; (&lt;strong&gt;CDI 2.0-PFD&lt;/strong&gt;).
-      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.&lt;/p&gt;
-      &lt;/div&gt;
-      &lt;div class=&quot;paragraph&quot;&gt;
-      &lt;p&gt;Notable fixes and improvements:&lt;/p&gt;
-      &lt;/div&gt;
-      &lt;div class=&quot;ulist&quot;&gt;
-      &lt;ul&gt;
-      &lt;li&gt;
-      &lt;p&gt;&lt;code&gt;InterceptionFactory&lt;/code&gt; handles interface correctly (&lt;a href=&quot;https://issues.jboss.org/browse/WELD-2335&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;WELD-2335&lt;/a&gt;)&lt;/p&gt;
-      &lt;/li&gt;
-      &lt;li&gt;
-      &lt;p&gt;Enable to obtain &lt;code&gt;InjectionPoint&lt;/code&gt; metadata from within &lt;code&gt;BeanConfigurator#produceWith()&lt;/code&gt; (&lt;a href=&quot;https://issues.jboss.org/browse/WELD-2333&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;WELD-2333&lt;/a&gt;)&lt;/p&gt;
-      &lt;/li&gt;
-      &lt;li&gt;
-      &lt;p&gt;&lt;code&gt;ObserverMethodConfigurator.beanClass()&lt;/code&gt; should be preset to the extension class (&lt;a href=&quot;https://issues.jboss.org/browse/WELD-2324&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;WELD-2324&lt;/a&gt;)&lt;/p&gt;
-      &lt;/li&gt;
-      &lt;li&gt;
-      &lt;p&gt;Performance improvements in &lt;code&gt;javax.enterprise.inject.Instance&lt;/code&gt; implementation (&lt;a href=&quot;https://issues.jboss.org/browse/WELD-2322&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;WELD-2322&lt;/a&gt; and &lt;a href=&quot;https://issues.jboss.org/browse/WELD-2323&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;WELD-2323&lt;/a&gt;)&lt;/p&gt;
-      &lt;/li&gt;
-      &lt;li&gt;
-      &lt;p&gt;Don’t include built-in session and conversation scoped beans in the bean identifier index (&lt;a href=&quot;https://issues.jboss.org/browse/WELD-2343&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;WELD-2343&lt;/a&gt;)&lt;/p&gt;
-      &lt;/li&gt;
-      &lt;li&gt;
-      &lt;p&gt;Support &lt;code&gt;InjectionPoint&lt;/code&gt; metadata injected into dependent singleton session bean (&lt;a href=&quot;https://issues.jboss.org/browse/WELD-2341&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;WELD-2341&lt;/a&gt;)&lt;/p&gt;
-      &lt;/li&gt;
-      &lt;li&gt;
-      &lt;p&gt;Logging&lt;/p&gt;
-      &lt;div class=&quot;ulist&quot;&gt;
-      &lt;ul&gt;
-      &lt;li&gt;
-      &lt;p&gt;Log DEBUG info about important phases during bootstrap (&lt;a href=&quot;https://issues.jboss.org/browse/WELD-2336&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;WELD-2336&lt;/a&gt;)&lt;/p&gt;
-      &lt;/li&gt;
-      &lt;li&gt;
-      &lt;p&gt;Fix the error message when an extension observer method is static (&lt;a href=&quot;https://issues.jboss.org/browse/WELD-2331&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;WELD-2331&lt;/a&gt;)&lt;/p&gt;
-      &lt;/li&gt;
-      &lt;li&gt;
-      &lt;p&gt;Improved transactional observer methods logging in case of failure (&lt;a href=&quot;https://issues.jboss.org/browse/WELD-2330&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;WELD-2330&lt;/a&gt;)&lt;/p&gt;
-      &lt;/li&gt;
-      &lt;/ul&gt;
-      &lt;/div&gt;
-      &lt;/li&gt;
-      &lt;li&gt;
-      &lt;p&gt;Weld SE - &lt;code&gt;ContainerInitialized&lt;/code&gt; should be fired after the container is initialized and shutdown hook is registered (&lt;a href=&quot;https://issues.jboss.org/browse/WELD-2340&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;WELD-2340&lt;/a&gt;)&lt;/p&gt;
-      &lt;/li&gt;
-      &lt;li&gt;
-      &lt;p&gt;Probe development tool&lt;/p&gt;
-      &lt;div class=&quot;ulist&quot;&gt;
-      &lt;ul&gt;
-      &lt;li&gt;
-      &lt;p&gt;Extended bean archive info&lt;/p&gt;
-      &lt;/li&gt;
-      &lt;li&gt;
-      &lt;p&gt;Monitor bean instance creation&lt;/p&gt;
-      &lt;/li&gt;
-      &lt;li&gt;
-      &lt;p&gt;Do not mark a bean as unused if only injected into an observer method or disposer method&lt;/p&gt;
-      &lt;/li&gt;
-      &lt;li&gt;
-      &lt;p&gt;&lt;code&gt;org.jboss.weld.probe&lt;/code&gt; package is vetoed&lt;/p&gt;
-      &lt;/li&gt;
-      &lt;/ul&gt;
-      &lt;/div&gt;
-      &lt;/li&gt;
-      &lt;/ul&gt;
-      &lt;/div&gt;
-      &lt;div class=&quot;paragraph&quot;&gt;
-      &lt;p&gt;See also &lt;a href=&quot;https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;amp;version=12333159&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;the release details&lt;/a&gt;.
-      Thanks to everyone involved in this release!&lt;/p&gt;
-      &lt;/div&gt;
-      &lt;div class=&quot;sect1&quot;&gt;
-      &lt;h2 id=&quot;_wildfly_patch&quot;&gt;WildFly Patch&lt;/h2&gt;
-      &lt;div class=&quot;sectionbody&quot;&gt;
-      &lt;div class=&quot;paragraph&quot;&gt;
-      &lt;p&gt;As usual, a &lt;a href=&quot;http://download.jboss.org/weld/3.0.0.CR2/wildfly-10.1.0.Final-weld-3.0.0.CR2-patch.zip&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;patch for WildFly&lt;/a&gt; is available.
-      This time the target platform is &lt;strong&gt;WildFly 10.1.0.Final&lt;/strong&gt;.
-      If you’re not familiar with patching WildFly, check the &lt;a href=&quot;https://weld.cdi-spec.org/documentation/#12&quot;&gt;FAQ&lt;/a&gt;.&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/3.0.0.CR2/en-US/html/&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=12333159&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;Release notes&lt;/a&gt; ]&lt;/p&gt;
-      &lt;/div&gt;
-      &lt;/div&gt;
-      &lt;/div&gt;
-    </content>
-  </entry>
 </feed>
diff --git a/news/2024/12/16/weld-514Final/index.html b/news/2024/12/16/weld-514Final/index.html
new file mode 100644
index 00000000..73955d02
--- /dev/null
+++ b/news/2024/12/16/weld-514Final/index.html
@@ -0,0 +1,244 @@
+<!DOCTYPE html>
+<html>
+  <head>
+    <meta charset="utf-8">
+    <title>
+      Weld: Weld 5.1.4.Final
+    </title>
+    <meta content="width=device-width, initial-scale=1.0" name="viewport">
+    <meta content="Tiny update for Weld 5.1" 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 5.1.4.Final
+                  <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">
+                  2024-12-16
+                  &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 small update for Weld 5.1 (5.1.4.Final) has been released.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>List of changes from 5.1.3.Final version:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Fix resource injection into beans added via extensions (<a href="https://issues.redhat.com/browse/WELD-2798">WELD-2798</a>)</p>
+                  </li>
+                  <li>
+                  <p>Prevent file leak in Weld&#8217;s <code>ServiceLoader</code> (<a href="https://issues.redhat.com/browse/WELD-2800">WELD-2800</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Note that most environments were unaffected by this; the only reported issue was for testing setup of GlassFish on Windows machines</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Deprecate <code>WeldCrossContextFilter</code>, to be removed in Weld 6 (<a href="https://issues.redhat.com/browse/WELD-2803">WELD-2803</a>)</p>
+                  </li>
+                  <li>
+                  <p>Update custom TCK exclusion list used for <code>relaxed mode</code> testing (<a href="https://issues.redhat.com/browse/WELD-2806">WELD-2806</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.4.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=12432223" 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/2024/12/16/weld-514Final/";
+                            var disqus_developer = null;
+                            var disqus_identifier = "6b76af4e0a56adc319166f323faad030da4a4664";
+                            (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 83c0763d..1895ef17 100644
--- a/news/index.html
+++ b/news/index.html
@@ -141,6 +141,60 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2024/12/16/weld-514Final/">Weld 5.1.4.Final</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2024-12-16
+                  &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 small update for Weld 5.1 (5.1.4.Final) has been released.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>List of changes from 5.1.3.Final version:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Fix resource injection into beans added via extensions (<a href="https://issues.redhat.com/browse/WELD-2798">WELD-2798</a>)</p>
+                  </li>
+                  <li>
+                  <p>Prevent file leak in Weld&#8217;s <code>ServiceLoader</code> (<a href="https://issues.redhat.com/browse/WELD-2800">WELD-2800</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Note that most environments were unaffected by this; the only reported issue was for testing setup of GlassFish on Windows machines</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Deprecate <code>WeldCrossContextFilter</code>, to be removed in Weld 6 (<a href="https://issues.redhat.com/browse/WELD-2803">WELD-2803</a>)</p>
+                  </li>
+                  <li>
+                  <p>Update custom TCK exclusion list used for <code>relaxed mode</code> testing (<a href="https://issues.redhat.com/browse/WELD-2806">WELD-2806</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.4.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=12432223" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2024/11/28/weld-600CR2/">Weld 6.0.0.CR2</a>
@@ -452,106 +506,6 @@ <h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2024/02/26/weld-600Beta1/">Weld 6.0.0.Beta1</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2024-2-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 Core 6.0.0.Beta1 along with Weld API 6.0.Beta2 are the latest two artifacts you&#8217;re going to need if you&#8217;re looking for an implementation of the CDI API 4.1.0.Beta1.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Changes based on CDI specification since last 6.x version:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>The method invoker API in CDI has been simplified and the transformer functionality removed from the specification (<a href="https://issues.redhat.com/browse/WELD-2765">WELD-2765</a>)</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Weld API introduced <code>WeldInvokerBuilder</code> which retains all of the transformers/wrappers that were originally present</p>
-                  </li>
-                  <li>
-                  <p>We also added some more validation and other tweaks but the whole functionality is still being worked on as part of the follow up release</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Support declaring <code>@Priority</code> on producers (<a href="https://issues.redhat.com/browse/WELD-2768">WELD-2768</a>)</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>This is also one of the features added by CDI API 4.1 and Beta1 of Weld supports it</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p><code>BeanManager</code> implementations in Weld now correctly extend <code>ELAwareBeanManager</code> from newly introduced CDI API module (<a href="https://issues.redhat.com/browse/WELD-2769">WELD-2769</a>)</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>There is no functionality change, this is just a step forward towards removing EL dependency from core CDI</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Implemented programmatic access to assignability rules on <code>BeanManager</code> (<a href="https://issues.redhat.com/browse/WELD-2774">WELD-2774</a>)</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p><code>BeanContainer</code>/<code>BeanManager</code> now allow users to invoke <code>#isMatchingBean()</code> and <code>#isMatchingEvent()</code> methods</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>Other changes and bugfixes:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Correct inheritance of producer fields if there is an extension present (<a href="https://issues.redhat.com/browse/WELD-2773">WELD-2773</a>)</p>
-                  </li>
-                  <li>
-                  <p>Make sure <code>@Default</code> qualifier is added to events fired via <code>BeanManager#getEvent()</code> where appropriate (<a href="https://issues.redhat.com/browse/WELD-2775">WELD-2775</a>)</p>
-                  </li>
-                  <li>
-                  <p>Weld SE - manually registered portable extensions now reside in synthetic bean archive instead of their own (<a href="https://issues.redhat.com/browse/WELD-2776">WELD-2776</a>)</p>
-                  </li>
-                  <li>
-                  <p>Updated CI setup to make sure bulk of our tests is running against JDK 21 (<a href="https://issues.redhat.com/browse/WELD-2777">WELD-2777</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.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=12415474" 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/18.html" class="page-link">18</a> <a href="/news/page/19.html" class="page-link">19</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 f0efed6f..5f159b6c 100644
--- a/news/page/10.html
+++ b/news/page/10.html
@@ -141,6 +141,203 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2017/08/07/weld-vertx-next/">Weld Vert.x Next?</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2017-8-7
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/vertx">vertx</a>
+                    ,
+                    <a href="/news/tags/integration">integration</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="#_what_is_it_good_for">What Is It Good For?</a>
+                  <ul class="sectlevel2">
+                  <li><a href="#_modules">Modules</a></li>
+                  </ul>
+                  </li>
+                  <li><a href="#_how_do_i_use_it_in_my_vert_x_webapp">How Do I Use It In My Vert.x Webapp?</a>
+                  <ul class="sectlevel2">
+                  <li><a href="#_1_project_configuration">1. Project Configuration</a></li>
+                  <li><a href="#_2_start_cdi_container">2. Start CDI Container</a></li>
+                  <li><a href="#_3_observe_events">3. Observe Events</a></li>
+                  <li><a href="#_4_declare_routes">4. Declare Routes</a></li>
+                  <li><a href="#_5_enjoy_and_celebrate">5. Enjoy and Celebrate</a></li>
+                  </ul>
+                  </li>
+                  <li><a href="#_future_and_plans">Future and Plans</a></li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>Last year Weld team announced the <a href="https://github.com/weld/weld-vertx" target="_blank" rel="noopener">weld-vertx</a> project (see also <a href="/news/2016/04/11/weld-meets-vertx/" target="_blank" rel="noopener">Weld meets Vert.x</a> and <a href="/news/2016/06/21/update-on-weld-vertx/" target="_blank" rel="noopener">Update on weld-vertx</a> articles).
+                  The goal was clear - bring the CDI programming model into the Vert.x ecosystem.
+                  Since then, several things have changed.
+                  Two new modules were added, <strong>CDI 2</strong> and <strong>Weld 3</strong> is now used by default, and <a href="http://search.maven.org/#search%7Cga%7C1%7Cweld-vertx" target="_blank" rel="noopener">two final versions</a> were released.
+                  I think it&#8217;s a good time to summarize the features and plans for future.</p>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_what_is_it_good_for">What Is It Good For?</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>First of all, it offers a mature component model for business logic in your Vert.x applications.
+                  A reasonable component model helps making your applications maintainable and scalable in terms of development and reusability.
+                  So the primary intention is to <em>implement the business logic as CDI beans and use Vert.x APIs for everything else</em>.</p>
+                  </div>
+                  <div class="sect2">
+                  <h3 id="_modules">Modules</h3>
+                  <div class="paragraph">
+                  <p>So far there are four modules available:</p>
+                  </div>
+                  <div class="olist arabic">
+                  <ol class="arabic">
+                  <li>
+                  <p>The <em>Core</em> module starts/stops the Weld SE container and to notifies CDI observer methods when a message is sent via Vert.x event bus. Also you can inject <code>io.vertx.core.Vertx</code> and <code>io.vertx.core.Context</code> in any CDI bean.</p>
+                  </li>
+                  <li>
+                  <p>The <em>Web</em> module allows to configure the router (a component responsible to find the "logic" to handle an HTTP request) in a declarative way, using <code>@org.jboss.weld.vertx.web.WebRoute</code> annotation. Of course, you can register routes programatically. But what if there are hundreds of routes? The more complicated the REST API is the more difficult it is to maintain the code.</p>
+                  </li>
+                  <li>
+                  <p>The <em>Service Proxy</em> module makes it possible to inject and invoke service proxies (as defined in <a href="https://github.com/vert-x3/vertx-service-proxy" class="bare">https://github.com/vert-x3/vertx-service-proxy</a>).</p>
+                  </li>
+                  <li>
+                  <p>The <em>Probe</em> module enables Weld Probe development tool in a Vert.x application.</p>
+                  </li>
+                  </ol>
+                  </div>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_how_do_i_use_it_in_my_vert_x_webapp">How Do I Use It In My Vert.x Webapp?</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>Let&#8217;s enhance an existing webapp in four simple steps.</p>
+                  </div>
+                  <div class="sect2">
+                  <h3 id="_1_project_configuration">1. Project Configuration</h3>
+                  <div class="paragraph">
+                  <p>Jus add the following dependency to your <code>pom.xml</code> and <a href="https://github.com/weld/weld-vertx/blob/master/examples/hello/src/main/resources/META-INF/beans.xml">beans.xml</a> into <code>src/main/resources/META-INF</code> (this will enable CDI).</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;dependency&gt;&#x000A;      &lt;groupId&gt;org.jboss.weld.vertx&lt;/groupId&gt;&#x000A;      &lt;artifactId&gt;weld-vertx-web&lt;/artifactId&gt;&#x000A;      &lt;version&gt;${version.weld-vertx}&lt;/version&gt;&#x000A;    &lt;/dependency&gt;</code></pre>
+                  </div>
+                  </div>
+                  <div class="admonitionblock note">
+                  <table>
+                  <tr>
+                  <td class="icon">
+                  <div class="title">Note</div>
+                  </td>
+                  <td class="content">
+                  This also brings in <code>org.jboss.weld.vertx:weld-vertx-core</code>, Vert.x and Weld dependencies.
+                  </td>
+                  </tr>
+                  </table>
+                  </div>
+                  </div>
+                  <div class="sect2">
+                  <h3 id="_2_start_cdi_container">2. Start CDI Container</h3>
+                  <div class="paragraph">
+                  <p>Deploy <code>WeldWebVerticle</code> and configure router:</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">class MyVertxApp {&#x000A;    &#x000A;         public static void main(String[] args) {&#x000A;             final Vertx vertx = Vertx.vertx();&#x000A;             // ...deploy other existing verticles&#x000A;             final WeldWebVerticle weldVerticle = new WeldWebVerticle();&#x000A;             vertx.deployVerticle(weldVerticle, result -&gt; {&#x000A;                 if (result.succeeded()) {&#x000A;                     vertx.createHttpServer().requestHandler(weldVerticle.createRouter()::accept).listen(8080);&#x000A;                 }&#x000A;             });&#x000A;         }&#x000A;     }</code></pre>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect2">
+                  <h3 id="_3_observe_events">3. Observe Events</h3>
+                  <div class="paragraph">
+                  <p>Create a CDI observer method to consume messages from the Vert.x event bus.
+                  <code>@VertxConsumer</code> qualifier is used to specify the address the consumer will be registered to.
+                  <code>VertxEvent</code> is a wrapper of a Vert.x message.</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@ApplicationScoped&#x000A;    class HelloBean {&#x000A;    &#x000A;      void consumerWithDependencies(@Observes @VertxConsumer("hello.address") VertxEvent event, HelloService service) {&#x000A;        // Reply to the message - io.vertx.core.eventbus.Message.reply(Object)&#x000A;        event.setReply(service.hello());&#x000A;      }&#x000A;    }</code></pre>
+                  </div>
+                  </div>
+                  <div class="admonitionblock note">
+                  <table>
+                  <tr>
+                  <td class="icon">
+                  <div class="title">Note</div>
+                  </td>
+                  <td class="content">
+                  Since we’re working with regular observer methods, additional parameters may be declared (next to the event parameter) - these parameters are injection points.
+                  </td>
+                  </tr>
+                  </table>
+                  </div>
+                  </div>
+                  <div class="sect2">
+                  <h3 id="_4_declare_routes">4. Declare Routes</h3>
+                  <div class="paragraph">
+                  <p>Annotate a class implementing <code>Handler&lt;RoutingContext&gt;</code> with <code>@org.jboss.weld.vertx.web.WebRoute</code>:</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@WebRoute("/hello") // Matches all HTTP methods&#x000A;    class HelloHandler implements Handler&lt;RoutingContext&gt; {&#x000A;    &#x000A;        @Inject&#x000A;        HelloService service;&#x000A;    &#x000A;        @Override&#x000A;        public void handle(RoutingContext ctx) {&#x000A;            ctx.response().setStatusCode(200).end(service.hello());&#x000A;        }&#x000A;    }</code></pre>
+                  </div>
+                  </div>
+                  <div class="paragraph">
+                  <p>This will be translated into something like:</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">void integrationPseudoCode() {&#x000A;      HelloHandler hello = produceInjectedInstanceOfHelloHandler();&#x000A;      Router router = obtainRouterInstance();&#x000A;      router.route("/hello").handler(hello);&#x000A;    }</code></pre>
+                  </div>
+                  </div>
+                  <div class="admonitionblock note">
+                  <table>
+                  <tr>
+                  <td class="icon">
+                  <div class="title">Note</div>
+                  </td>
+                  <td class="content">
+                  <code>@WebRoute</code> is repeatable, i.e. if multiple annotations are declared on a handler class a single handler instance is used for multiple routes.
+                  </td>
+                  </tr>
+                  </table>
+                  </div>
+                  </div>
+                  <div class="sect2">
+                  <h3 id="_5_enjoy_and_celebrate">5. Enjoy and Celebrate</h3>
+                  <div class="paragraph">
+                  <p>And that&#8217;s it.
+                  Fairly straightforward, isn&#8217;t it?</p>
+                  </div>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_future_and_plans">Future and Plans</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>So far there are no new features on the roadmap.
+                  The plan is to provide bugfix releases as needed.
+                  But <code>weld-vertx</code> is an open source project and so the future is in hands of the community.
+                  Feel free to <a href="https://github.com/weld/weld-vertx/issues">create issues, share ideas, throw feature requests</a> and send pull requests!</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2017/06/14/weld-244Final/">Weld 2.4.4.Final</a>
@@ -765,112 +962,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/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/18.html" class="page-link">18</a> <a href="/news/page/19.html" class="page-link">19</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 f454270e..62322632 100644
--- a/news/page/11.html
+++ b/news/page/11.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>
@@ -561,85 +667,6 @@ <h2 id="_wildfly_patch">WildFly Patch</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2016/11/18/weld-241Final/">Weld 2.4.1.Final</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2016-11-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>The development of <strong>Weld 3</strong> (CDI 2) is underway.
-                  However, we don&#8217;t forget about the maintenance of the stable branch of Weld!
-                  So I am very pleased to announce the first bugfix 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=12331553" target="_blank" rel="noopener">the release details</a>.
-                  Thanks to everyone involved in this release!</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Notable fixes and improvements:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>removed false positive warning about Jandex version used (<a href="https://issues.jboss.org/browse/WELD-2231" target="_blank" rel="noopener">WELD-2231</a>)</p>
-                  </li>
-                  <li>
-                  <p>fixed Groovy support - only filter out relevant methods from Groovy objects when generating bean proxies (<a href="https://issues.jboss.org/browse/WELD-2255" target="_blank" rel="noopener">WELD-2255</a>)</p>
-                  </li>
-                  <li>
-                  <p>optimized proxy class generation for "large classes" (<a href="https://issues.jboss.org/browse/WELD-2244" target="_blank" rel="noopener">WELD-2244</a>)</p>
-                  </li>
-                  <li>
-                  <p>improved the way Weld configuration info is logged (<a href="https://issues.jboss.org/browse/WELD-2238" target="_blank" rel="noopener">WELD-2238</a>)</p>
-                  </li>
-                  <li>
-                  <p>Weld SE</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>added support for nested directories in uber jars, e.g. Spring Boot jar (<a href="https://issues.jboss.org/browse/WELD-2254" target="_blank" rel="noopener">WELD-2254</a>)</p>
-                  </li>
-                  <li>
-                  <p>allow to use <code>CDI.getBeanManager()</code> after <code>BeforeBeanDiscovery</code> is fired (<a href="https://issues.jboss.org/browse/WELD-2256" target="_blank" rel="noopener">WELD-2256</a>)</p>
-                  </li>
-                  <li>
-                  <p>don&#8217;t abort container initialization if <code>JandexClassFileServices</code> is unable to load an annotation (<a href="https://issues.jboss.org/browse/WELD-2232" target="_blank" rel="noopener">WELD-2232</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Weld Servlet - document the usage of <code>org.jboss.weld.environment.container.class</code> init param (<a href="https://issues.jboss.org/browse/WELD-2236" target="_blank" rel="noopener">WELD-2236</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.4.1.Final/wildfly-10.1.0.Final-weld-2.4.1.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 <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.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=12331553" target="_blank" rel="noopener">Release notes</a> &#93;</p>
-                  </div>
-                  </div>
-                  </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/18.html" class="page-link">18</a> <a href="/news/page/19.html" class="page-link">19</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 e694be8a..823df899 100644
--- a/news/page/12.html
+++ b/news/page/12.html
@@ -141,6 +141,85 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2016/11/18/weld-241Final/">Weld 2.4.1.Final</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2016-11-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>The development of <strong>Weld 3</strong> (CDI 2) is underway.
+                  However, we don&#8217;t forget about the maintenance of the stable branch of Weld!
+                  So I am very pleased to announce the first bugfix 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=12331553" target="_blank" rel="noopener">the release details</a>.
+                  Thanks to everyone involved in this release!</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Notable fixes and improvements:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>removed false positive warning about Jandex version used (<a href="https://issues.jboss.org/browse/WELD-2231" target="_blank" rel="noopener">WELD-2231</a>)</p>
+                  </li>
+                  <li>
+                  <p>fixed Groovy support - only filter out relevant methods from Groovy objects when generating bean proxies (<a href="https://issues.jboss.org/browse/WELD-2255" target="_blank" rel="noopener">WELD-2255</a>)</p>
+                  </li>
+                  <li>
+                  <p>optimized proxy class generation for "large classes" (<a href="https://issues.jboss.org/browse/WELD-2244" target="_blank" rel="noopener">WELD-2244</a>)</p>
+                  </li>
+                  <li>
+                  <p>improved the way Weld configuration info is logged (<a href="https://issues.jboss.org/browse/WELD-2238" target="_blank" rel="noopener">WELD-2238</a>)</p>
+                  </li>
+                  <li>
+                  <p>Weld SE</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>added support for nested directories in uber jars, e.g. Spring Boot jar (<a href="https://issues.jboss.org/browse/WELD-2254" target="_blank" rel="noopener">WELD-2254</a>)</p>
+                  </li>
+                  <li>
+                  <p>allow to use <code>CDI.getBeanManager()</code> after <code>BeforeBeanDiscovery</code> is fired (<a href="https://issues.jboss.org/browse/WELD-2256" target="_blank" rel="noopener">WELD-2256</a>)</p>
+                  </li>
+                  <li>
+                  <p>don&#8217;t abort container initialization if <code>JandexClassFileServices</code> is unable to load an annotation (<a href="https://issues.jboss.org/browse/WELD-2232" target="_blank" rel="noopener">WELD-2232</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Weld Servlet - document the usage of <code>org.jboss.weld.environment.container.class</code> init param (<a href="https://issues.jboss.org/browse/WELD-2236" target="_blank" rel="noopener">WELD-2236</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.4.1.Final/wildfly-10.1.0.Final-weld-2.4.1.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 <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.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=12331553" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2016/10/25/tip3-performance/">Weld Tip 3 - Boost performance of Weld apps</a>
@@ -949,184 +1028,6 @@ <h2 id="_wildfly_patch">WildFly Patch</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2016/08/19/weld-240CR1/">First release candidate of Weld 2.4</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2016-8-19
-                  &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 id="toc" class="toc">
-                  <div id="toctitle" class="title">Contents</div>
-                  <ul class="sectlevel1">
-                  <li><a href="#_removed_dependency_on_com_google_guavaguava">Removed dependency on <code>com.google.guava:guava</code></a></li>
-                  <li><a href="#_enhanced_version_of_javax_enterprise_inject_instance">Enhanced version of <code>javax.enterprise.inject.Instance</code></a></li>
-                  <li><a href="#_veto_annotatedtype_not_annotated_with_bean_defining_annotation">Veto <code>AnnotatedType</code> not annotated with bean defining annotation</a></li>
-                  <li><a href="#_activaterequestscope_moved_to_weld_api"><code>@ActivateRequestScope</code> moved to Weld API</a></li>
-                  <li><a href="#_improved_rolling_upgrades_support">Improved rolling upgrades support</a></li>
-                  <li><a href="#_events_reflect_the_output_of_cdi_494">Events - reflect the output of CDI-494</a></li>
-                  <li><a href="#_probe_allow_to_filter_unused_beans">Probe - allow to filter unused beans</a></li>
-                  <li><a href="#_cleanup">Cleanup</a></li>
-                  <li><a href="#_initial_java_9_support">Initial Java 9 support</a></li>
-                  <li><a href="#_bugs">Bugs</a></li>
-                  <li><a href="#_wildfly_patch">WildFly Patch</a></li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>I am pleased to announce the first release candidate of Weld 2.4 (CDI 1.2).
-                  See also <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12330683" target="_blank" rel="noopener">the release details</a>.
-                  Thanks to everyone involved in this release!</p>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_removed_dependency_on_com_google_guavaguava">Removed dependency on <code>com.google.guava:guava</code></h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>Weld does not depend on <code>com.google.guava:guava</code> anymore (actually, Weld 3 does not depend on guava since 3.0.0.Alpha2).
-                  This significantly reduces the footprint of both Weld SE and Weld Servlet.
-                  The dependency is also not bundled with shaded artifacts for Weld SE and Weld Servlet.</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_enhanced_version_of_javax_enterprise_inject_instance">Enhanced version of <code>javax.enterprise.inject.Instance</code></h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>Weld now provides <code>org.jboss.weld.inject.WeldInstance</code> - an enhanced version of <code>javax.enterprise.inject.Instance</code>.
-                  There are three additional methods - <code>getHandler()</code>, <code>handlers()</code> and <code>isResolvable()</code>.
-                  A handler allows to inspect the metadata of the relevant bean and to destroy the underlying contextual instance.
-                  <code>isResolvable()</code> is just a convenient method - a replacement for <code>!isUnsatisfied() &amp;&amp; !isAmbiguous()</code>.
-                  For more details see also <a href="http://docs.jboss.org/weld/reference/2.4.0.CR1/en-US/html/injection.html#_enhanced_version_of_literal_javax_enterprise_inject_instance_literal" target="_blank" rel="noopener">the reference guide</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p><code>WeldInstance</code> is automatically available in Weld SE and Weld Servlet where the Weld API is always on the class path.
-                  It is also available in Weld-powered EE containers. In this case, users would have to compile their application against the Weld API and exclude the Weld API artifact from the deployment (e.g. use provided scope in Maven).</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>This functionality is based on a new proposal for <a href="https://issues.jboss.org/browse/CDI-589" target="_blank" rel="noopener">CDI-589</a>.</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_veto_annotatedtype_not_annotated_with_bean_defining_annotation">Veto <code>AnnotatedType</code> not annotated with bean defining annotation</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>Sometimes it might be useful to process all types during bootstrap, i.e. fire/observe <code>ProcessAnnotatedType</code> event for each Java class discovered, but veto types which are <strong>not annotated with a bean defining annotation</strong>.
-                  The main reason is that not all classes that meet all of the necessary conditions are intended to become beans.
-                  And so vetoing such types helps to conserve memory used by the container.
-                  Note that if you use <code>bean-discovey-mode=annotated</code> (implicit bean archive) then no <code>ProcessAnnotatedType</code> will be fired for any such type because it’s not discovered at all.
-                  And there might be portable extensions which use <code>ProcessAnnotatedType</code> to extract some important information from classes which are not beans.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Therefore, Weld allows to use <code>bean-discovey-mode=all</code> (explicit bean archive) and veto types without a bean defining annotation whose <code>AnnotatedType#getJavaClass().getName()</code> matches a <a href="http://docs.jboss.org/weld/reference/2.4.0.CR1/en-US/html/configure.html#veto-types-without-bean-defining-annotation">regular expression</a>.
-                  In other words, a type is vetoed if its name matches a regular expression and at the same time is not annotated with a bean defining annotation.
-                  This functionality is implemented as a built-in portable extension processing all types from all bean archives (it was already doable using an extension but we believe it&#8217;s more convenient to have this functionality out of the box).</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>This is a workaround for problems of <code>bean-discovey-mode=annotated</code> mentioned in <a href="https://issues.jboss.org/browse/CDI-420" target="_blank" rel="noopener">CDI-420</a>.</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_activaterequestscope_moved_to_weld_api"><code>@ActivateRequestScope</code> moved to Weld API</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>This interceptor binding can be used to activate the request scope within a business method invocation.
-                  It was previously part of the Weld SE but we believe it might be useful in any environment.
-                  See also <a href="https://issues.jboss.org/browse/WELD-2150" target="_blank" rel="noopener">WELD-2150</a>.</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_improved_rolling_upgrades_support">Improved rolling upgrades support</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p><a href="https://issues.jboss.org/secure/ViewProfile.jspa?name=lprimak">Lenny Primak</a> (a Weld community member - thanks for the report again!) struggled with rolling upgrades on certain application servers (Payara, GlassFish).
-                  Therefore, a new configuration property was introduced.
-                  This property allows to specify a delimiter which is used to abbreviate a bean archive identifier (which is usually derived from the archive name) before used as a part of an identifier of an internal component (such as bean).
-                  See also <a href="http://docs.jboss.org/weld/reference/2.4.0.CR1/en-US/html/configure.html#_rolling_upgrades_id_delimiter" target="_blank" rel="noopener">the reference guide</a> and <a href="https://issues.jboss.org/browse/WELD-2064" target="_blank" rel="noopener">WELD-2064</a>.</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_events_reflect_the_output_of_cdi_494">Events - reflect the output of CDI-494</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>This change reflects the clarification around <code>Event</code> operations - <em>"A wildcard type is not considered an unresolvable type variable"</em>.
-                  See also <a href="https://issues.jboss.org/browse/WELD-2137" target="_blank" rel="noopener">WELD-2137</a> and <a href="https://issues.jboss.org/browse/CDI-494" target="_blank" rel="noopener">CDI-494</a>.
-                  Simply said, the snippet below and similar ones should now work:</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@Inject Event&lt;List&lt;?&gt;&gt; event;&#x000A;    &#x000A;    public void fireLists() {&#x000A;      List&lt;String&gt; stringList = new ArrayList&lt;&gt;();&#x000A;      event.fire(stringList);&#x000A;      List&lt;Integer&gt; intList = new ArrayList&lt;&gt;();&#x000A;      event.fire(intList);&#x000A;    }&#x000A;    &#x000A;    void observeAllLists(@Observes List&lt;?&gt; anyList) {&#x000A;      // Will be notified&#x000A;    }</code></pre>
-                  </div>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_probe_allow_to_filter_unused_beans">Probe - allow to filter unused beans</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>The Probe development tool now identifies beans which are most likely unused (a bean is considered unused if it has no direct dependents, does not declare any observer or producer methods, is not annotated with <code>@Named</code> and is not a built-in bean, extension, interceptor or decorator).
-                  This might be useful to identify types suitable for vetoing as mentioned in <a href="#_veto_code_annotatedtype_code_not_annotated_with_bean_defining_annotation">[_veto_code_annotatedtype_code_not_annotated_with_bean_defining_annotation]</a>.</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_cleanup">Cleanup</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>Weld has underwent an internal cleanup. A lot of deprecated and unused classes were removed.</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_initial_java_9_support">Initial Java 9 support</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>It&#8217;s now possible to build Weld with Java 9.
-                  Note that this does not mean that Weld is modularized in a <a href="http://openjdk.java.net/projects/jigsaw/" target="_blank" rel="noopener">Jigsaw way</a>.
-                  It&#8217;s just the first step on a long road ;-).</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_bugs">Bugs</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>Last but not least - a few bugs were killed.
-                  Weld SE - provided <code>ClassLoader</code> is also used to load extensions (<a href="https://issues.jboss.org/browse/WELD-2209" target="_blank" rel="noopener">WELD-2209</a>).
-                  <code>AnnotatedTypeValidator</code> does consider extended interfaces (<a href="https://issues.jboss.org/browse/WELD-2221" target="_blank" rel="noopener">WELD-2221</a>).
-                  Invocation of a JDK8 default method should be intercepted (this only works if using <code>jboss-classfilewriter</code> 1.2.0.Beta1+, <a href="https://issues.jboss.org/browse/WELD-2093" target="_blank" rel="noopener">WELD-2093</a>).</p>
-                  </div>
-                  </div>
-                  </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.0.CR1/wildfly-10.0.0.Final-weld-2.4.0.CR1-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.4.0.CR1/en-US/html/" target="_blank" rel="noopener">Documentation</a> &#93;
-                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12330683" 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/18.html" class="page-link">18</a> <a href="/news/page/19.html" class="page-link">19</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 c83c41cb..bb9d8ba0 100644
--- a/news/page/13.html
+++ b/news/page/13.html
@@ -141,6 +141,184 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2016/08/19/weld-240CR1/">First release candidate of Weld 2.4</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2016-8-19
+                  &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 id="toc" class="toc">
+                  <div id="toctitle" class="title">Contents</div>
+                  <ul class="sectlevel1">
+                  <li><a href="#_removed_dependency_on_com_google_guavaguava">Removed dependency on <code>com.google.guava:guava</code></a></li>
+                  <li><a href="#_enhanced_version_of_javax_enterprise_inject_instance">Enhanced version of <code>javax.enterprise.inject.Instance</code></a></li>
+                  <li><a href="#_veto_annotatedtype_not_annotated_with_bean_defining_annotation">Veto <code>AnnotatedType</code> not annotated with bean defining annotation</a></li>
+                  <li><a href="#_activaterequestscope_moved_to_weld_api"><code>@ActivateRequestScope</code> moved to Weld API</a></li>
+                  <li><a href="#_improved_rolling_upgrades_support">Improved rolling upgrades support</a></li>
+                  <li><a href="#_events_reflect_the_output_of_cdi_494">Events - reflect the output of CDI-494</a></li>
+                  <li><a href="#_probe_allow_to_filter_unused_beans">Probe - allow to filter unused beans</a></li>
+                  <li><a href="#_cleanup">Cleanup</a></li>
+                  <li><a href="#_initial_java_9_support">Initial Java 9 support</a></li>
+                  <li><a href="#_bugs">Bugs</a></li>
+                  <li><a href="#_wildfly_patch">WildFly Patch</a></li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>I am pleased to announce the first release candidate of Weld 2.4 (CDI 1.2).
+                  See also <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12330683" target="_blank" rel="noopener">the release details</a>.
+                  Thanks to everyone involved in this release!</p>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_removed_dependency_on_com_google_guavaguava">Removed dependency on <code>com.google.guava:guava</code></h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>Weld does not depend on <code>com.google.guava:guava</code> anymore (actually, Weld 3 does not depend on guava since 3.0.0.Alpha2).
+                  This significantly reduces the footprint of both Weld SE and Weld Servlet.
+                  The dependency is also not bundled with shaded artifacts for Weld SE and Weld Servlet.</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_enhanced_version_of_javax_enterprise_inject_instance">Enhanced version of <code>javax.enterprise.inject.Instance</code></h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>Weld now provides <code>org.jboss.weld.inject.WeldInstance</code> - an enhanced version of <code>javax.enterprise.inject.Instance</code>.
+                  There are three additional methods - <code>getHandler()</code>, <code>handlers()</code> and <code>isResolvable()</code>.
+                  A handler allows to inspect the metadata of the relevant bean and to destroy the underlying contextual instance.
+                  <code>isResolvable()</code> is just a convenient method - a replacement for <code>!isUnsatisfied() &amp;&amp; !isAmbiguous()</code>.
+                  For more details see also <a href="http://docs.jboss.org/weld/reference/2.4.0.CR1/en-US/html/injection.html#_enhanced_version_of_literal_javax_enterprise_inject_instance_literal" target="_blank" rel="noopener">the reference guide</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p><code>WeldInstance</code> is automatically available in Weld SE and Weld Servlet where the Weld API is always on the class path.
+                  It is also available in Weld-powered EE containers. In this case, users would have to compile their application against the Weld API and exclude the Weld API artifact from the deployment (e.g. use provided scope in Maven).</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>This functionality is based on a new proposal for <a href="https://issues.jboss.org/browse/CDI-589" target="_blank" rel="noopener">CDI-589</a>.</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_veto_annotatedtype_not_annotated_with_bean_defining_annotation">Veto <code>AnnotatedType</code> not annotated with bean defining annotation</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>Sometimes it might be useful to process all types during bootstrap, i.e. fire/observe <code>ProcessAnnotatedType</code> event for each Java class discovered, but veto types which are <strong>not annotated with a bean defining annotation</strong>.
+                  The main reason is that not all classes that meet all of the necessary conditions are intended to become beans.
+                  And so vetoing such types helps to conserve memory used by the container.
+                  Note that if you use <code>bean-discovey-mode=annotated</code> (implicit bean archive) then no <code>ProcessAnnotatedType</code> will be fired for any such type because it’s not discovered at all.
+                  And there might be portable extensions which use <code>ProcessAnnotatedType</code> to extract some important information from classes which are not beans.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Therefore, Weld allows to use <code>bean-discovey-mode=all</code> (explicit bean archive) and veto types without a bean defining annotation whose <code>AnnotatedType#getJavaClass().getName()</code> matches a <a href="http://docs.jboss.org/weld/reference/2.4.0.CR1/en-US/html/configure.html#veto-types-without-bean-defining-annotation">regular expression</a>.
+                  In other words, a type is vetoed if its name matches a regular expression and at the same time is not annotated with a bean defining annotation.
+                  This functionality is implemented as a built-in portable extension processing all types from all bean archives (it was already doable using an extension but we believe it&#8217;s more convenient to have this functionality out of the box).</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>This is a workaround for problems of <code>bean-discovey-mode=annotated</code> mentioned in <a href="https://issues.jboss.org/browse/CDI-420" target="_blank" rel="noopener">CDI-420</a>.</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_activaterequestscope_moved_to_weld_api"><code>@ActivateRequestScope</code> moved to Weld API</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>This interceptor binding can be used to activate the request scope within a business method invocation.
+                  It was previously part of the Weld SE but we believe it might be useful in any environment.
+                  See also <a href="https://issues.jboss.org/browse/WELD-2150" target="_blank" rel="noopener">WELD-2150</a>.</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_improved_rolling_upgrades_support">Improved rolling upgrades support</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p><a href="https://issues.jboss.org/secure/ViewProfile.jspa?name=lprimak">Lenny Primak</a> (a Weld community member - thanks for the report again!) struggled with rolling upgrades on certain application servers (Payara, GlassFish).
+                  Therefore, a new configuration property was introduced.
+                  This property allows to specify a delimiter which is used to abbreviate a bean archive identifier (which is usually derived from the archive name) before used as a part of an identifier of an internal component (such as bean).
+                  See also <a href="http://docs.jboss.org/weld/reference/2.4.0.CR1/en-US/html/configure.html#_rolling_upgrades_id_delimiter" target="_blank" rel="noopener">the reference guide</a> and <a href="https://issues.jboss.org/browse/WELD-2064" target="_blank" rel="noopener">WELD-2064</a>.</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_events_reflect_the_output_of_cdi_494">Events - reflect the output of CDI-494</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>This change reflects the clarification around <code>Event</code> operations - <em>"A wildcard type is not considered an unresolvable type variable"</em>.
+                  See also <a href="https://issues.jboss.org/browse/WELD-2137" target="_blank" rel="noopener">WELD-2137</a> and <a href="https://issues.jboss.org/browse/CDI-494" target="_blank" rel="noopener">CDI-494</a>.
+                  Simply said, the snippet below and similar ones should now work:</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@Inject Event&lt;List&lt;?&gt;&gt; event;&#x000A;    &#x000A;    public void fireLists() {&#x000A;      List&lt;String&gt; stringList = new ArrayList&lt;&gt;();&#x000A;      event.fire(stringList);&#x000A;      List&lt;Integer&gt; intList = new ArrayList&lt;&gt;();&#x000A;      event.fire(intList);&#x000A;    }&#x000A;    &#x000A;    void observeAllLists(@Observes List&lt;?&gt; anyList) {&#x000A;      // Will be notified&#x000A;    }</code></pre>
+                  </div>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_probe_allow_to_filter_unused_beans">Probe - allow to filter unused beans</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>The Probe development tool now identifies beans which are most likely unused (a bean is considered unused if it has no direct dependents, does not declare any observer or producer methods, is not annotated with <code>@Named</code> and is not a built-in bean, extension, interceptor or decorator).
+                  This might be useful to identify types suitable for vetoing as mentioned in <a href="#_veto_code_annotatedtype_code_not_annotated_with_bean_defining_annotation">[_veto_code_annotatedtype_code_not_annotated_with_bean_defining_annotation]</a>.</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_cleanup">Cleanup</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>Weld has underwent an internal cleanup. A lot of deprecated and unused classes were removed.</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_initial_java_9_support">Initial Java 9 support</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>It&#8217;s now possible to build Weld with Java 9.
+                  Note that this does not mean that Weld is modularized in a <a href="http://openjdk.java.net/projects/jigsaw/" target="_blank" rel="noopener">Jigsaw way</a>.
+                  It&#8217;s just the first step on a long road ;-).</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_bugs">Bugs</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>Last but not least - a few bugs were killed.
+                  Weld SE - provided <code>ClassLoader</code> is also used to load extensions (<a href="https://issues.jboss.org/browse/WELD-2209" target="_blank" rel="noopener">WELD-2209</a>).
+                  <code>AnnotatedTypeValidator</code> does consider extended interfaces (<a href="https://issues.jboss.org/browse/WELD-2221" target="_blank" rel="noopener">WELD-2221</a>).
+                  Invocation of a JDK8 default method should be intercepted (this only works if using <code>jboss-classfilewriter</code> 1.2.0.Beta1+, <a href="https://issues.jboss.org/browse/WELD-2093" target="_blank" rel="noopener">WELD-2093</a>).</p>
+                  </div>
+                  </div>
+                  </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.0.CR1/wildfly-10.0.0.Final-weld-2.4.0.CR1-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.4.0.CR1/en-US/html/" target="_blank" rel="noopener">Documentation</a> &#93;
+                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12330683" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </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>
@@ -450,157 +628,6 @@ <h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2016/04/28/weld-300Alpha16/">Weld 3.0.0.Alpha16</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2016-4-28
-                  &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>
-                  Martin Kouba
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>The next experimental Weld version has been released!
-                  See also <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12327858" target="_blank" rel="noopener">the release details</a>.
-                  Thanks to everyone involved in this release!</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>This release includes a lot of bugfixes and improvements (e.g. all the notable tasks implemented in the latest stable version: <a href="/news/2016/04/22/weld-234Final/">Weld 2.3.4.Final</a>).
-                  However, the main goal of this release is to align with CDI API 2.0.Alpha4, and in particular to implement the current version of "metadata builders" API (<a href="https://issues.jboss.org/browse/CDI-558" target="_blank" rel="noopener">CDI-558</a>).
-                  So that everyone can play with the API, discover possibilities and find potential issues.
-                  Note that this release also introduces a non-standard experimental feature: <a href="/news/2016/02/08/weld-se-synth-lifecycle-events/">Weld SE synthetic container lifecycle event observers</a>.
-                  So it should be even easier to get started - no extension class is needed in Weld SE.</p>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_metadata_configurators_basic_ideas">Metadata configurators - basic ideas</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>Note that we don&#8217;t use the term "builder" because there is no <code>build()</code> method in the API.
-                  Also note that the API is not intended to cover every possible case.
-                  Instead, we would like to help with common tasks.
-                  And if necessary, an extension developer can always use the original replacement methods for more complicated stuff.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>IMPORTANT POINTS:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>an extension developer receives a configurator instance from a container lifecycle event</p>
-                  </li>
-                  <li>
-                  <p>a configurator instance is always automatically processed at the end of the observer invocation</p>
-                  </li>
-                  <li>
-                  <p>for <strong>bean discovery events</strong> (all events starting with <code>Process</code>):</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p><code>configureX()</code> methods return the same configurator instance (for the given observer method invocation)</p>
-                  </li>
-                  <li>
-                  <p>the configurator is initialized/preconfigured with the component being processed, e.g. <code>ProcessAnnotatedType.configureAnnotatedType()</code> returns a configurator initialized with <code>ProcessAnnotatedType.getAnnotatedType()</code></p>
-                  </li>
-                  <li>
-                  <p>the result of the configurator will automatically replace the original component (e.g. <code>AnnotatedType</code> in case of <code>ProcessAnnotatedType</code>)</p>
-                  </li>
-                  <li>
-                  <p>replacement methods (e.g. <code>ProcessAnnotatedType.setAnnotatedType()</code>) should not be used together with configurators (<a href="https://issues.jboss.org/browse/CDI-596" target="_blank" rel="noopener">CDI-596</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>for <strong>application lifecycle events</strong> (e.g. <code>AfterBeanDiscovery</code>):</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p><code>addX()</code> methods always return a new configurator instance</p>
-                  </li>
-                  <li>
-                  <p>the configurator is always uninitialized/empty, but we should probably define some default values wherever it makes sense (e.g. <code>Reception</code> for observer methods)</p>
-                  </li>
-                  <li>
-                  <p>the result of the configurator will be automatically added (e.g. <code>Bean</code> in case of <code>AfterBeanDiscovery.addBean()</code>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>We have prepared some simple examples - see below.
-                  More advanced examples can be found in <a href="https://github.com/cdi-spec/cdi-tck/tree/master/impl/src/main/java/org/jboss/cdi/tck/tests/extensions/configurators" target="_blank" rel="noopener">the TCK test cases</a>.
-                  And as usual - feel free to add comments to this blog post. Any feedback is appreciated!</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_beforebeandiscovery_example">BeforeBeanDiscovery example</h2>
-                  <div class="sectionbody">
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@Singleton&#x000A;    class MyService {&#x000A;        // This class is not placed in a bean archive&#x000A;    }&#x000A;    &#x000A;    class MyExtension implements Extension {&#x000A;    &#x000A;        void beforeBeanDiscovery(@Observes BeforeBeanDiscovery event) {&#x000A;            // Add MyService to the set of discovered classes and replace @Singleton with @ApplicationScoped&#x000A;            event.addAnnotatedType(MyService.class.getName(), MyService.class)&#x000A;                   .remove(Singleton.class)&#x000A;                   .add(ApplicationScoped.Literal.INSTANCE);&#x000A;        }&#x000A;    }</code></pre>
-                  </div>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_processannotatedtype_example">ProcessAnnotatedType example</h2>
-                  <div class="sectionbody">
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">class MyExtension implements Extension {&#x000A;    &#x000A;        void processAnnotatedType(@Observes @WithAnnotations({ Observes.class, ObservesAsync.class }) ProcessAnnotatedType&lt;?&gt; event) {&#x000A;            // Add interceptor binding to all methods annotated with @Observes or @ObservesAsync&#x000A;            event.configureAnnotatedType()&#x000A;                    .filterMethods(MyExtension::isObserver)&#x000A;                    .forEach(methodConfigurator -&gt; methodConfigurator.add(Monitored.Literal.INSTANCE))&#x000A;        }&#x000A;    &#x000A;        static boolean isObserver(AnnotatedMethod&lt;?&gt; annotatedMethod) {&#x000A;            return annotatedMethod.isAnnotationPresent(Observes.class) || annotatedMethod.isAnnotationPresent(ObservesAsync.class);&#x000A;        }&#x000A;    }</code></pre>
-                  </div>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_processbeanattributes_example">ProcessBeanAttributes example</h2>
-                  <div class="sectionbody">
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">class MyExtension implements Extension {&#x000A;    &#x000A;        void processBeanAttributes(@Observes ProcessBeanAttributes&lt;?&gt; event) {&#x000A;            // For all beans remove the IllegalBeanType from the set of bean types&#x000A;            if (event.getBeanAttributes().getTypes().contains(IllegalBeanType.class)) {&#x000A;                Set&lt;Type&gt; legalTypes = new HashSet(event.getBeanAttributes().getTypes());&#x000A;                legalTypes.remove(IllegalBeanType.class);&#x000A;                event.configureBeanAttributes().types(legalTypes);&#x000A;            }&#x000A;        }&#x000A;    }</code></pre>
-                  </div>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_afterbeandiscovery_example">AfterBeanDiscovery example</h2>
-                  <div class="sectionbody">
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">class MyExtension implements Extension {&#x000A;    &#x000A;        void afterBeanDiscovery(@Observes AfterBeanDiscovery event) {&#x000A;            //  Add a new synthetic observer method - no need to use the fluent API&#x000A;            ObserverMethodConfigurator&lt;Foo&gt; configurator = event.&lt;Foo&gt;addObserverMethod();&#x000A;            configurator.observedType(Foo.class);&#x000A;            configurator.reception(Reception.ALWAYS);&#x000A;            configurator.transactionPhase(TransactionPhase.IN_PROGRESS);&#x000A;            configurator.notifyWith((foo) -&gt; System.out.println("Foo observed: " + foo));&#x000A;    &#x000A;            // Add dependent bean - Integer between 0 and 999&#x000A;            event.addBean().addType(Integer.class).addQualifier(Random.Literal.INSTANCE)&#x000A;                    .produceWith(() -&gt; new java.util.Random().nextInt(1000))&#x000A;        }&#x000A;    }</code></pre>
-                  </div>
-                  </div>
-                  </div>
-                  </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.Alpha16/wildfly-10.0.0.Final-weld-3.0.0.Alpha16-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="/download/">Download</a> &#93;
-                  &#91; <a href="http://docs.jboss.org/weld/reference/3.0.0.Alpha16/en-US/html/" target="_blank" rel="noopener">Documentation</a> &#93;
-                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12327858" target="_blank" rel="noopener">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/18.html" class="page-link">18</a> <a href="/news/page/19.html" class="page-link">19</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 786a3499..a92a627d 100644
--- a/news/page/14.html
+++ b/news/page/14.html
@@ -141,6 +141,157 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2016/04/28/weld-300Alpha16/">Weld 3.0.0.Alpha16</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2016-4-28
+                  &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>
+                  Martin Kouba
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>The next experimental Weld version has been released!
+                  See also <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12327858" target="_blank" rel="noopener">the release details</a>.
+                  Thanks to everyone involved in this release!</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>This release includes a lot of bugfixes and improvements (e.g. all the notable tasks implemented in the latest stable version: <a href="/news/2016/04/22/weld-234Final/">Weld 2.3.4.Final</a>).
+                  However, the main goal of this release is to align with CDI API 2.0.Alpha4, and in particular to implement the current version of "metadata builders" API (<a href="https://issues.jboss.org/browse/CDI-558" target="_blank" rel="noopener">CDI-558</a>).
+                  So that everyone can play with the API, discover possibilities and find potential issues.
+                  Note that this release also introduces a non-standard experimental feature: <a href="/news/2016/02/08/weld-se-synth-lifecycle-events/">Weld SE synthetic container lifecycle event observers</a>.
+                  So it should be even easier to get started - no extension class is needed in Weld SE.</p>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_metadata_configurators_basic_ideas">Metadata configurators - basic ideas</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>Note that we don&#8217;t use the term "builder" because there is no <code>build()</code> method in the API.
+                  Also note that the API is not intended to cover every possible case.
+                  Instead, we would like to help with common tasks.
+                  And if necessary, an extension developer can always use the original replacement methods for more complicated stuff.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>IMPORTANT POINTS:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>an extension developer receives a configurator instance from a container lifecycle event</p>
+                  </li>
+                  <li>
+                  <p>a configurator instance is always automatically processed at the end of the observer invocation</p>
+                  </li>
+                  <li>
+                  <p>for <strong>bean discovery events</strong> (all events starting with <code>Process</code>):</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p><code>configureX()</code> methods return the same configurator instance (for the given observer method invocation)</p>
+                  </li>
+                  <li>
+                  <p>the configurator is initialized/preconfigured with the component being processed, e.g. <code>ProcessAnnotatedType.configureAnnotatedType()</code> returns a configurator initialized with <code>ProcessAnnotatedType.getAnnotatedType()</code></p>
+                  </li>
+                  <li>
+                  <p>the result of the configurator will automatically replace the original component (e.g. <code>AnnotatedType</code> in case of <code>ProcessAnnotatedType</code>)</p>
+                  </li>
+                  <li>
+                  <p>replacement methods (e.g. <code>ProcessAnnotatedType.setAnnotatedType()</code>) should not be used together with configurators (<a href="https://issues.jboss.org/browse/CDI-596" target="_blank" rel="noopener">CDI-596</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>for <strong>application lifecycle events</strong> (e.g. <code>AfterBeanDiscovery</code>):</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p><code>addX()</code> methods always return a new configurator instance</p>
+                  </li>
+                  <li>
+                  <p>the configurator is always uninitialized/empty, but we should probably define some default values wherever it makes sense (e.g. <code>Reception</code> for observer methods)</p>
+                  </li>
+                  <li>
+                  <p>the result of the configurator will be automatically added (e.g. <code>Bean</code> in case of <code>AfterBeanDiscovery.addBean()</code>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>We have prepared some simple examples - see below.
+                  More advanced examples can be found in <a href="https://github.com/cdi-spec/cdi-tck/tree/master/impl/src/main/java/org/jboss/cdi/tck/tests/extensions/configurators" target="_blank" rel="noopener">the TCK test cases</a>.
+                  And as usual - feel free to add comments to this blog post. Any feedback is appreciated!</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_beforebeandiscovery_example">BeforeBeanDiscovery example</h2>
+                  <div class="sectionbody">
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@Singleton&#x000A;    class MyService {&#x000A;        // This class is not placed in a bean archive&#x000A;    }&#x000A;    &#x000A;    class MyExtension implements Extension {&#x000A;    &#x000A;        void beforeBeanDiscovery(@Observes BeforeBeanDiscovery event) {&#x000A;            // Add MyService to the set of discovered classes and replace @Singleton with @ApplicationScoped&#x000A;            event.addAnnotatedType(MyService.class.getName(), MyService.class)&#x000A;                   .remove(Singleton.class)&#x000A;                   .add(ApplicationScoped.Literal.INSTANCE);&#x000A;        }&#x000A;    }</code></pre>
+                  </div>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_processannotatedtype_example">ProcessAnnotatedType example</h2>
+                  <div class="sectionbody">
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">class MyExtension implements Extension {&#x000A;    &#x000A;        void processAnnotatedType(@Observes @WithAnnotations({ Observes.class, ObservesAsync.class }) ProcessAnnotatedType&lt;?&gt; event) {&#x000A;            // Add interceptor binding to all methods annotated with @Observes or @ObservesAsync&#x000A;            event.configureAnnotatedType()&#x000A;                    .filterMethods(MyExtension::isObserver)&#x000A;                    .forEach(methodConfigurator -&gt; methodConfigurator.add(Monitored.Literal.INSTANCE))&#x000A;        }&#x000A;    &#x000A;        static boolean isObserver(AnnotatedMethod&lt;?&gt; annotatedMethod) {&#x000A;            return annotatedMethod.isAnnotationPresent(Observes.class) || annotatedMethod.isAnnotationPresent(ObservesAsync.class);&#x000A;        }&#x000A;    }</code></pre>
+                  </div>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_processbeanattributes_example">ProcessBeanAttributes example</h2>
+                  <div class="sectionbody">
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">class MyExtension implements Extension {&#x000A;    &#x000A;        void processBeanAttributes(@Observes ProcessBeanAttributes&lt;?&gt; event) {&#x000A;            // For all beans remove the IllegalBeanType from the set of bean types&#x000A;            if (event.getBeanAttributes().getTypes().contains(IllegalBeanType.class)) {&#x000A;                Set&lt;Type&gt; legalTypes = new HashSet(event.getBeanAttributes().getTypes());&#x000A;                legalTypes.remove(IllegalBeanType.class);&#x000A;                event.configureBeanAttributes().types(legalTypes);&#x000A;            }&#x000A;        }&#x000A;    }</code></pre>
+                  </div>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_afterbeandiscovery_example">AfterBeanDiscovery example</h2>
+                  <div class="sectionbody">
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">class MyExtension implements Extension {&#x000A;    &#x000A;        void afterBeanDiscovery(@Observes AfterBeanDiscovery event) {&#x000A;            //  Add a new synthetic observer method - no need to use the fluent API&#x000A;            ObserverMethodConfigurator&lt;Foo&gt; configurator = event.&lt;Foo&gt;addObserverMethod();&#x000A;            configurator.observedType(Foo.class);&#x000A;            configurator.reception(Reception.ALWAYS);&#x000A;            configurator.transactionPhase(TransactionPhase.IN_PROGRESS);&#x000A;            configurator.notifyWith((foo) -&gt; System.out.println("Foo observed: " + foo));&#x000A;    &#x000A;            // Add dependent bean - Integer between 0 and 999&#x000A;            event.addBean().addType(Integer.class).addQualifier(Random.Literal.INSTANCE)&#x000A;                    .produceWith(() -&gt; new java.util.Random().nextInt(1000))&#x000A;        }&#x000A;    }</code></pre>
+                  </div>
+                  </div>
+                  </div>
+                  </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.Alpha16/wildfly-10.0.0.Final-weld-3.0.0.Alpha16-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="/download/">Download</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/3.0.0.Alpha16/en-US/html/" target="_blank" rel="noopener">Documentation</a> &#93;
+                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12327858" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2016/04/22/weld-234Final/">Weld 2.3.4.Final</a>
@@ -470,73 +621,6 @@ <h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2016/02/04/weld-300Alpha15/">Weld 3.0.0.Alpha15</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2016-2-4
-                  &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>
-                  Martin Kouba
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>Weld 3.0.0.Alpha15 the next experimental Weld version has been released.
-                  See also <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12327857">the release details</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>The <code>CompletionStage</code> used to bind actions to the completion of the asynchronous delivery is now using <code>org.jboss.weld.manager.api.ExecutorServices</code> SPI as the default asynchronous execution facility.
-                  Previously, the <code>ForkJoinPool#commonPool()</code> (a default executor of the underlying <code>CompletableFuture</code>) was used.
-                  It&#8217;s an important change because the <code>ForkJoinPool#commonPool()</code> is not a good fit for Java EE.
-                  See also <a href="https://issues.jboss.org/browse/WELD-2073">WELD-2073</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>The <code>ExperimentalAfterBeanDiscovery</code> receives two more methods: <code>interceptorBuilder()</code> and <code>addInterceptor()</code>.
-                  An interceptor builder allows you to create an interceptor bean without the need to create an interceptor class.
-                  This might be handy for simple use cases:</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">class MyExtension {&#x000A;      void afterBeanDiscovery(@Observes AfterBeanDiscovery event) {&#x000A;        event.addInterceptor().intercept(InterceptionType.AROUND_INVOKE, (c) -&gt; {&#x000A;                long start = System.currentTimeMillis();&#x000A;                try {&#x000A;                    return c.proceed();&#x000A;                } finally {&#x000A;                    System.out.println("Time: " + System.currentTimeMillis() - start);&#x000A;                }&#x000A;            }).priority(2600).addBinding(MonitoringBinding.Literal.INSTANCE);&#x000A;      }&#x000A;    }</code></pre>
-                  </div>
-                  </div>
-                  <div class="paragraph">
-                  <p>See also <a href="https://issues.jboss.org/browse/WELD-2008">WELD-2008</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>This release also contains some enhancements and bugfixes around proxies.
-                  E.g. better support for DeltaSpike partial beans (<a href="https://issues.jboss.org/browse/WELD-2084">WELD-2084</a>), better support for Camel CDI (<a href="https://issues.jboss.org/browse/WELD-2089">WELD-2089</a>) and better support for proxies with non public classes (<a href="https://issues.jboss.org/browse/WELD-2091">WELD-2091</a>).
-                  Furthermore, we are going to drop Jetty 7,8, 9.0, 9.1 and 9.2 support in Weld 3 (<a href="https://issues.jboss.org/browse/WELD-2032">WELD-2032</a>).
-                  Also the decorator validation was improved (<a href="https://issues.jboss.org/browse/WELD-2085">WELD-2085</a>, <a href="https://issues.jboss.org/browse/WELD-1811">WELD-1811</a>, <a href="https://issues.jboss.org/browse/WELD-2039">WELD-2039</a>).
-                  Last but not least, we have performed some SPI cleanup (<a href="https://issues.jboss.org/browse/WELD-2077">WELD-2077</a>, <a href="https://issues.jboss.org/browse/WELD-2079">WELD-2079</a>).</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.Alpha15/wildfly-10.0.0.Final-weld-3.0.0.Alpha15-patch.zip">patch for WildFly</a> is available. This patch not only upgrades Weld within an existing WildFly instance but also upgrades CDI API to 2.0 EDR1. 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">Markus&#8217;s tutorial</a>.</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=12327857">Release notes</a> &#93;
-                  &#91; <a href="http://download.jboss.org/weld/3.0.0.Alpha15/weld-3.0.0.Alpha15.zip">Distribution</a> &#93;
-                  &#91; <a href="http://download.jboss.org/weld/3.0.0.Alpha15/wildfly-10.0.0.Final-weld-3.0.0.Alpha15-patch.zip">Patch for Wildfly 10.0.0.Final</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/18.html" class="page-link">18</a> <a href="/news/page/19.html" class="page-link">19</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 c1c650a3..9784c6ca 100644
--- a/news/page/15.html
+++ b/news/page/15.html
@@ -141,6 +141,73 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2016/02/04/weld-300Alpha15/">Weld 3.0.0.Alpha15</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2016-2-4
+                  &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>
+                  Martin Kouba
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>Weld 3.0.0.Alpha15 the next experimental Weld version has been released.
+                  See also <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12327857">the release details</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>The <code>CompletionStage</code> used to bind actions to the completion of the asynchronous delivery is now using <code>org.jboss.weld.manager.api.ExecutorServices</code> SPI as the default asynchronous execution facility.
+                  Previously, the <code>ForkJoinPool#commonPool()</code> (a default executor of the underlying <code>CompletableFuture</code>) was used.
+                  It&#8217;s an important change because the <code>ForkJoinPool#commonPool()</code> is not a good fit for Java EE.
+                  See also <a href="https://issues.jboss.org/browse/WELD-2073">WELD-2073</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>The <code>ExperimentalAfterBeanDiscovery</code> receives two more methods: <code>interceptorBuilder()</code> and <code>addInterceptor()</code>.
+                  An interceptor builder allows you to create an interceptor bean without the need to create an interceptor class.
+                  This might be handy for simple use cases:</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">class MyExtension {&#x000A;      void afterBeanDiscovery(@Observes AfterBeanDiscovery event) {&#x000A;        event.addInterceptor().intercept(InterceptionType.AROUND_INVOKE, (c) -&gt; {&#x000A;                long start = System.currentTimeMillis();&#x000A;                try {&#x000A;                    return c.proceed();&#x000A;                } finally {&#x000A;                    System.out.println("Time: " + System.currentTimeMillis() - start);&#x000A;                }&#x000A;            }).priority(2600).addBinding(MonitoringBinding.Literal.INSTANCE);&#x000A;      }&#x000A;    }</code></pre>
+                  </div>
+                  </div>
+                  <div class="paragraph">
+                  <p>See also <a href="https://issues.jboss.org/browse/WELD-2008">WELD-2008</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>This release also contains some enhancements and bugfixes around proxies.
+                  E.g. better support for DeltaSpike partial beans (<a href="https://issues.jboss.org/browse/WELD-2084">WELD-2084</a>), better support for Camel CDI (<a href="https://issues.jboss.org/browse/WELD-2089">WELD-2089</a>) and better support for proxies with non public classes (<a href="https://issues.jboss.org/browse/WELD-2091">WELD-2091</a>).
+                  Furthermore, we are going to drop Jetty 7,8, 9.0, 9.1 and 9.2 support in Weld 3 (<a href="https://issues.jboss.org/browse/WELD-2032">WELD-2032</a>).
+                  Also the decorator validation was improved (<a href="https://issues.jboss.org/browse/WELD-2085">WELD-2085</a>, <a href="https://issues.jboss.org/browse/WELD-1811">WELD-1811</a>, <a href="https://issues.jboss.org/browse/WELD-2039">WELD-2039</a>).
+                  Last but not least, we have performed some SPI cleanup (<a href="https://issues.jboss.org/browse/WELD-2077">WELD-2077</a>, <a href="https://issues.jboss.org/browse/WELD-2079">WELD-2079</a>).</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.Alpha15/wildfly-10.0.0.Final-weld-3.0.0.Alpha15-patch.zip">patch for WildFly</a> is available. This patch not only upgrades Weld within an existing WildFly instance but also upgrades CDI API to 2.0 EDR1. 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">Markus&#8217;s tutorial</a>.</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=12327857">Release notes</a> &#93;
+                  &#91; <a href="http://download.jboss.org/weld/3.0.0.Alpha15/weld-3.0.0.Alpha15.zip">Distribution</a> &#93;
+                  &#91; <a href="http://download.jboss.org/weld/3.0.0.Alpha15/wildfly-10.0.0.Final-weld-3.0.0.Alpha15-patch.zip">Patch for Wildfly 10.0.0.Final</a>
+                  &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2015/12/10/weld-232Final/">Weld 2.3.2.Final</a>
@@ -430,67 +497,6 @@ <h2 id="_jboss_forge_example">JBoss Forge example</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2015/10/27/weld-231Final/">Weld 2.3.1.Final arrives...</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2015-10-27
-                  &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.1.Final has been released! The delivery: a few killed bugs, couple of Weld SE enhancements and several Weld Probe improvements.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Notable bug-fixes and enhancements:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Private producer, disposer and observer methods should be intercepted (<a href="https://issues.jboss.org/browse/WELD-2043">WELD-2043</a>)</p>
-                  </li>
-                  <li>
-                  <p>Specializing bean - remove @Default qualifier unless explicitly declared (<a href="https://issues.jboss.org/browse/WELD-2043">WELD-2046</a>)</p>
-                  </li>
-                  <li>
-                  <p>Weld SE</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Fix the development mode enablement</p>
-                  </li>
-                  <li>
-                  <p>Allow to pass a ResourceLoader to be used for scanning (<a href="https://issues.jboss.org/browse/WELD-2043">WELD-2044</a>)</p>
-                  </li>
-                  <li>
-                  <p>Allow to skip the registration of a shutdown hook (<a href="https://issues.jboss.org/browse/WELD-2043">WELD-2051</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Weld Probe now supports monitoring of container lifecycle events during bootstrap (see also <a href="http://docs.jboss.org/weld/reference/latest/html/configure.html#config-dev-mode">supported configuration properties</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.1.Final/en-US/html/">Documentation</a> &#93;
-                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12327517">Release notes</a> &#93;</p>
-                  </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> <span class="skip">...</span><a href="/news/page/18.html" class="page-link">18</a> <a href="/news/page/19.html" class="page-link">19</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 6b2b5972..bca7b9ab 100644
--- a/news/page/16.html
+++ b/news/page/16.html
@@ -141,6 +141,67 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2015/10/27/weld-231Final/">Weld 2.3.1.Final arrives...</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2015-10-27
+                  &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.1.Final has been released! The delivery: a few killed bugs, couple of Weld SE enhancements and several Weld Probe improvements.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Notable bug-fixes and enhancements:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Private producer, disposer and observer methods should be intercepted (<a href="https://issues.jboss.org/browse/WELD-2043">WELD-2043</a>)</p>
+                  </li>
+                  <li>
+                  <p>Specializing bean - remove @Default qualifier unless explicitly declared (<a href="https://issues.jboss.org/browse/WELD-2043">WELD-2046</a>)</p>
+                  </li>
+                  <li>
+                  <p>Weld SE</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Fix the development mode enablement</p>
+                  </li>
+                  <li>
+                  <p>Allow to pass a ResourceLoader to be used for scanning (<a href="https://issues.jboss.org/browse/WELD-2043">WELD-2044</a>)</p>
+                  </li>
+                  <li>
+                  <p>Allow to skip the registration of a shutdown hook (<a href="https://issues.jboss.org/browse/WELD-2043">WELD-2051</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Weld Probe now supports monitoring of container lifecycle events during bootstrap (see also <a href="http://docs.jboss.org/weld/reference/latest/html/configure.html#config-dev-mode">supported configuration properties</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.1.Final/en-US/html/">Documentation</a> &#93;
+                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12327517">Release notes</a> &#93;</p>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2015/09/18/weld-230Final/">Weld 2.3.0.Final released!</a>
@@ -496,160 +557,6 @@ <h2 id="_wildfly_patch">WildFly Patch</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2015/04/21/weld-300Alpha8/">Weld 3.0.0.Alpha8</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2015-4-21
-                  &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.Alpha8 has been released.
-                  The main change is the enhanced API for using Weld in Java SE environment. In addition, this release comes with several weld-probe improvements.</p>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_enhanced_api_for_weld_se">Enhanced API for Weld SE</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>Weld has provided <a href="http://docs.jboss.org/weld/reference/latest-2.2/en-US/html/environments.html#_java_se">support for the Java SE environment</a> for a long time with the weld-se module.
-                  The API provides an easy way for an application to initialize Weld and use it in a standalone mode.
-                  On initialization Weld SE scans the classpath for bean archives with the <code>beans.xml</code> file, similarly to how it&#8217;s done in the Java EE environment.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>In this release we are extending the API further.
-                  This is partially inspired by the current discussion in the CDI expert group where a standardized CDI API for Java SE is being proposed as part of <a href="https://issues.jboss.org/browse/CDI-26">CDI-26</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>The following code snippet shows the new API in action:</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">Weld builder = new Weld()&#x000A;        .disableDiscovery()&#x000A;        .packages(Main.class, Utils.class)&#x000A;        .interceptors(TransactionalInterceptor.class)&#x000A;        .property("org.jboss.weld.construction.relaxed", true);&#x000A;    &#x000A;    try (WeldContainer weld = builder.initialize()) {&#x000A;        MyBean bean = weld.select(MyBean.class).get();&#x000A;        System.out.println(bean.computeResult());&#x000A;    }</code></pre>
-                  </div>
-                  </div>
-                  <div class="paragraph">
-                  <p>There are several new things to notice:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>the <code>Weld</code> class is used as a builder to configure Weld before it is initialized</p>
-                  </li>
-                  <li>
-                  <p>automatic scanning can be disabled</p>
-                  </li>
-                  <li>
-                  <p>instead of scanning, classes or packages can be selected explicitly. All classes in those packages will be managed by Weld</p>
-                  </li>
-                  <li>
-                  <p>interceptors, decorators, extensions and <a href="http://docs.jboss.org/weld/reference/3.0.0.Alpha8/en-US/html/configure.html#_weld_configuration">Weld-specific configuration options</a> can be specified using the builder</p>
-                  </li>
-                  <li>
-                  <p><code>WeldContainer</code> now implements <code>AutoCloseable</code> and can therefore be used in a <code>try-with-resources</code> block. At any time that execution gets outside of the code block, the Weld instance is shut down and all managed instances are safely destroyed.</p>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>It is also possible to start multiple independent Weld instances:</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">new Weld().disableDiscovery().containerId("one").beanClasses(MyBean.class).initialize();&#x000A;    new Weld().disableDiscovery().containerId("two").beanClasses(OtherBean.class).initialize();&#x000A;    &#x000A;    MyBean bean = WeldContainer.instance("one").select(MyBean.class).get();&#x000A;    System.out.println(bean.computeResult());&#x000A;    &#x000A;    WeldContainer.instance("one").shutdown();&#x000A;    WeldContainer.instance("two").shutdown();</code></pre>
-                  </div>
-                  </div>
-                  <div class="paragraph">
-                  <p>Here, two independent <code>WeldContainer</code> instances are initialized.
-                  Each of them is given a unique ID.
-                  The ID can subsequently be used to obtain a <code>WeldContainer</code> reference in a different place of the code.
-                  One possible use-case this enables is for a library or framework (e.g. a testing framework) to use an embedded instance of Weld internally for its own needs (dependency injection, events, extensibility).
-                  This instance would not interfere with the Weld instance used by the application.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Obviously, automatic classpath scanning can still be used as before:</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">try (WeldContainer weld = new Weld().enableDiscovery().initialize()) {&#x000A;        MyBean bean = weld.select(MyBean.class).get();&#x000A;        System.out.println(bean.computeResult());&#x000A;    }</code></pre>
-                  </div>
-                  </div>
-                  <div class="paragraph">
-                  <p><strong>Update:</strong></p>
-                  </div>
-                  <div class="paragraph">
-                  <p>To play with the new API use the following dependency in you Maven project:</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;dependency&gt;&#x000A;        &lt;groupId&gt;org.jboss.weld.se&lt;/groupId&gt;&#x000A;        &lt;artifactId&gt;weld-se-core&lt;/artifactId&gt;&#x000A;        &lt;version&gt;3.0.0.Alpha8&lt;/version&gt;&#x000A;    &lt;/dependency&gt;</code></pre>
-                  </div>
-                  </div>
-                  <div class="paragraph">
-                  <p>Aforementioned classes are from the <code>org.jboss.weld.environment.se</code> package.</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_weld_probe_enhancements">Weld Probe Enhancements</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>Since the last Alpha releases there were several enhancements to Weld Probe.
-                  If you are not familiar with Weld Probe, check this <a href="http://weld.cdi-spec.org/news/2015/02/05/weld-300Alpha4/">introductory blog post first</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>A new feature of Probe is that, when the development mode is enabled, it now embeds a tiny information bar directly into the application&#8217;s HTML output.
-                  That makes it easy to navigate to Probe directly from the application anytime.
-                  Furthermore, if invocation tracking is enabled, the information bar helps navigate directly to the invocation tree related to the request that rendered the output.</p>
-                  </div>
-                  <div class="imageblock">
-                  <div class="content">
-                  <img src="/images/blog/probe-bar.png" alt="Weld Probe information bar embedded in application&#8217;s HTML output">
-                  </div>
-                  </div>
-                  <div class="paragraph">
-                  <p><br></p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Additionally, the following Probe improvements were implemented:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>tracked invocations are now grouped into a invocation tree instead of being tracked in isolation</p>
-                  </li>
-                  <li>
-                  <p>a special type of edges is now used in the overview graph to represent a "declared by" relation (when a bean declares a producer method or field)</p>
-                  </li>
-                  <li>
-                  <p>Instance&lt;?&gt; injection points are now treated specially - a resolved bean is show as injection point&#8217;s dependency</p>
-                  </li>
-                  </ul>
-                  </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=12326881">Release notes</a> &#93;
-                  &#91; <a href="https://sourceforge.net/projects/jboss/files/Weld/3.0.0.Alpha8">Distribution</a> &#93;
-                  &#91; Patch for Wildfly
-                  (<a href="http://sourceforge.net/projects/jboss/files/Weld/3.0.0.Alpha8/wildfly-8.2.0.Final-weld-3.0.0.Alpha8-patch.zip/download">8.2</a>,
-                  <a href="http://sourceforge.net/projects/jboss/files/Weld/3.0.0.Alpha8/wildfly-9.0.0.Beta2-weld-3.0.0.Alpha8-patch.zip/download">9 Beta</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/19.html" class="page-link">19</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 f3a00605..5ffe1455 100644
--- a/news/page/17.html
+++ b/news/page/17.html
@@ -141,6 +141,160 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2015/04/21/weld-300Alpha8/">Weld 3.0.0.Alpha8</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2015-4-21
+                  &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.Alpha8 has been released.
+                  The main change is the enhanced API for using Weld in Java SE environment. In addition, this release comes with several weld-probe improvements.</p>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_enhanced_api_for_weld_se">Enhanced API for Weld SE</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>Weld has provided <a href="http://docs.jboss.org/weld/reference/latest-2.2/en-US/html/environments.html#_java_se">support for the Java SE environment</a> for a long time with the weld-se module.
+                  The API provides an easy way for an application to initialize Weld and use it in a standalone mode.
+                  On initialization Weld SE scans the classpath for bean archives with the <code>beans.xml</code> file, similarly to how it&#8217;s done in the Java EE environment.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>In this release we are extending the API further.
+                  This is partially inspired by the current discussion in the CDI expert group where a standardized CDI API for Java SE is being proposed as part of <a href="https://issues.jboss.org/browse/CDI-26">CDI-26</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>The following code snippet shows the new API in action:</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">Weld builder = new Weld()&#x000A;        .disableDiscovery()&#x000A;        .packages(Main.class, Utils.class)&#x000A;        .interceptors(TransactionalInterceptor.class)&#x000A;        .property("org.jboss.weld.construction.relaxed", true);&#x000A;    &#x000A;    try (WeldContainer weld = builder.initialize()) {&#x000A;        MyBean bean = weld.select(MyBean.class).get();&#x000A;        System.out.println(bean.computeResult());&#x000A;    }</code></pre>
+                  </div>
+                  </div>
+                  <div class="paragraph">
+                  <p>There are several new things to notice:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>the <code>Weld</code> class is used as a builder to configure Weld before it is initialized</p>
+                  </li>
+                  <li>
+                  <p>automatic scanning can be disabled</p>
+                  </li>
+                  <li>
+                  <p>instead of scanning, classes or packages can be selected explicitly. All classes in those packages will be managed by Weld</p>
+                  </li>
+                  <li>
+                  <p>interceptors, decorators, extensions and <a href="http://docs.jboss.org/weld/reference/3.0.0.Alpha8/en-US/html/configure.html#_weld_configuration">Weld-specific configuration options</a> can be specified using the builder</p>
+                  </li>
+                  <li>
+                  <p><code>WeldContainer</code> now implements <code>AutoCloseable</code> and can therefore be used in a <code>try-with-resources</code> block. At any time that execution gets outside of the code block, the Weld instance is shut down and all managed instances are safely destroyed.</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>It is also possible to start multiple independent Weld instances:</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">new Weld().disableDiscovery().containerId("one").beanClasses(MyBean.class).initialize();&#x000A;    new Weld().disableDiscovery().containerId("two").beanClasses(OtherBean.class).initialize();&#x000A;    &#x000A;    MyBean bean = WeldContainer.instance("one").select(MyBean.class).get();&#x000A;    System.out.println(bean.computeResult());&#x000A;    &#x000A;    WeldContainer.instance("one").shutdown();&#x000A;    WeldContainer.instance("two").shutdown();</code></pre>
+                  </div>
+                  </div>
+                  <div class="paragraph">
+                  <p>Here, two independent <code>WeldContainer</code> instances are initialized.
+                  Each of them is given a unique ID.
+                  The ID can subsequently be used to obtain a <code>WeldContainer</code> reference in a different place of the code.
+                  One possible use-case this enables is for a library or framework (e.g. a testing framework) to use an embedded instance of Weld internally for its own needs (dependency injection, events, extensibility).
+                  This instance would not interfere with the Weld instance used by the application.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Obviously, automatic classpath scanning can still be used as before:</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">try (WeldContainer weld = new Weld().enableDiscovery().initialize()) {&#x000A;        MyBean bean = weld.select(MyBean.class).get();&#x000A;        System.out.println(bean.computeResult());&#x000A;    }</code></pre>
+                  </div>
+                  </div>
+                  <div class="paragraph">
+                  <p><strong>Update:</strong></p>
+                  </div>
+                  <div class="paragraph">
+                  <p>To play with the new API use the following dependency in you Maven project:</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;dependency&gt;&#x000A;        &lt;groupId&gt;org.jboss.weld.se&lt;/groupId&gt;&#x000A;        &lt;artifactId&gt;weld-se-core&lt;/artifactId&gt;&#x000A;        &lt;version&gt;3.0.0.Alpha8&lt;/version&gt;&#x000A;    &lt;/dependency&gt;</code></pre>
+                  </div>
+                  </div>
+                  <div class="paragraph">
+                  <p>Aforementioned classes are from the <code>org.jboss.weld.environment.se</code> package.</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_weld_probe_enhancements">Weld Probe Enhancements</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>Since the last Alpha releases there were several enhancements to Weld Probe.
+                  If you are not familiar with Weld Probe, check this <a href="http://weld.cdi-spec.org/news/2015/02/05/weld-300Alpha4/">introductory blog post first</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>A new feature of Probe is that, when the development mode is enabled, it now embeds a tiny information bar directly into the application&#8217;s HTML output.
+                  That makes it easy to navigate to Probe directly from the application anytime.
+                  Furthermore, if invocation tracking is enabled, the information bar helps navigate directly to the invocation tree related to the request that rendered the output.</p>
+                  </div>
+                  <div class="imageblock">
+                  <div class="content">
+                  <img src="/images/blog/probe-bar.png" alt="Weld Probe information bar embedded in application&#8217;s HTML output">
+                  </div>
+                  </div>
+                  <div class="paragraph">
+                  <p><br></p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Additionally, the following Probe improvements were implemented:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>tracked invocations are now grouped into a invocation tree instead of being tracked in isolation</p>
+                  </li>
+                  <li>
+                  <p>a special type of edges is now used in the overview graph to represent a "declared by" relation (when a bean declares a producer method or field)</p>
+                  </li>
+                  <li>
+                  <p>Instance&lt;?&gt; injection points are now treated specially - a resolved bean is show as injection point&#8217;s dependency</p>
+                  </li>
+                  </ul>
+                  </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=12326881">Release notes</a> &#93;
+                  &#91; <a href="https://sourceforge.net/projects/jboss/files/Weld/3.0.0.Alpha8">Distribution</a> &#93;
+                  &#91; Patch for Wildfly
+                  (<a href="http://sourceforge.net/projects/jboss/files/Weld/3.0.0.Alpha8/wildfly-8.2.0.Final-weld-3.0.0.Alpha8-patch.zip/download">8.2</a>,
+                  <a href="http://sourceforge.net/projects/jboss/files/Weld/3.0.0.Alpha8/wildfly-9.0.0.Beta2-weld-3.0.0.Alpha8-patch.zip/download">9 Beta</a>)
+                  &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2015/02/25/weld-300Alpha5/">Weld 3.0.0.Alpha5</a>
@@ -894,62 +1048,6 @@ <h2 id="_give_it_a_try">Give it a try!</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2014/09/18/weld-next/">Weld.Next</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2014-9-18
-                  &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.5.Final. The fifth mostly bug-fixing release in the series addresses <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12325389">23 issues</a>.
-                  In addition, the Servlet module got an update and among other things now supports:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>all three bean discovery modes (e.g. only explicitly annotated classes will be loaded as CDI beans)</p>
-                  </li>
-                  <li>
-                  <p>bean archive isolation</p>
-                  </li>
-                  <li>
-                  <p>using Jandex for faster deployment discovery</p>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>See the <a href="http://docs.jboss.org/weld/reference/2.2.5.Final/en-US/html/_application_servers_and_environments_supported_by_weld.html#_servlet_containers_such_as_tomcat_or_jetty">reference documentation </a>
-                  for details.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Talking about documentation we are grateful to <a href="http://www.next-presso.com/author/antoine/">Antoine Sabot-Durand</a> for migrating our reference documentation to <a href="http://www.methods.co.nz/asciidoc/">AsciiDoc</a>.
-                  We also thank our community contributors <strong>Antonin Stefanutti</strong> and <strong>Stefan Grossmann</strong> who contributed with pull requests.</p>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_weld_3_0">Weld 3.0</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>In the coming months, our focus will be shifting towards <strong>Weld 3.0</strong> - the future reference implementation of <a href="http://cdi-spec.org/">CDI 2.0</a>.
-                  Initially, we plan on releasing Alpha releases every two weeks starting in early October.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>The Alpha releases are likely to break compatibility from time to time and will often contain bleeding edge or prototype code.
-                  The goals is however to give the CDI community a chance to test drive the proposed changes in the CDI specification as soon as possible and give quick feedback to the CDI expert group.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Weld 3.0 will also be a good opportunity to get involved in the development of this open-source project. <strong>Interested?</strong> See our <a href="http://weld.cdi-spec.org/community/">community web page</a> for more details.</p>
-                  </div>
-                  </div>
-                  </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/19.html" class="page-link">19</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 55be1121..1c941872 100644
--- a/news/page/18.html
+++ b/news/page/18.html
@@ -141,6 +141,62 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2014/09/18/weld-next/">Weld.Next</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2014-9-18
+                  &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.5.Final. The fifth mostly bug-fixing release in the series addresses <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12325389">23 issues</a>.
+                  In addition, the Servlet module got an update and among other things now supports:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>all three bean discovery modes (e.g. only explicitly annotated classes will be loaded as CDI beans)</p>
+                  </li>
+                  <li>
+                  <p>bean archive isolation</p>
+                  </li>
+                  <li>
+                  <p>using Jandex for faster deployment discovery</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>See the <a href="http://docs.jboss.org/weld/reference/2.2.5.Final/en-US/html/_application_servers_and_environments_supported_by_weld.html#_servlet_containers_such_as_tomcat_or_jetty">reference documentation </a>
+                  for details.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Talking about documentation we are grateful to <a href="http://www.next-presso.com/author/antoine/">Antoine Sabot-Durand</a> for migrating our reference documentation to <a href="http://www.methods.co.nz/asciidoc/">AsciiDoc</a>.
+                  We also thank our community contributors <strong>Antonin Stefanutti</strong> and <strong>Stefan Grossmann</strong> who contributed with pull requests.</p>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_weld_3_0">Weld 3.0</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>In the coming months, our focus will be shifting towards <strong>Weld 3.0</strong> - the future reference implementation of <a href="http://cdi-spec.org/">CDI 2.0</a>.
+                  Initially, we plan on releasing Alpha releases every two weeks starting in early October.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>The Alpha releases are likely to break compatibility from time to time and will often contain bleeding edge or prototype code.
+                  The goals is however to give the CDI community a chance to test drive the proposed changes in the CDI specification as soon as possible and give quick feedback to the CDI expert group.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Weld 3.0 will also be a good opportunity to get involved in the development of this open-source project. <strong>Interested?</strong> See our <a href="http://weld.cdi-spec.org/community/">community web page</a> for more details.</p>
+                  </div>
+                  </div>
+                  </div>
+                </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>
@@ -444,118 +500,6 @@ <h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2013/10/22/weld-210-final/">Weld 2.1.0.Final</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2013-10-22
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Jozef Hartinger
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>I am pleased to announce that Weld 2.1.0.Final has just been released. Weld is the reference implementation of <a href="http://cdi-spec.org">Contexts and Dependency Injection for Java EE (CDI)</a>.
-                  Here is the highlight of what’s new in Weld 2.1.0:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>OSGi support with Pax CDI</p>
-                  </li>
-                  <li>
-                  <p>Improved runtime performance and memory consumption</p>
-                  </li>
-                  <li>
-                  <p>Better integration with various Servlet dispatch types</p>
-                  </li>
-                  <li>
-                  <p>SLF4j was replaced with <a href="https://github.com/jboss-logging">jboss-logging</a></p>
-                  </li>
-                  <li>
-                  <p>30 fixed bugs</p>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="weld-osgi">The future of Weld-OSGi</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p><a href="http://www.slideshare.net/TrevorReznik/weldosgi-injecting-easiness-in-osgi">Weld-osgi</a> is a framework that allows the CDI programming model to be used in the OSGi environment.
-                  The framework was developed entirely by the Weld community and became a part of Weld since version 1.2.0</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>The framework provides three main features:</p>
-                  </div>
-                  <div class="olist arabic">
-                  <ol class="arabic">
-                  <li>
-                  <p>The CDI programming model can be used within OSGi bundles.</p>
-                  </li>
-                  <li>
-                  <p>The OSGi service layer and utility facilities are accessible through CDI injection</p>
-                  </li>
-                  <li>
-                  <p>The CDI event bus can be used for both inter-bundle communication and delivering OSGi events.</p>
-                  </li>
-                  </ol>
-                  </div>
-                  <div class="paragraph">
-                  <p>The weld-osgi framework served as an inspiration for a standardization effort, known as <a href="http://www.osgi.org/download/osgi-early-draft-2013-03.pdf">RFC-193</a> (formerly RFP-146).
-                  The proposal is now part of the <a href="http://www.osgi.org/download/osgi-early-draft-2013-03.pdf">OSGi early draft</a></p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Due to the tight schedule of CDI 1.1, weld-osgi did never make it to Weld 2.0 and was therefore left behind, stuck in the gradually abandoned 1.2 branch.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>In the meantime, work on the reference implementation of RFC-193 begun. The reference implementation is known as <a href="https://ops4j1.jira.com/wiki/display/PAXCDI/Documentation">Pax CDI</a> and it is an open-source project hosted on <a href="https://github.com/ops4j/org.ops4j.pax.cdi">GitHub</a>.
-                  Pax CDI aims to be portable across OSGi implementations as well as CDI implementations.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>We always wanted to bring OSGi support back in Weld 2.1. However, we decided not to revive the weld-osgi framework nor align it to the new RFC-193 specification. Therefore, weld-osgi will not be merged into Weld 2.x code base.
-                  Instead, we decided to shift our focus towards Pax CDI and make sure it works well with Weld.
-                  This was done and Weld 2.1.0 is now one of the CDI runtimes supported by Pax CDI. You can play with the current <a href="https://ops4j1.jira.com/wiki/display/PAXCDI/Download">Pax CDI SNAPSHOT</a>
-                  or wait for the upcoming <a href="https://ops4j1.jira.com/browse/PAXCDI/fixforversion/11996">0.5 release</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>EDIT 2013-10-30: Pax CDI 0.5.0 was released. See the <a href="http://team.ops4j.org/wiki/display/PAXCDI/2013/10/27/Pax+CDI+0.5.0+Released">release announcement</a> for more details.</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_performance">Performance</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>The CDI specification requires the request, conversation and application contexts to be active during every HTTP request.
-                  Obviously, the CDI contexts are not necessary for every HTTP request. Fetching a static resource is an example of one such request.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>In Weld 2.1.0 we optimized the component that handles context activation/deactivation and cut down the overhead.
-                  In addition, it is now possible to completely suppress CDI context activation on certain types of HTTP requests should this minimized overhead still be undesired.
-                  See <a href="https://community.jboss.org/people/mkouba/blog/2013/09/18/weld&#8212;&#8203;skip-cdi-context-activation-for-some-http-requests">Martin’s blog post</a> or
-                  <a href="http://docs.jboss.org/weld/reference/latest/en-US/html/configure.html#d0e6194">the reference documentation</a> for more details.</p>
-                  </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, Marko Lukša, Stuart Douglas, Marek Schmidt, Ron Šmeral, Tomáš Remeš, Max Pimm, Jesse McConnell, Harald Wellmann and Dirk Strauss.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>&#91; <a href="https://sourceforge.net/projects/jboss/files/Weld/2.1.0.Final">Distribution</a> &#93;
-                  &#91; <a href="https://issues.jboss.org/issues/?jql=project%20%3D%20WELD%20AND%20fixVersion%20in%20%28%222.1.0.Final%22%2C%20%222.1.0.Alpha1%22%2C%20%222.1.0.Beta1%22%2C%20%222.1.0.Beta2%22%2C%20%222.1.0.CR1%22%29%20ORDER%20BY%20updated%20ASC">Release notes</a> &#93;
-                  &#91; <a href="http://docs.jboss.org/weld/reference/2.1.0.Final/en-US/html/">Documentation</a> &#93;
-                  &#91; <a href="http://docs.jboss.org/cdi/api/1.1/">CDI 1.1 Javadoc</a> &#93;</p>
-                  </div>
-                  </div>
-                  </div>
-                </div>
-                <hr>
-              </div>
               <div class="pagination-links"><a href="/news/page/17.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/17.html" class="page-link">17</a> <span class="current-page">18</span> <a href="/news/page/19.html" class="page-link">19</a> <a href="/news/page/19.html" class="next-link">Next</a> </div>
               <hr>
               <div>
diff --git a/news/page/19.html b/news/page/19.html
index 139a2648..895ee141 100644
--- a/news/page/19.html
+++ b/news/page/19.html
@@ -141,6 +141,118 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2013/10/22/weld-210-final/">Weld 2.1.0.Final</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2013-10-22
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Jozef Hartinger
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>I am pleased to announce that Weld 2.1.0.Final has just been released. Weld is the reference implementation of <a href="http://cdi-spec.org">Contexts and Dependency Injection for Java EE (CDI)</a>.
+                  Here is the highlight of what’s new in Weld 2.1.0:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>OSGi support with Pax CDI</p>
+                  </li>
+                  <li>
+                  <p>Improved runtime performance and memory consumption</p>
+                  </li>
+                  <li>
+                  <p>Better integration with various Servlet dispatch types</p>
+                  </li>
+                  <li>
+                  <p>SLF4j was replaced with <a href="https://github.com/jboss-logging">jboss-logging</a></p>
+                  </li>
+                  <li>
+                  <p>30 fixed bugs</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="weld-osgi">The future of Weld-OSGi</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p><a href="http://www.slideshare.net/TrevorReznik/weldosgi-injecting-easiness-in-osgi">Weld-osgi</a> is a framework that allows the CDI programming model to be used in the OSGi environment.
+                  The framework was developed entirely by the Weld community and became a part of Weld since version 1.2.0</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>The framework provides three main features:</p>
+                  </div>
+                  <div class="olist arabic">
+                  <ol class="arabic">
+                  <li>
+                  <p>The CDI programming model can be used within OSGi bundles.</p>
+                  </li>
+                  <li>
+                  <p>The OSGi service layer and utility facilities are accessible through CDI injection</p>
+                  </li>
+                  <li>
+                  <p>The CDI event bus can be used for both inter-bundle communication and delivering OSGi events.</p>
+                  </li>
+                  </ol>
+                  </div>
+                  <div class="paragraph">
+                  <p>The weld-osgi framework served as an inspiration for a standardization effort, known as <a href="http://www.osgi.org/download/osgi-early-draft-2013-03.pdf">RFC-193</a> (formerly RFP-146).
+                  The proposal is now part of the <a href="http://www.osgi.org/download/osgi-early-draft-2013-03.pdf">OSGi early draft</a></p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Due to the tight schedule of CDI 1.1, weld-osgi did never make it to Weld 2.0 and was therefore left behind, stuck in the gradually abandoned 1.2 branch.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>In the meantime, work on the reference implementation of RFC-193 begun. The reference implementation is known as <a href="https://ops4j1.jira.com/wiki/display/PAXCDI/Documentation">Pax CDI</a> and it is an open-source project hosted on <a href="https://github.com/ops4j/org.ops4j.pax.cdi">GitHub</a>.
+                  Pax CDI aims to be portable across OSGi implementations as well as CDI implementations.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>We always wanted to bring OSGi support back in Weld 2.1. However, we decided not to revive the weld-osgi framework nor align it to the new RFC-193 specification. Therefore, weld-osgi will not be merged into Weld 2.x code base.
+                  Instead, we decided to shift our focus towards Pax CDI and make sure it works well with Weld.
+                  This was done and Weld 2.1.0 is now one of the CDI runtimes supported by Pax CDI. You can play with the current <a href="https://ops4j1.jira.com/wiki/display/PAXCDI/Download">Pax CDI SNAPSHOT</a>
+                  or wait for the upcoming <a href="https://ops4j1.jira.com/browse/PAXCDI/fixforversion/11996">0.5 release</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>EDIT 2013-10-30: Pax CDI 0.5.0 was released. See the <a href="http://team.ops4j.org/wiki/display/PAXCDI/2013/10/27/Pax+CDI+0.5.0+Released">release announcement</a> for more details.</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_performance">Performance</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>The CDI specification requires the request, conversation and application contexts to be active during every HTTP request.
+                  Obviously, the CDI contexts are not necessary for every HTTP request. Fetching a static resource is an example of one such request.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>In Weld 2.1.0 we optimized the component that handles context activation/deactivation and cut down the overhead.
+                  In addition, it is now possible to completely suppress CDI context activation on certain types of HTTP requests should this minimized overhead still be undesired.
+                  See <a href="https://community.jboss.org/people/mkouba/blog/2013/09/18/weld&#8212;&#8203;skip-cdi-context-activation-for-some-http-requests">Martin’s blog post</a> or
+                  <a href="http://docs.jboss.org/weld/reference/latest/en-US/html/configure.html#d0e6194">the reference documentation</a> for more details.</p>
+                  </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, Marko Lukša, Stuart Douglas, Marek Schmidt, Ron Šmeral, Tomáš Remeš, Max Pimm, Jesse McConnell, Harald Wellmann and Dirk Strauss.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="https://sourceforge.net/projects/jboss/files/Weld/2.1.0.Final">Distribution</a> &#93;
+                  &#91; <a href="https://issues.jboss.org/issues/?jql=project%20%3D%20WELD%20AND%20fixVersion%20in%20%28%222.1.0.Final%22%2C%20%222.1.0.Alpha1%22%2C%20%222.1.0.Beta1%22%2C%20%222.1.0.Beta2%22%2C%20%222.1.0.CR1%22%29%20ORDER%20BY%20updated%20ASC">Release notes</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/2.1.0.Final/en-US/html/">Documentation</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/cdi/api/1.1/">CDI 1.1 Javadoc</a> &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2013/09/20/weld-210beta2-tip/">Weld 2.1.0.Beta2 tip</a>
diff --git a/news/page/2.html b/news/page/2.html
index 8ce78356..f8a80e50 100644
--- a/news/page/2.html
+++ b/news/page/2.html
@@ -141,6 +141,106 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2024/02/26/weld-600Beta1/">Weld 6.0.0.Beta1</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2024-2-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 Core 6.0.0.Beta1 along with Weld API 6.0.Beta2 are the latest two artifacts you&#8217;re going to need if you&#8217;re looking for an implementation of the CDI API 4.1.0.Beta1.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Changes based on CDI specification since last 6.x version:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>The method invoker API in CDI has been simplified and the transformer functionality removed from the specification (<a href="https://issues.redhat.com/browse/WELD-2765">WELD-2765</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Weld API introduced <code>WeldInvokerBuilder</code> which retains all of the transformers/wrappers that were originally present</p>
+                  </li>
+                  <li>
+                  <p>We also added some more validation and other tweaks but the whole functionality is still being worked on as part of the follow up release</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Support declaring <code>@Priority</code> on producers (<a href="https://issues.redhat.com/browse/WELD-2768">WELD-2768</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>This is also one of the features added by CDI API 4.1 and Beta1 of Weld supports it</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p><code>BeanManager</code> implementations in Weld now correctly extend <code>ELAwareBeanManager</code> from newly introduced CDI API module (<a href="https://issues.redhat.com/browse/WELD-2769">WELD-2769</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>There is no functionality change, this is just a step forward towards removing EL dependency from core CDI</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Implemented programmatic access to assignability rules on <code>BeanManager</code> (<a href="https://issues.redhat.com/browse/WELD-2774">WELD-2774</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p><code>BeanContainer</code>/<code>BeanManager</code> now allow users to invoke <code>#isMatchingBean()</code> and <code>#isMatchingEvent()</code> methods</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>Other changes and bugfixes:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Correct inheritance of producer fields if there is an extension present (<a href="https://issues.redhat.com/browse/WELD-2773">WELD-2773</a>)</p>
+                  </li>
+                  <li>
+                  <p>Make sure <code>@Default</code> qualifier is added to events fired via <code>BeanManager#getEvent()</code> where appropriate (<a href="https://issues.redhat.com/browse/WELD-2775">WELD-2775</a>)</p>
+                  </li>
+                  <li>
+                  <p>Weld SE - manually registered portable extensions now reside in synthetic bean archive instead of their own (<a href="https://issues.redhat.com/browse/WELD-2776">WELD-2776</a>)</p>
+                  </li>
+                  <li>
+                  <p>Updated CI setup to make sure bulk of our tests is running against JDK 21 (<a href="https://issues.redhat.com/browse/WELD-2777">WELD-2777</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.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=12415474" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2023/10/26/weld-600Alpha1/">Weld 6.0.0.Alpha1</a>
@@ -402,69 +502,6 @@ <h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2023/06/12/weld-511Final/">Weld 5.1.1.Final</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2023-6-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>
-                  Matej Novotny
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>It&#8217;s time for some minor updates and fixes, Weld 5.1.1.Final is now available!</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Main highlights are as follows:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Fix bean type assignability for beans with recursive generic types (<a href="https://issues.redhat.com/browse/WELD-2738">WELD-2738</a>)</p>
-                  </li>
-                  <li>
-                  <p>Failing validation for pasivation capability, Weld should throw <code>DeploymentException</code> instead of <code>DefinitionException</code> (<a href="https://issues.redhat.com/browse/WELD-2741">WELD-2741</a>)</p>
-                  </li>
-                  <li>
-                  <p>Avoid firing <code>ProcessInjectionTarget</code> multiple times if a specialized bean was vetoed (<a href="https://issues.redhat.com/browse/WELD-2742">WELD-2742</a>)</p>
-                  </li>
-                  <li>
-                  <p><code>BeanManager#getReference</code> should not create a child <code>CreationalContext</code> instance (<a href="https://issues.redhat.com/browse/WELD-2743">WELD-2743</a>)</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>This should only affect scenarios in which beans were 'manually' created and destroyed in which case the destruction could end up incomplete</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Fix how Weld defines proxies to avoid problems in JDK 17+ along with the newest JBoss Class File Writer (1.3.0.Final) (<a href="https://issues.redhat.com/browse/WELD-2744">WELD-2744</a>)</p>
-                  </li>
-                  <li>
-                  <p>Correction to documentation which incorrectly suggested <code>@ManagedBean</code> was a bean defining annotation (<a href="https://issues.redhat.com/browse/WELD-2737">WELD-2737</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>As always, if you find further issues with Weld 5, 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/5.1.1.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=12397581" 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/18.html" class="page-link">18</a> <a href="/news/page/19.html" class="page-link">19</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 5aa0f314..23dca555 100644
--- a/news/page/3.html
+++ b/news/page/3.html
@@ -141,6 +141,69 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2023/06/12/weld-511Final/">Weld 5.1.1.Final</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2023-6-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>
+                  Matej Novotny
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>It&#8217;s time for some minor updates and fixes, Weld 5.1.1.Final is now available!</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Main highlights are as follows:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Fix bean type assignability for beans with recursive generic types (<a href="https://issues.redhat.com/browse/WELD-2738">WELD-2738</a>)</p>
+                  </li>
+                  <li>
+                  <p>Failing validation for pasivation capability, Weld should throw <code>DeploymentException</code> instead of <code>DefinitionException</code> (<a href="https://issues.redhat.com/browse/WELD-2741">WELD-2741</a>)</p>
+                  </li>
+                  <li>
+                  <p>Avoid firing <code>ProcessInjectionTarget</code> multiple times if a specialized bean was vetoed (<a href="https://issues.redhat.com/browse/WELD-2742">WELD-2742</a>)</p>
+                  </li>
+                  <li>
+                  <p><code>BeanManager#getReference</code> should not create a child <code>CreationalContext</code> instance (<a href="https://issues.redhat.com/browse/WELD-2743">WELD-2743</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>This should only affect scenarios in which beans were 'manually' created and destroyed in which case the destruction could end up incomplete</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Fix how Weld defines proxies to avoid problems in JDK 17+ along with the newest JBoss Class File Writer (1.3.0.Final) (<a href="https://issues.redhat.com/browse/WELD-2744">WELD-2744</a>)</p>
+                  </li>
+                  <li>
+                  <p>Correction to documentation which incorrectly suggested <code>@ManagedBean</code> was a bean defining annotation (<a href="https://issues.redhat.com/browse/WELD-2737">WELD-2737</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>As always, if you find further issues with Weld 5, 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/5.1.1.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=12397581" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2022/10/03/weld-510Final/">Weld 5.1.0.Final</a>
@@ -360,83 +423,6 @@ <h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2022/04/29/weld-500Final/">Weld 5.0.0.Final</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2022-4-29
-                  &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>CDI 4 has passed its Final ballot and is now available in Maven Central.
-                  Some of you may have played with it already, but where is the fun in it, if you don&#8217;t have a Final implementation, right?
-                  Have no fear, Weld 5 Final is here!</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>As usual, there is Weld 5.0.Final API as well as Weld 5.0.0.Final core impl.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>It is very much the same as CR2, with some additional tweaks and fixes that came to light when working on integrations within EE servers.
-                  That&#8217;s right, EE servers are already making progress towards integrating CDI 4 and Weld 5.
-                  Folks over at Open Liberty did their Weld 5 homework about a week ago and WildFly now has a pending <a href="https://github.com/wildfly/wildfly/pull/15474">pull request</a> that adds missing bits for CDI 4 support.
-                  It might still be a while before there is a Beta WildFly release, but if you have the nerves, you can build the SNAPSHOT at least.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Back on the topic of changes, here is a list of fixes from CR2 to Final:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Self-interception can now be used on protected methods, params and return types (<a href="https://issues.jboss.org/browse/WELD-2712" target="_blank" rel="noopener">WELD-2712</a>)</p>
-                  </li>
-                  <li>
-                  <p>Rewieved Weld examples and made sure they run for EE 10 (<a href="https://issues.jboss.org/browse/WELD-2708" target="_blank" rel="noopener">WELD-2708</a>)</p>
-                  </li>
-                  <li>
-                  <p>Review Weld 5 documentation (<a href="https://issues.jboss.org/browse/WELD-2696" target="_blank" rel="noopener">WELD-2696</a>)</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Note that the servlet part is still outdated and being worked on as we need to see if there is workable EE 10 variant, see <a href="https://issues.jboss.org/browse/WELD-2716" target="_blank" rel="noopener">WELD-2716</a></p>
-                  </li>
-                  <li>
-                  <p>We expect that this will be sorted by the time we ship 5.0.1.Final</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Firing of the <code>Startup</code> event for web modules can happen too early (<a href="https://issues.jboss.org/browse/WELD-2717" target="_blank" rel="noopener">WELD-2717</a>)</p>
-                  </li>
-                  <li>
-                  <p>Synthetic beans coming from Build Compatible extension should be registered under their respective extensions (<a href="https://issues.jboss.org/browse/WELD-2718" target="_blank" rel="noopener">WELD-2718</a>)</p>
-                  </li>
-                  <li>
-                  <p>Exceptions thrown during execution of Build Compatible extensions now correctly preserve their cause (<a href="https://issues.jboss.org/browse/WELD-2710" target="_blank" rel="noopener">WELD-2710</a>)</p>
-                  </li>
-                  <li>
-                  <p>Some of our SE testing was being skipped ever since Groovy dependency update, this is now corrected (<a href="https://issues.jboss.org/browse/WELD-2714" target="_blank" rel="noopener">WELD-2714</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.0.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=12383754" target="_blank" rel="noopener">Release notes</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/18.html" class="page-link">18</a> <a href="/news/page/19.html" class="page-link">19</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 5317505d..ce93e699 100644
--- a/news/page/4.html
+++ b/news/page/4.html
@@ -141,6 +141,83 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2022/04/29/weld-500Final/">Weld 5.0.0.Final</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2022-4-29
+                  &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>CDI 4 has passed its Final ballot and is now available in Maven Central.
+                  Some of you may have played with it already, but where is the fun in it, if you don&#8217;t have a Final implementation, right?
+                  Have no fear, Weld 5 Final is here!</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>As usual, there is Weld 5.0.Final API as well as Weld 5.0.0.Final core impl.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>It is very much the same as CR2, with some additional tweaks and fixes that came to light when working on integrations within EE servers.
+                  That&#8217;s right, EE servers are already making progress towards integrating CDI 4 and Weld 5.
+                  Folks over at Open Liberty did their Weld 5 homework about a week ago and WildFly now has a pending <a href="https://github.com/wildfly/wildfly/pull/15474">pull request</a> that adds missing bits for CDI 4 support.
+                  It might still be a while before there is a Beta WildFly release, but if you have the nerves, you can build the SNAPSHOT at least.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Back on the topic of changes, here is a list of fixes from CR2 to Final:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Self-interception can now be used on protected methods, params and return types (<a href="https://issues.jboss.org/browse/WELD-2712" target="_blank" rel="noopener">WELD-2712</a>)</p>
+                  </li>
+                  <li>
+                  <p>Rewieved Weld examples and made sure they run for EE 10 (<a href="https://issues.jboss.org/browse/WELD-2708" target="_blank" rel="noopener">WELD-2708</a>)</p>
+                  </li>
+                  <li>
+                  <p>Review Weld 5 documentation (<a href="https://issues.jboss.org/browse/WELD-2696" target="_blank" rel="noopener">WELD-2696</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Note that the servlet part is still outdated and being worked on as we need to see if there is workable EE 10 variant, see <a href="https://issues.jboss.org/browse/WELD-2716" target="_blank" rel="noopener">WELD-2716</a></p>
+                  </li>
+                  <li>
+                  <p>We expect that this will be sorted by the time we ship 5.0.1.Final</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Firing of the <code>Startup</code> event for web modules can happen too early (<a href="https://issues.jboss.org/browse/WELD-2717" target="_blank" rel="noopener">WELD-2717</a>)</p>
+                  </li>
+                  <li>
+                  <p>Synthetic beans coming from Build Compatible extension should be registered under their respective extensions (<a href="https://issues.jboss.org/browse/WELD-2718" target="_blank" rel="noopener">WELD-2718</a>)</p>
+                  </li>
+                  <li>
+                  <p>Exceptions thrown during execution of Build Compatible extensions now correctly preserve their cause (<a href="https://issues.jboss.org/browse/WELD-2710" target="_blank" rel="noopener">WELD-2710</a>)</p>
+                  </li>
+                  <li>
+                  <p>Some of our SE testing was being skipped ever since Groovy dependency update, this is now corrected (<a href="https://issues.jboss.org/browse/WELD-2714" target="_blank" rel="noopener">WELD-2714</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.0.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=12383754" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2022/03/23/weld-500CR2/">Weld 5.0.0.CR2</a>
@@ -606,71 +683,6 @@ <h2 id="_more_in_depth_overview_of_resolved_issues_in_weld_5">More in-depth over
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2021/07/14/weld-402Final-318Final/">Weld 4.0.2.Final and 3.1.8.Final</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2021-7-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>New maintenance releases for Weld 3 and 4 have been rolled out.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>There is only a handful of changes this time so let&#8217;s skid across them:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Prevent <code>WeldInvocationContext</code> from ever returning <code>null</code> when queried for interceptor bindings (<a href="https://issues.jboss.org/browse/WELD-2675" target="_blank" rel="noopener">WELD-2675</a>)</p>
-                  </li>
-                  <li>
-                  <p>Fix an NPE if there is an EJB bean with default package present (<a href="https://issues.jboss.org/browse/WELD-2674" target="_blank" rel="noopener">WELD-2674</a>)</p>
-                  </li>
-                  <li>
-                  <p>Weld wasn&#8217;t working on JDK 17 due to <code>jboss-classfilewriter</code> issue; this should no longer be the case (<a href="https://issues.jboss.org/browse/WELD-2671" target="_blank" rel="noopener">WELD-2671</a>)</p>
-                  </li>
-                  <li>
-                  <p>Correction to proxy name creation for producers based on interfaces - Weld should now use package and class of the most specific interface (<a href="https://issues.jboss.org/browse/WELD-2675" target="_blank" rel="noopener">WELD-2675</a>)</p>
-                  </li>
-                  <li>
-                  <p>Weld now provides correct metadata (via <code>@Decorated</code>) in cases where more than one decorator is applied to a single bean (<a href="https://issues.jboss.org/browse/WELD-2673" target="_blank" rel="noopener">WELD-2673</a>)</p>
-                  </li>
-                  <li>
-                  <p>We have decided to no longer provide WildFly patches for each release (<a href="https://issues.jboss.org/browse/WELD-2660" target="_blank" rel="noopener">WELD-2660</a>)</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>After discussion with WildFly team, we figured the current way is not going to work for anything beyond Weld 3</p>
-                  </li>
-                  <li>
-                  <p>And we aren&#8217;t even certain this feature is requested and/or used anymore; if you feel otherwise, please create a JIRA to let us know</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>&#91; <a href="/download/">Download</a> &#93;
-                  &#91; <a href="http://docs.jboss.org/weld/reference/4.0.2.Final/en-US/html_single/" target="_blank" rel="noopener">Documentation Weld 4.0.2.Final</a> &#93;
-                  &#91; <a href="http://docs.jboss.org/weld/reference/3.1.8.Final/en-US/html_single/" target="_blank" rel="noopener">Documentation Weld 3.1.8.Final</a> &#93;
-                  &#91; <a href="https://issues.redhat.com/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12356277" target="_blank" rel="noopener">Release notes for Weld 4.0.2.Final</a> &#93;
-                  &#91; <a href="https://issues.redhat.com/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12356276" target="_blank" rel="noopener">Release notes for Weld 3.1.8.Final</a> &#93;</p>
-                  </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/18.html" class="page-link">18</a> <a href="/news/page/19.html" class="page-link">19</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 13094668..011fbfa3 100644
--- a/news/page/5.html
+++ b/news/page/5.html
@@ -141,6 +141,71 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2021/07/14/weld-402Final-318Final/">Weld 4.0.2.Final and 3.1.8.Final</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2021-7-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>New maintenance releases for Weld 3 and 4 have been rolled out.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>There is only a handful of changes this time so let&#8217;s skid across them:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Prevent <code>WeldInvocationContext</code> from ever returning <code>null</code> when queried for interceptor bindings (<a href="https://issues.jboss.org/browse/WELD-2675" target="_blank" rel="noopener">WELD-2675</a>)</p>
+                  </li>
+                  <li>
+                  <p>Fix an NPE if there is an EJB bean with default package present (<a href="https://issues.jboss.org/browse/WELD-2674" target="_blank" rel="noopener">WELD-2674</a>)</p>
+                  </li>
+                  <li>
+                  <p>Weld wasn&#8217;t working on JDK 17 due to <code>jboss-classfilewriter</code> issue; this should no longer be the case (<a href="https://issues.jboss.org/browse/WELD-2671" target="_blank" rel="noopener">WELD-2671</a>)</p>
+                  </li>
+                  <li>
+                  <p>Correction to proxy name creation for producers based on interfaces - Weld should now use package and class of the most specific interface (<a href="https://issues.jboss.org/browse/WELD-2675" target="_blank" rel="noopener">WELD-2675</a>)</p>
+                  </li>
+                  <li>
+                  <p>Weld now provides correct metadata (via <code>@Decorated</code>) in cases where more than one decorator is applied to a single bean (<a href="https://issues.jboss.org/browse/WELD-2673" target="_blank" rel="noopener">WELD-2673</a>)</p>
+                  </li>
+                  <li>
+                  <p>We have decided to no longer provide WildFly patches for each release (<a href="https://issues.jboss.org/browse/WELD-2660" target="_blank" rel="noopener">WELD-2660</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>After discussion with WildFly team, we figured the current way is not going to work for anything beyond Weld 3</p>
+                  </li>
+                  <li>
+                  <p>And we aren&#8217;t even certain this feature is requested and/or used anymore; if you feel otherwise, please create a JIRA to let us know</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="/download/">Download</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/4.0.2.Final/en-US/html_single/" target="_blank" rel="noopener">Documentation Weld 4.0.2.Final</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/3.1.8.Final/en-US/html_single/" target="_blank" rel="noopener">Documentation Weld 3.1.8.Final</a> &#93;
+                  &#91; <a href="https://issues.redhat.com/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12356277" target="_blank" rel="noopener">Release notes for Weld 4.0.2.Final</a> &#93;
+                  &#91; <a href="https://issues.redhat.com/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12356276" target="_blank" rel="noopener">Release notes for Weld 3.1.8.Final</a> &#93;</p>
+                  </div>
+                </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>
@@ -526,79 +591,6 @@ <h2 id="_wildfly_patch">WildFly Patch</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2020/12/16/weld-400Final/">Weld 4.0.0.Final</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2020-12-16
-                  &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>An early Xmas present for CDI lovers is here - <code>Final</code> release for Weld 4 is now available!
-                  You can pick your Xmas jar-packaged present from Maven Central right away.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Since there were no new reported issues after integrating Weld <code>4.0.0.CR1</code> version into GlassFish and WildFly EE 9 preview, we have promoted Weld to <code>Final</code> release.
-                  Latest core version is now <code>4.0.0.Final</code> and Weld API that ships with it is <code>4.0.Final</code>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Functionally, Weld 3 and 4 remain identical and both are getting the same treatment and doses of bugfixes.
-                  The main difference is that Weld 4 operates with EE 9, meaning it expects you to use it with CDI 3.0 along with the new <code>jakarta</code> package names.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Given that most changes poured into this version were more about dependecy updates, structural changes etc., I won&#8217;t list them all here.
-                  However, if you are still curious, you could take a peek at <a href="https://issues.redhat.com/projects/WELD?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page&amp;status=all">JIRA release page</a> and browse various Weld 4 releases that we did over time.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>What&#8217;s more important is that we are keen on hearing from you should you find any issues with this version.
-                  Whether you are an integrator or user, we realize no project is ever bug-free and we want to smack those bugs!
-                  So if you hit any problems that you think are bugs, let us know via one of the usual channels:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Ask on mailing list <code>weld-dev@lists.jboss.org</code></p>
-                  </li>
-                  <li>
-                  <p>Create <a href="https://issues.redhat.com/projects/WELD/summary">JIRA</a> issues</p>
-                  </li>
-                  <li>
-                  <p>Drop the question on <a href="https://gitter.im/weld/user">Weld Gitter</a></p>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>Last but not least, the Weld team wishes you Merry Christmas and Happy New Year.</p>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_wildfly_patch">WildFly Patch</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>Sorry to disappoint, but we cannot provide a patch yet.
-                  WildFly <a href="https://github.com/wildfly/wildfly/tree/master/ee-9">source code</a> already contains the needed bits for EE 9 server variant, but there wasn&#8217;t a release yet.
-                  Good news is, once there is a release, it will already contain Weld 4 Final!
-                  From there on, we can then deliver patches as we used to.</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.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=12352570" 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/18.html" class="page-link">18</a> <a href="/news/page/19.html" class="page-link">19</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 a6e4104b..b7e3ac0e 100644
--- a/news/page/6.html
+++ b/news/page/6.html
@@ -141,6 +141,79 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2020/12/16/weld-400Final/">Weld 4.0.0.Final</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2020-12-16
+                  &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>An early Xmas present for CDI lovers is here - <code>Final</code> release for Weld 4 is now available!
+                  You can pick your Xmas jar-packaged present from Maven Central right away.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Since there were no new reported issues after integrating Weld <code>4.0.0.CR1</code> version into GlassFish and WildFly EE 9 preview, we have promoted Weld to <code>Final</code> release.
+                  Latest core version is now <code>4.0.0.Final</code> and Weld API that ships with it is <code>4.0.Final</code>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Functionally, Weld 3 and 4 remain identical and both are getting the same treatment and doses of bugfixes.
+                  The main difference is that Weld 4 operates with EE 9, meaning it expects you to use it with CDI 3.0 along with the new <code>jakarta</code> package names.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Given that most changes poured into this version were more about dependecy updates, structural changes etc., I won&#8217;t list them all here.
+                  However, if you are still curious, you could take a peek at <a href="https://issues.redhat.com/projects/WELD?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page&amp;status=all">JIRA release page</a> and browse various Weld 4 releases that we did over time.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>What&#8217;s more important is that we are keen on hearing from you should you find any issues with this version.
+                  Whether you are an integrator or user, we realize no project is ever bug-free and we want to smack those bugs!
+                  So if you hit any problems that you think are bugs, let us know via one of the usual channels:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Ask on mailing list <code>weld-dev@lists.jboss.org</code></p>
+                  </li>
+                  <li>
+                  <p>Create <a href="https://issues.redhat.com/projects/WELD/summary">JIRA</a> issues</p>
+                  </li>
+                  <li>
+                  <p>Drop the question on <a href="https://gitter.im/weld/user">Weld Gitter</a></p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>Last but not least, the Weld team wishes you Merry Christmas and Happy New Year.</p>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_wildfly_patch">WildFly Patch</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>Sorry to disappoint, but we cannot provide a patch yet.
+                  WildFly <a href="https://github.com/wildfly/wildfly/tree/master/ee-9">source code</a> already contains the needed bits for EE 9 server variant, but there wasn&#8217;t a release yet.
+                  Good news is, once there is a release, it will already contain Weld 4 Final!
+                  From there on, we can then deliver patches as we used to.</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.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=12352570" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2020/09/18/weld-400Beta1/">Weld 4.0.0.Beta1</a>
@@ -577,102 +650,6 @@ <h2 id="_wildfly_patch">WildFly Patch</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2019/11/28/weld-313Final/">Weld 3.1.3.Final</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2019-11-28
-                  &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.3.Final arrives along with Weld API 3.1.SP2.
-                  This is a minor update which had a main goal of swapping whole Weld internals from Java EE 8 to Jakarta EE 8.</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>API was transferred to Jakarta EE GAVs (<a href="https://issues.jboss.org/browse/WELD-2598" target="_blank" rel="noopener">WELD-2598</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Weld Core</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Core and whole testing was transferred to Jakarta EE GAvs (<a href="https://issues.jboss.org/browse/WELD-2598" target="_blank" rel="noopener">WELD-2598</a>)</p>
-                  </li>
-                  <li>
-                  <p>Properties inside <code>beans.xml</code> now support spec-descriptor-property-replacement on WildFly (<a href="https://issues.jboss.org/browse/WELD-2600" target="_blank" rel="noopener">WELD-2600</a>)</p>
-                  </li>
-                  <li>
-                  <p>Rolling updates delimiter is now correctly ignored for external bean archives (<a href="https://issues.jboss.org/browse/WELD-2596" target="_blank" rel="noopener">WELD-2596</a>)</p>
-                  </li>
-                  <li>
-                  <p>Allow for <code>private final</code> method in intercepted beans, these methods are then ignored during interception but Weld no longer blows up (<a href="https://issues.jboss.org/browse/WELD-2595" target="_blank" rel="noopener">WELD-2595</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Weld Servlet</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Adjust Jetty attributes accordingly to how they were renamed (<a href="https://issues.jboss.org/browse/WELD-2597" target="_blank" rel="noopener">WELD-2597</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Other</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Fix several misplaced licenses that were causing confusion (<a href="https://issues.jboss.org/browse/WELD-2599" target="_blank" rel="noopener">WELD-2599</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>This time around, the <a href="http://download.jboss.org/weld/3.1.3.Final/wildfly-18.0.1.Final-weld-3.1.3.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly 18.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.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=12342783" target="_blank" rel="noopener">Release notes</a> &#93;</p>
-                  </div>
-                  </div>
-                  </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/18.html" class="page-link">18</a> <a href="/news/page/19.html" class="page-link">19</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 cf8b5c91..ddbe3e94 100644
--- a/news/page/7.html
+++ b/news/page/7.html
@@ -141,6 +141,102 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2019/11/28/weld-313Final/">Weld 3.1.3.Final</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2019-11-28
+                  &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.3.Final arrives along with Weld API 3.1.SP2.
+                  This is a minor update which had a main goal of swapping whole Weld internals from Java EE 8 to Jakarta EE 8.</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>API was transferred to Jakarta EE GAVs (<a href="https://issues.jboss.org/browse/WELD-2598" target="_blank" rel="noopener">WELD-2598</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Weld Core</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Core and whole testing was transferred to Jakarta EE GAvs (<a href="https://issues.jboss.org/browse/WELD-2598" target="_blank" rel="noopener">WELD-2598</a>)</p>
+                  </li>
+                  <li>
+                  <p>Properties inside <code>beans.xml</code> now support spec-descriptor-property-replacement on WildFly (<a href="https://issues.jboss.org/browse/WELD-2600" target="_blank" rel="noopener">WELD-2600</a>)</p>
+                  </li>
+                  <li>
+                  <p>Rolling updates delimiter is now correctly ignored for external bean archives (<a href="https://issues.jboss.org/browse/WELD-2596" target="_blank" rel="noopener">WELD-2596</a>)</p>
+                  </li>
+                  <li>
+                  <p>Allow for <code>private final</code> method in intercepted beans, these methods are then ignored during interception but Weld no longer blows up (<a href="https://issues.jboss.org/browse/WELD-2595" target="_blank" rel="noopener">WELD-2595</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Weld Servlet</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Adjust Jetty attributes accordingly to how they were renamed (<a href="https://issues.jboss.org/browse/WELD-2597" target="_blank" rel="noopener">WELD-2597</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Other</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Fix several misplaced licenses that were causing confusion (<a href="https://issues.jboss.org/browse/WELD-2599" target="_blank" rel="noopener">WELD-2599</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>This time around, the <a href="http://download.jboss.org/weld/3.1.3.Final/wildfly-18.0.1.Final-weld-3.1.3.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly 18.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.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=12342783" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2019/08/06/weld-312Final/">Weld 3.1.2.Final</a>
@@ -718,161 +814,6 @@ <h2 id="_wildfly_patch">WildFly Patch</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2018/07/26/weld-305Final/">Weld 3.0.5.Final</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2018-7-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.5.Final is here and hand in hand with it comes Weld API 3.0.SP4.
-                  And in case you missed it, there was <a href="https://search.maven.org/#artifactdetails%7Cjavax.enterprise%7Ccdi-api%7C2.0.SP1%7Cjar">CDI 2.0.SP1 release</a> as well.
-                  It comes with few <a href="https://issues.jboss.org/issues/?jql=project%20%3D%20CDI%20AND%20fixVersion%20%3D%202.0.SP1">security manager related fixes</a> and Weld is of course compliant with it.
-                  If you are running on a servlet or in SE, you may need to update it yourself, in case of EE it usually falls to the server to update this dependency for you.</p>
-                  </div>
-                  <div class="admonitionblock note">
-                  <table>
-                  <tr>
-                  <td class="icon">
-                  <div class="title">Note</div>
-                  </td>
-                  <td class="content">
-                  This time around we are not providing a patch for WildFly 13 as there were major changes blocking us from doing so.
-                  However, Wildfly 14 will contain all of the above updates - Weld core, Weld API, CDI API - so keep an eye out for its release!
-                  </td>
-                  </tr>
-                  </table>
-                  </div>
-                  <div class="paragraph">
-                  <p>As for updates and fixes, we keep looking at JDK 11 and have done another round of fixing to keep up with adjustments and removals going on in JDK.
-                  There is a bunch of interceptor/decorator fixes for those of you who indulge in using complex class hierarchies with abstractions, generics and default methods.
-                  So let&#8217;s take a look at them all, shall we?</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>Fixed possible race condition appearing during bean index creation (<a href="https://issues.jboss.org/browse/WELD-2492" target="_blank" rel="noopener">WELD-2492</a>)</p>
-                  </li>
-                  <li>
-                  <p>Avoid creating unnecessary bean metatada for anonymous and local classes (<a href="https://issues.jboss.org/browse/WELD-2498" target="_blank" rel="noopener">WELD-2498</a>)</p>
-                  </li>
-                  <li>
-                  <p>Corrected decorator subclass creation when said decorator overrides only default method (<a href="https://issues.jboss.org/browse/WELD-2501" target="_blank" rel="noopener">WELD-2501</a>)</p>
-                  </li>
-                  <li>
-                  <p>Avoid optimizing self invocation of private methods in order to avoid <code>IllegalAccessError</code> (<a href="https://issues.jboss.org/browse/WELD-2506" target="_blank" rel="noopener">WELD-2506</a>)</p>
-                  </li>
-                  <li>
-                  <p>Allow interception of abstract, package-private classes with public methods (<a href="https://issues.jboss.org/browse/WELD-2507" target="_blank" rel="noopener">WELD-2507</a>)</p>
-                  </li>
-                  <li>
-                  <p>Fix interception of overriden generic methods invoked via superclass (<a href="https://issues.jboss.org/browse/WELD-2514" target="_blank" rel="noopener">WELD-2514</a>)</p>
-                  </li>
-                  <li>
-                  <p>Implement reflection fallback for qualifier loading when there are multiple instances of the class in the deployment (<a href="https://issues.jboss.org/browse/WELD-2250" target="_blank" rel="noopener">WELD-2250</a>)</p>
-                  </li>
-                  <li>
-                  <p>Make conversation ID parameter detection more robust (<a href="https://issues.jboss.org/browse/WELD-2512" target="_blank" rel="noopener">WELD-2512</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Weld SE</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Make default <code>StartMain</code> more container friendly by exiting with error code should an exception appear (<a href="https://issues.jboss.org/browse/WELD-2502" target="_blank" rel="noopener">WELD-2502</a>)</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>There is also a follow-up custom exception handling proposal if you want to glance at it (<a href="https://issues.jboss.org/browse/WELD-2503" target="_blank" rel="noopener">WELD-2503</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Fix possible NPE coming from <code>beans.xml</code> merging in complex Weld SE deployment scenarios (<a href="https://issues.jboss.org/browse/WELD-2515" target="_blank" rel="noopener">WELD-2515</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>JDK 9/10 and onwards</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p><code>WeldProvider</code> moved to servlet core module to align it with how Jigsaw handles services (<a href="https://issues.jboss.org/browse/WELD-2435" target="_blank" rel="noopener">WELD-2435</a>)</p>
-                  </li>
-                  <li>
-                  <p>Fixed SE/Servlet resource loading behavior when <code>ForkJoinPool</code> is used on JDK 9+ (<a href="https://issues.jboss.org/browse/WELD-2494" target="_blank" rel="noopener">WELD-2494</a>)</p>
-                  </li>
-                  <li>
-                  <p>Review executability of Weld examples on JDK 10+ (<a href="https://issues.jboss.org/browse/WELD-2495" target="_blank" rel="noopener">WELD-2495</a>)</p>
-                  </li>
-                  <li>
-                  <p>Update to JBoss Classfilewriter 1.2.3.Final which is JDK 11 compliant (<a href="https://issues.jboss.org/browse/WELD-2509" target="_blank" rel="noopener">WELD-2509</a>)</p>
-                  </li>
-                  <li>
-                  <p>If running in JPMS, remove dependency on <code>java.desktop</code> to shrink the footprint (<a href="https://issues.jboss.org/browse/WELD-2504" target="_blank" rel="noopener">WELD-2504</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Probe development tool</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Probe now recognizes <code>BeforeDestroyed</code> event (<a href="https://issues.jboss.org/browse/WELD-2500" target="_blank" rel="noopener">WELD-2500</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Other</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>We are now looking at testing Weld with JDK 11 on a regular basis and have taken steps to ensure it works (<a href="https://issues.jboss.org/browse/WELD-2516" target="_blank" rel="noopener">WELD-2516</a>)</p>
-                  </li>
-                  <li>
-                  <p>Updated patching profiles for Weld 3 and WFLY, the process is now more automated and configurable (<a href="https://issues.jboss.org/browse/WELD-2491" target="_blank" rel="noopener">WELD-2491</a>)</p>
-                  </li>
-                  <li>
-                  <p>OSGi bundle now import BCEL only optionally (<a href="https://issues.jboss.org/browse/WELD-2499" target="_blank" rel="noopener">WELD-2499</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>&#91; <a href="/download/">Download</a> &#93;
-                  &#91; <a href="http://docs.jboss.org/weld/reference/3.0.5.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=12337420" target="_blank" rel="noopener">Release notes</a> &#93;</p>
-                  </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/18.html" class="page-link">18</a> <a href="/news/page/19.html" class="page-link">19</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 174fbc39..f60a5876 100644
--- a/news/page/8.html
+++ b/news/page/8.html
@@ -141,6 +141,161 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2018/07/26/weld-305Final/">Weld 3.0.5.Final</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2018-7-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.5.Final is here and hand in hand with it comes Weld API 3.0.SP4.
+                  And in case you missed it, there was <a href="https://search.maven.org/#artifactdetails%7Cjavax.enterprise%7Ccdi-api%7C2.0.SP1%7Cjar">CDI 2.0.SP1 release</a> as well.
+                  It comes with few <a href="https://issues.jboss.org/issues/?jql=project%20%3D%20CDI%20AND%20fixVersion%20%3D%202.0.SP1">security manager related fixes</a> and Weld is of course compliant with it.
+                  If you are running on a servlet or in SE, you may need to update it yourself, in case of EE it usually falls to the server to update this dependency for you.</p>
+                  </div>
+                  <div class="admonitionblock note">
+                  <table>
+                  <tr>
+                  <td class="icon">
+                  <div class="title">Note</div>
+                  </td>
+                  <td class="content">
+                  This time around we are not providing a patch for WildFly 13 as there were major changes blocking us from doing so.
+                  However, Wildfly 14 will contain all of the above updates - Weld core, Weld API, CDI API - so keep an eye out for its release!
+                  </td>
+                  </tr>
+                  </table>
+                  </div>
+                  <div class="paragraph">
+                  <p>As for updates and fixes, we keep looking at JDK 11 and have done another round of fixing to keep up with adjustments and removals going on in JDK.
+                  There is a bunch of interceptor/decorator fixes for those of you who indulge in using complex class hierarchies with abstractions, generics and default methods.
+                  So let&#8217;s take a look at them all, shall we?</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>Fixed possible race condition appearing during bean index creation (<a href="https://issues.jboss.org/browse/WELD-2492" target="_blank" rel="noopener">WELD-2492</a>)</p>
+                  </li>
+                  <li>
+                  <p>Avoid creating unnecessary bean metatada for anonymous and local classes (<a href="https://issues.jboss.org/browse/WELD-2498" target="_blank" rel="noopener">WELD-2498</a>)</p>
+                  </li>
+                  <li>
+                  <p>Corrected decorator subclass creation when said decorator overrides only default method (<a href="https://issues.jboss.org/browse/WELD-2501" target="_blank" rel="noopener">WELD-2501</a>)</p>
+                  </li>
+                  <li>
+                  <p>Avoid optimizing self invocation of private methods in order to avoid <code>IllegalAccessError</code> (<a href="https://issues.jboss.org/browse/WELD-2506" target="_blank" rel="noopener">WELD-2506</a>)</p>
+                  </li>
+                  <li>
+                  <p>Allow interception of abstract, package-private classes with public methods (<a href="https://issues.jboss.org/browse/WELD-2507" target="_blank" rel="noopener">WELD-2507</a>)</p>
+                  </li>
+                  <li>
+                  <p>Fix interception of overriden generic methods invoked via superclass (<a href="https://issues.jboss.org/browse/WELD-2514" target="_blank" rel="noopener">WELD-2514</a>)</p>
+                  </li>
+                  <li>
+                  <p>Implement reflection fallback for qualifier loading when there are multiple instances of the class in the deployment (<a href="https://issues.jboss.org/browse/WELD-2250" target="_blank" rel="noopener">WELD-2250</a>)</p>
+                  </li>
+                  <li>
+                  <p>Make conversation ID parameter detection more robust (<a href="https://issues.jboss.org/browse/WELD-2512" target="_blank" rel="noopener">WELD-2512</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Weld SE</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Make default <code>StartMain</code> more container friendly by exiting with error code should an exception appear (<a href="https://issues.jboss.org/browse/WELD-2502" target="_blank" rel="noopener">WELD-2502</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>There is also a follow-up custom exception handling proposal if you want to glance at it (<a href="https://issues.jboss.org/browse/WELD-2503" target="_blank" rel="noopener">WELD-2503</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Fix possible NPE coming from <code>beans.xml</code> merging in complex Weld SE deployment scenarios (<a href="https://issues.jboss.org/browse/WELD-2515" target="_blank" rel="noopener">WELD-2515</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>JDK 9/10 and onwards</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p><code>WeldProvider</code> moved to servlet core module to align it with how Jigsaw handles services (<a href="https://issues.jboss.org/browse/WELD-2435" target="_blank" rel="noopener">WELD-2435</a>)</p>
+                  </li>
+                  <li>
+                  <p>Fixed SE/Servlet resource loading behavior when <code>ForkJoinPool</code> is used on JDK 9+ (<a href="https://issues.jboss.org/browse/WELD-2494" target="_blank" rel="noopener">WELD-2494</a>)</p>
+                  </li>
+                  <li>
+                  <p>Review executability of Weld examples on JDK 10+ (<a href="https://issues.jboss.org/browse/WELD-2495" target="_blank" rel="noopener">WELD-2495</a>)</p>
+                  </li>
+                  <li>
+                  <p>Update to JBoss Classfilewriter 1.2.3.Final which is JDK 11 compliant (<a href="https://issues.jboss.org/browse/WELD-2509" target="_blank" rel="noopener">WELD-2509</a>)</p>
+                  </li>
+                  <li>
+                  <p>If running in JPMS, remove dependency on <code>java.desktop</code> to shrink the footprint (<a href="https://issues.jboss.org/browse/WELD-2504" target="_blank" rel="noopener">WELD-2504</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Probe development tool</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Probe now recognizes <code>BeforeDestroyed</code> event (<a href="https://issues.jboss.org/browse/WELD-2500" target="_blank" rel="noopener">WELD-2500</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Other</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>We are now looking at testing Weld with JDK 11 on a regular basis and have taken steps to ensure it works (<a href="https://issues.jboss.org/browse/WELD-2516" target="_blank" rel="noopener">WELD-2516</a>)</p>
+                  </li>
+                  <li>
+                  <p>Updated patching profiles for Weld 3 and WFLY, the process is now more automated and configurable (<a href="https://issues.jboss.org/browse/WELD-2491" target="_blank" rel="noopener">WELD-2491</a>)</p>
+                  </li>
+                  <li>
+                  <p>OSGi bundle now import BCEL only optionally (<a href="https://issues.jboss.org/browse/WELD-2499" target="_blank" rel="noopener">WELD-2499</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="/download/">Download</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/3.0.5.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=12337420" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2018/07/10/weld-team-changes/">Weld team changes</a>
@@ -621,135 +776,6 @@ <h2 id="_wildfly_patch">WildFly Patch</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2017/12/19/weld-meets-junit5/">Weld meets JUnit 5</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2017-12-19
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/junit">junit</a>
-                    ,
-                    <a href="/news/tags/testing">testing</a>
-                    ,
-                    <a href="/news/tags/weld-se">weld-se</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Matej Novotny
-                </div>
-                <p></p>
-                <div class="content">
-                  <div id="toc" class="toc">
-                  <div id="toctitle" class="title">Contents</div>
-                  <ul class="sectlevel1">
-                  <li><a href="#_gav_coordinates">GAV Coordinates</a></li>
-                  <li><a href="#_first_steps">First Steps</a></li>
-                  <li><a href="#_dude_where_is_my_container">Dude, Where Is My Container?</a></li>
-                  <li><a href="#_help_i_am_stuck_with_junit_4">Help, I Am Stuck With JUnit 4</a></li>
-                  <li><a href="#_what_if_i_would_like_to">What If I Would Like To&#8230;&#8203;</a></li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>In this article I want to bring <a href="https://github.com/weld/weld-junit" target="_blank" rel="noopener">weld-junit</a> into light.
-                  You might have heard about or, better still, used our extension for JUnit 4 which has been around for some time now.
-                  But after getting ourselves acquainted with JUnit 5, we decided we should create another one for JUnit 5.
-                  In the sections below I will try to introduce the basic usage and ideas behind it, for more in depth information, you can glance the <a href="https://github.com/weld/weld-junit/blob/master/junit5/README.md">readme file</a> residing directly in the repository.</p>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_gav_coordinates">GAV Coordinates</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>Here are group and artifact IDs you need to grab the artifact for Maven projects:</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;dependency&gt;&#x000A;      &lt;groupId&gt;org.jboss.weld&lt;/groupId&gt;&#x000A;      &lt;artifactId&gt;weld-junit-parent&lt;/artifactId&gt;&#x000A;      &lt;version&gt;${weld.junit.version}&lt;/version&gt;&#x000A;    &lt;/dependency&gt;</code></pre>
-                  </div>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_first_steps">First Steps</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>You can use the extension as you would any other in JUnit 5, via <code>@ExtendWith</code> from JUnit library along with the name of our extension - <code>org.jboss.weld.junit5.WeldJunit5Extension</code>.
-                  Alternatively, there is a shorter annotation <code>@org.jboss.weld.junit5.EnableWeld</code>.
-                  Both of these can be used on class and method level.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Hence your test could look like this:</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>[ source, java ]</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre>@EnableWeld&#x000A;    public class InjectionWithWeldTest {&#x000A;    &#x000A;      @Inject&#x000A;      BarBean beanAsField;&#x000A;    &#x000A;      @Test&#x000A;      public void testThatItWorks(FooBean beanAsParam) {&#x000A;        assertNotNull(beanAsParam);&#x000A;        beanAsParam.ping();&#x000A;        assertNotNull(beanAsField);&#x000A;        beanAsField.ping();&#x000A;      }&#x000A;    &#x000A;    }</pre>
-                  </div>
-                  </div>
-                  <div class="paragraph">
-                  <p>Behind the scenes, Weld will bootstrap SE container for each test container invocation and tear it down afterwards (works for both, per-method and per-class lifecycle).
-                  As you might have guessed, Weld will also automatically inject into any fields within the test class which you annotated with <code>@Inject</code>.
-                  Furthermore, it will attempt to resolve parameters in your test methods in very much the same way.
-                  But beware, by default Weld will only scan classes from within the test package!
-                  With this in mind, you can play around with beans to your liking.</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_dude_where_is_my_container">Dude, Where Is My Container?</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>Good point, when working with Weld SE you normally have the power to customize container bootstrap and, once running, to query it for beans, fire events and so on.
-                  And you shall retain that right!</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Only you are going to need a public field with type <code>org.jboss.weld.junit5.WeldInitiator</code> which you annotate with <code>@org.jboss.weld.junit5.WeldSetup</code>.
-                  This class has a bunch of static method which will allow you to customize the boostrap and it also works as a handle to grasp the <code>WeldContainer</code> running below.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Too much talk, not enough code, so here we go:</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>[ source, java ]</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre>@ExtendWith(WeldJUnit5Extension.class)&#x000A;    public class WeldJUnit5CustomizedTest {&#x000A;    &#x000A;      @WeldSetup&#x000A;      public WeldInitiator weld = WeldInitiator.of(WeldInitiator.createWeld()&#x000A;                                               .alternatives(FooAlternative.class)&#x000A;                                               .beanClasses(Foo.class, FooAlternative.class)&#x000A;                                               .enableInterceptors(MyInterceptor.class));&#x000A;    &#x000A;      @Inject&#x000A;      Foo bean; // this will be FooAlternative in the end&#x000A;    &#x000A;      @Test&#x000A;      public void testWeldContainerUsage() {&#x000A;        weld.event().select(MyPayload.class).fire(new MyPayload());&#x000A;        weld.select(Foo.class).isResolvable();&#x000A;      }&#x000A;    }</pre>
-                  </div>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_help_i_am_stuck_with_junit_4">Help, I Am Stuck With JUnit 4</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>No problems, we got you covered, check out our <a href="https://github.com/weld/weld-junit/blob/master/junit4/README.md">JUnit 4 extension</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>They are both very similar and easy to master.
-                  The only notable difference is that in JUnit 4 you always need the initiator class - <code>org.jboss.weld.junit4.WeldInitiator</code>.</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_what_if_i_would_like_to">What If I Would Like To&#8230;&#8203;</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>If you&#8217;re stuck and need a helping hand, we are listening on the usual channels - mailing list, Stack Overflow, Gitter, IRC, GitHub.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>It might also be the case that we forgot about something quite important, so don&#8217;t hesitate to reach to us through those channels, or open a GitHub issue straight away.
-                  We are happy for any kind of feedback we can get.</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/18.html" class="page-link">18</a> <a href="/news/page/19.html" class="page-link">19</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 4860d252..d55fe64f 100644
--- a/news/page/9.html
+++ b/news/page/9.html
@@ -141,6 +141,135 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2017/12/19/weld-meets-junit5/">Weld meets JUnit 5</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2017-12-19
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/junit">junit</a>
+                    ,
+                    <a href="/news/tags/testing">testing</a>
+                    ,
+                    <a href="/news/tags/weld-se">weld-se</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Matej Novotny
+                </div>
+                <p></p>
+                <div class="content">
+                  <div id="toc" class="toc">
+                  <div id="toctitle" class="title">Contents</div>
+                  <ul class="sectlevel1">
+                  <li><a href="#_gav_coordinates">GAV Coordinates</a></li>
+                  <li><a href="#_first_steps">First Steps</a></li>
+                  <li><a href="#_dude_where_is_my_container">Dude, Where Is My Container?</a></li>
+                  <li><a href="#_help_i_am_stuck_with_junit_4">Help, I Am Stuck With JUnit 4</a></li>
+                  <li><a href="#_what_if_i_would_like_to">What If I Would Like To&#8230;&#8203;</a></li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>In this article I want to bring <a href="https://github.com/weld/weld-junit" target="_blank" rel="noopener">weld-junit</a> into light.
+                  You might have heard about or, better still, used our extension for JUnit 4 which has been around for some time now.
+                  But after getting ourselves acquainted with JUnit 5, we decided we should create another one for JUnit 5.
+                  In the sections below I will try to introduce the basic usage and ideas behind it, for more in depth information, you can glance the <a href="https://github.com/weld/weld-junit/blob/master/junit5/README.md">readme file</a> residing directly in the repository.</p>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_gav_coordinates">GAV Coordinates</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>Here are group and artifact IDs you need to grab the artifact for Maven projects:</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;dependency&gt;&#x000A;      &lt;groupId&gt;org.jboss.weld&lt;/groupId&gt;&#x000A;      &lt;artifactId&gt;weld-junit-parent&lt;/artifactId&gt;&#x000A;      &lt;version&gt;${weld.junit.version}&lt;/version&gt;&#x000A;    &lt;/dependency&gt;</code></pre>
+                  </div>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_first_steps">First Steps</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>You can use the extension as you would any other in JUnit 5, via <code>@ExtendWith</code> from JUnit library along with the name of our extension - <code>org.jboss.weld.junit5.WeldJunit5Extension</code>.
+                  Alternatively, there is a shorter annotation <code>@org.jboss.weld.junit5.EnableWeld</code>.
+                  Both of these can be used on class and method level.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Hence your test could look like this:</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>[ source, java ]</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre>@EnableWeld&#x000A;    public class InjectionWithWeldTest {&#x000A;    &#x000A;      @Inject&#x000A;      BarBean beanAsField;&#x000A;    &#x000A;      @Test&#x000A;      public void testThatItWorks(FooBean beanAsParam) {&#x000A;        assertNotNull(beanAsParam);&#x000A;        beanAsParam.ping();&#x000A;        assertNotNull(beanAsField);&#x000A;        beanAsField.ping();&#x000A;      }&#x000A;    &#x000A;    }</pre>
+                  </div>
+                  </div>
+                  <div class="paragraph">
+                  <p>Behind the scenes, Weld will bootstrap SE container for each test container invocation and tear it down afterwards (works for both, per-method and per-class lifecycle).
+                  As you might have guessed, Weld will also automatically inject into any fields within the test class which you annotated with <code>@Inject</code>.
+                  Furthermore, it will attempt to resolve parameters in your test methods in very much the same way.
+                  But beware, by default Weld will only scan classes from within the test package!
+                  With this in mind, you can play around with beans to your liking.</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_dude_where_is_my_container">Dude, Where Is My Container?</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>Good point, when working with Weld SE you normally have the power to customize container bootstrap and, once running, to query it for beans, fire events and so on.
+                  And you shall retain that right!</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Only you are going to need a public field with type <code>org.jboss.weld.junit5.WeldInitiator</code> which you annotate with <code>@org.jboss.weld.junit5.WeldSetup</code>.
+                  This class has a bunch of static method which will allow you to customize the boostrap and it also works as a handle to grasp the <code>WeldContainer</code> running below.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Too much talk, not enough code, so here we go:</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>[ source, java ]</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre>@ExtendWith(WeldJUnit5Extension.class)&#x000A;    public class WeldJUnit5CustomizedTest {&#x000A;    &#x000A;      @WeldSetup&#x000A;      public WeldInitiator weld = WeldInitiator.of(WeldInitiator.createWeld()&#x000A;                                               .alternatives(FooAlternative.class)&#x000A;                                               .beanClasses(Foo.class, FooAlternative.class)&#x000A;                                               .enableInterceptors(MyInterceptor.class));&#x000A;    &#x000A;      @Inject&#x000A;      Foo bean; // this will be FooAlternative in the end&#x000A;    &#x000A;      @Test&#x000A;      public void testWeldContainerUsage() {&#x000A;        weld.event().select(MyPayload.class).fire(new MyPayload());&#x000A;        weld.select(Foo.class).isResolvable();&#x000A;      }&#x000A;    }</pre>
+                  </div>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_help_i_am_stuck_with_junit_4">Help, I Am Stuck With JUnit 4</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>No problems, we got you covered, check out our <a href="https://github.com/weld/weld-junit/blob/master/junit4/README.md">JUnit 4 extension</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>They are both very similar and easy to master.
+                  The only notable difference is that in JUnit 4 you always need the initiator class - <code>org.jboss.weld.junit4.WeldInitiator</code>.</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_what_if_i_would_like_to">What If I Would Like To&#8230;&#8203;</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>If you&#8217;re stuck and need a helping hand, we are listening on the usual channels - mailing list, Stack Overflow, Gitter, IRC, GitHub.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>It might also be the case that we forgot about something quite important, so don&#8217;t hesitate to reach to us through those channels, or open a GitHub issue straight away.
+                  We are happy for any kind of feedback we can get.</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2017/12/18/weld-246Final/">Weld 2.4.6.Final</a>
@@ -627,203 +756,6 @@ <h2 id="_wildfly_patch">WildFly Patch</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2017/08/07/weld-vertx-next/">Weld Vert.x Next?</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2017-8-7
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/vertx">vertx</a>
-                    ,
-                    <a href="/news/tags/integration">integration</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="#_what_is_it_good_for">What Is It Good For?</a>
-                  <ul class="sectlevel2">
-                  <li><a href="#_modules">Modules</a></li>
-                  </ul>
-                  </li>
-                  <li><a href="#_how_do_i_use_it_in_my_vert_x_webapp">How Do I Use It In My Vert.x Webapp?</a>
-                  <ul class="sectlevel2">
-                  <li><a href="#_1_project_configuration">1. Project Configuration</a></li>
-                  <li><a href="#_2_start_cdi_container">2. Start CDI Container</a></li>
-                  <li><a href="#_3_observe_events">3. Observe Events</a></li>
-                  <li><a href="#_4_declare_routes">4. Declare Routes</a></li>
-                  <li><a href="#_5_enjoy_and_celebrate">5. Enjoy and Celebrate</a></li>
-                  </ul>
-                  </li>
-                  <li><a href="#_future_and_plans">Future and Plans</a></li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>Last year Weld team announced the <a href="https://github.com/weld/weld-vertx" target="_blank" rel="noopener">weld-vertx</a> project (see also <a href="/news/2016/04/11/weld-meets-vertx/" target="_blank" rel="noopener">Weld meets Vert.x</a> and <a href="/news/2016/06/21/update-on-weld-vertx/" target="_blank" rel="noopener">Update on weld-vertx</a> articles).
-                  The goal was clear - bring the CDI programming model into the Vert.x ecosystem.
-                  Since then, several things have changed.
-                  Two new modules were added, <strong>CDI 2</strong> and <strong>Weld 3</strong> is now used by default, and <a href="http://search.maven.org/#search%7Cga%7C1%7Cweld-vertx" target="_blank" rel="noopener">two final versions</a> were released.
-                  I think it&#8217;s a good time to summarize the features and plans for future.</p>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_what_is_it_good_for">What Is It Good For?</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>First of all, it offers a mature component model for business logic in your Vert.x applications.
-                  A reasonable component model helps making your applications maintainable and scalable in terms of development and reusability.
-                  So the primary intention is to <em>implement the business logic as CDI beans and use Vert.x APIs for everything else</em>.</p>
-                  </div>
-                  <div class="sect2">
-                  <h3 id="_modules">Modules</h3>
-                  <div class="paragraph">
-                  <p>So far there are four modules available:</p>
-                  </div>
-                  <div class="olist arabic">
-                  <ol class="arabic">
-                  <li>
-                  <p>The <em>Core</em> module starts/stops the Weld SE container and to notifies CDI observer methods when a message is sent via Vert.x event bus. Also you can inject <code>io.vertx.core.Vertx</code> and <code>io.vertx.core.Context</code> in any CDI bean.</p>
-                  </li>
-                  <li>
-                  <p>The <em>Web</em> module allows to configure the router (a component responsible to find the "logic" to handle an HTTP request) in a declarative way, using <code>@org.jboss.weld.vertx.web.WebRoute</code> annotation. Of course, you can register routes programatically. But what if there are hundreds of routes? The more complicated the REST API is the more difficult it is to maintain the code.</p>
-                  </li>
-                  <li>
-                  <p>The <em>Service Proxy</em> module makes it possible to inject and invoke service proxies (as defined in <a href="https://github.com/vert-x3/vertx-service-proxy" class="bare">https://github.com/vert-x3/vertx-service-proxy</a>).</p>
-                  </li>
-                  <li>
-                  <p>The <em>Probe</em> module enables Weld Probe development tool in a Vert.x application.</p>
-                  </li>
-                  </ol>
-                  </div>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_how_do_i_use_it_in_my_vert_x_webapp">How Do I Use It In My Vert.x Webapp?</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>Let&#8217;s enhance an existing webapp in four simple steps.</p>
-                  </div>
-                  <div class="sect2">
-                  <h3 id="_1_project_configuration">1. Project Configuration</h3>
-                  <div class="paragraph">
-                  <p>Jus add the following dependency to your <code>pom.xml</code> and <a href="https://github.com/weld/weld-vertx/blob/master/examples/hello/src/main/resources/META-INF/beans.xml">beans.xml</a> into <code>src/main/resources/META-INF</code> (this will enable CDI).</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;dependency&gt;&#x000A;      &lt;groupId&gt;org.jboss.weld.vertx&lt;/groupId&gt;&#x000A;      &lt;artifactId&gt;weld-vertx-web&lt;/artifactId&gt;&#x000A;      &lt;version&gt;${version.weld-vertx}&lt;/version&gt;&#x000A;    &lt;/dependency&gt;</code></pre>
-                  </div>
-                  </div>
-                  <div class="admonitionblock note">
-                  <table>
-                  <tr>
-                  <td class="icon">
-                  <div class="title">Note</div>
-                  </td>
-                  <td class="content">
-                  This also brings in <code>org.jboss.weld.vertx:weld-vertx-core</code>, Vert.x and Weld dependencies.
-                  </td>
-                  </tr>
-                  </table>
-                  </div>
-                  </div>
-                  <div class="sect2">
-                  <h3 id="_2_start_cdi_container">2. Start CDI Container</h3>
-                  <div class="paragraph">
-                  <p>Deploy <code>WeldWebVerticle</code> and configure router:</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">class MyVertxApp {&#x000A;    &#x000A;         public static void main(String[] args) {&#x000A;             final Vertx vertx = Vertx.vertx();&#x000A;             // ...deploy other existing verticles&#x000A;             final WeldWebVerticle weldVerticle = new WeldWebVerticle();&#x000A;             vertx.deployVerticle(weldVerticle, result -&gt; {&#x000A;                 if (result.succeeded()) {&#x000A;                     vertx.createHttpServer().requestHandler(weldVerticle.createRouter()::accept).listen(8080);&#x000A;                 }&#x000A;             });&#x000A;         }&#x000A;     }</code></pre>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect2">
-                  <h3 id="_3_observe_events">3. Observe Events</h3>
-                  <div class="paragraph">
-                  <p>Create a CDI observer method to consume messages from the Vert.x event bus.
-                  <code>@VertxConsumer</code> qualifier is used to specify the address the consumer will be registered to.
-                  <code>VertxEvent</code> is a wrapper of a Vert.x message.</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@ApplicationScoped&#x000A;    class HelloBean {&#x000A;    &#x000A;      void consumerWithDependencies(@Observes @VertxConsumer("hello.address") VertxEvent event, HelloService service) {&#x000A;        // Reply to the message - io.vertx.core.eventbus.Message.reply(Object)&#x000A;        event.setReply(service.hello());&#x000A;      }&#x000A;    }</code></pre>
-                  </div>
-                  </div>
-                  <div class="admonitionblock note">
-                  <table>
-                  <tr>
-                  <td class="icon">
-                  <div class="title">Note</div>
-                  </td>
-                  <td class="content">
-                  Since we’re working with regular observer methods, additional parameters may be declared (next to the event parameter) - these parameters are injection points.
-                  </td>
-                  </tr>
-                  </table>
-                  </div>
-                  </div>
-                  <div class="sect2">
-                  <h3 id="_4_declare_routes">4. Declare Routes</h3>
-                  <div class="paragraph">
-                  <p>Annotate a class implementing <code>Handler&lt;RoutingContext&gt;</code> with <code>@org.jboss.weld.vertx.web.WebRoute</code>:</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@WebRoute("/hello") // Matches all HTTP methods&#x000A;    class HelloHandler implements Handler&lt;RoutingContext&gt; {&#x000A;    &#x000A;        @Inject&#x000A;        HelloService service;&#x000A;    &#x000A;        @Override&#x000A;        public void handle(RoutingContext ctx) {&#x000A;            ctx.response().setStatusCode(200).end(service.hello());&#x000A;        }&#x000A;    }</code></pre>
-                  </div>
-                  </div>
-                  <div class="paragraph">
-                  <p>This will be translated into something like:</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">void integrationPseudoCode() {&#x000A;      HelloHandler hello = produceInjectedInstanceOfHelloHandler();&#x000A;      Router router = obtainRouterInstance();&#x000A;      router.route("/hello").handler(hello);&#x000A;    }</code></pre>
-                  </div>
-                  </div>
-                  <div class="admonitionblock note">
-                  <table>
-                  <tr>
-                  <td class="icon">
-                  <div class="title">Note</div>
-                  </td>
-                  <td class="content">
-                  <code>@WebRoute</code> is repeatable, i.e. if multiple annotations are declared on a handler class a single handler instance is used for multiple routes.
-                  </td>
-                  </tr>
-                  </table>
-                  </div>
-                  </div>
-                  <div class="sect2">
-                  <h3 id="_5_enjoy_and_celebrate">5. Enjoy and Celebrate</h3>
-                  <div class="paragraph">
-                  <p>And that&#8217;s it.
-                  Fairly straightforward, isn&#8217;t it?</p>
-                  </div>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_future_and_plans">Future and Plans</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>So far there are no new features on the roadmap.
-                  The plan is to provide bugfix releases as needed.
-                  But <code>weld-vertx</code> is an open source project and so the future is in hands of the community.
-                  Feel free to <a href="https://github.com/weld/weld-vertx/issues">create issues, share ideas, throw feature requests</a> and send pull requests!</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/18.html" class="page-link">18</a> <a href="/news/page/19.html" class="page-link">19</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 b7ccdbf9..f4959503 100644
--- a/news/tags/release/index.html
+++ b/news/tags/release/index.html
@@ -141,6 +141,60 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2024/12/16/weld-514Final/">Weld 5.1.4.Final</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2024-12-16
+                  &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 small update for Weld 5.1 (5.1.4.Final) has been released.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>List of changes from 5.1.3.Final version:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Fix resource injection into beans added via extensions (<a href="https://issues.redhat.com/browse/WELD-2798">WELD-2798</a>)</p>
+                  </li>
+                  <li>
+                  <p>Prevent file leak in Weld&#8217;s <code>ServiceLoader</code> (<a href="https://issues.redhat.com/browse/WELD-2800">WELD-2800</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Note that most environments were unaffected by this; the only reported issue was for testing setup of GlassFish on Windows machines</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Deprecate <code>WeldCrossContextFilter</code>, to be removed in Weld 6 (<a href="https://issues.redhat.com/browse/WELD-2803">WELD-2803</a>)</p>
+                  </li>
+                  <li>
+                  <p>Update custom TCK exclusion list used for <code>relaxed mode</code> testing (<a href="https://issues.redhat.com/browse/WELD-2806">WELD-2806</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.4.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=12432223" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2024/11/28/weld-600CR2/">Weld 6.0.0.CR2</a>
@@ -813,69 +867,6 @@ <h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2023/06/12/weld-511Final/">Weld 5.1.1.Final</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2023-6-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>
-                  Matej Novotny
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>It&#8217;s time for some minor updates and fixes, Weld 5.1.1.Final is now available!</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Main highlights are as follows:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Fix bean type assignability for beans with recursive generic types (<a href="https://issues.redhat.com/browse/WELD-2738">WELD-2738</a>)</p>
-                  </li>
-                  <li>
-                  <p>Failing validation for pasivation capability, Weld should throw <code>DeploymentException</code> instead of <code>DefinitionException</code> (<a href="https://issues.redhat.com/browse/WELD-2741">WELD-2741</a>)</p>
-                  </li>
-                  <li>
-                  <p>Avoid firing <code>ProcessInjectionTarget</code> multiple times if a specialized bean was vetoed (<a href="https://issues.redhat.com/browse/WELD-2742">WELD-2742</a>)</p>
-                  </li>
-                  <li>
-                  <p><code>BeanManager#getReference</code> should not create a child <code>CreationalContext</code> instance (<a href="https://issues.redhat.com/browse/WELD-2743">WELD-2743</a>)</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>This should only affect scenarios in which beans were 'manually' created and destroyed in which case the destruction could end up incomplete</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Fix how Weld defines proxies to avoid problems in JDK 17+ along with the newest JBoss Class File Writer (1.3.0.Final) (<a href="https://issues.redhat.com/browse/WELD-2744">WELD-2744</a>)</p>
-                  </li>
-                  <li>
-                  <p>Correction to documentation which incorrectly suggested <code>@ManagedBean</code> was a bean defining annotation (<a href="https://issues.redhat.com/browse/WELD-2737">WELD-2737</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>As always, if you find further issues with Weld 5, 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/5.1.1.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=12397581" 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/6.html" class="page-link">6</a> <a href="/news/tags/release/page/7.html" class="page-link">7</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 8d9201ba..8d6d1c4c 100644
--- a/news/tags/release/page/2.html
+++ b/news/tags/release/page/2.html
@@ -141,6 +141,69 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2023/06/12/weld-511Final/">Weld 5.1.1.Final</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2023-6-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>
+                  Matej Novotny
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>It&#8217;s time for some minor updates and fixes, Weld 5.1.1.Final is now available!</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Main highlights are as follows:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Fix bean type assignability for beans with recursive generic types (<a href="https://issues.redhat.com/browse/WELD-2738">WELD-2738</a>)</p>
+                  </li>
+                  <li>
+                  <p>Failing validation for pasivation capability, Weld should throw <code>DeploymentException</code> instead of <code>DefinitionException</code> (<a href="https://issues.redhat.com/browse/WELD-2741">WELD-2741</a>)</p>
+                  </li>
+                  <li>
+                  <p>Avoid firing <code>ProcessInjectionTarget</code> multiple times if a specialized bean was vetoed (<a href="https://issues.redhat.com/browse/WELD-2742">WELD-2742</a>)</p>
+                  </li>
+                  <li>
+                  <p><code>BeanManager#getReference</code> should not create a child <code>CreationalContext</code> instance (<a href="https://issues.redhat.com/browse/WELD-2743">WELD-2743</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>This should only affect scenarios in which beans were 'manually' created and destroyed in which case the destruction could end up incomplete</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Fix how Weld defines proxies to avoid problems in JDK 17+ along with the newest JBoss Class File Writer (1.3.0.Final) (<a href="https://issues.redhat.com/browse/WELD-2744">WELD-2744</a>)</p>
+                  </li>
+                  <li>
+                  <p>Correction to documentation which incorrectly suggested <code>@ManagedBean</code> was a bean defining annotation (<a href="https://issues.redhat.com/browse/WELD-2737">WELD-2737</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>As always, if you find further issues with Weld 5, 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/5.1.1.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=12397581" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2022/10/03/weld-510Final/">Weld 5.1.0.Final</a>
@@ -902,71 +965,6 @@ <h2 id="_more_in_depth_overview_of_resolved_issues_in_weld_5">More in-depth over
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2021/07/14/weld-402Final-318Final/">Weld 4.0.2.Final and 3.1.8.Final</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2021-7-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>New maintenance releases for Weld 3 and 4 have been rolled out.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>There is only a handful of changes this time so let&#8217;s skid across them:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Prevent <code>WeldInvocationContext</code> from ever returning <code>null</code> when queried for interceptor bindings (<a href="https://issues.jboss.org/browse/WELD-2675" target="_blank" rel="noopener">WELD-2675</a>)</p>
-                  </li>
-                  <li>
-                  <p>Fix an NPE if there is an EJB bean with default package present (<a href="https://issues.jboss.org/browse/WELD-2674" target="_blank" rel="noopener">WELD-2674</a>)</p>
-                  </li>
-                  <li>
-                  <p>Weld wasn&#8217;t working on JDK 17 due to <code>jboss-classfilewriter</code> issue; this should no longer be the case (<a href="https://issues.jboss.org/browse/WELD-2671" target="_blank" rel="noopener">WELD-2671</a>)</p>
-                  </li>
-                  <li>
-                  <p>Correction to proxy name creation for producers based on interfaces - Weld should now use package and class of the most specific interface (<a href="https://issues.jboss.org/browse/WELD-2675" target="_blank" rel="noopener">WELD-2675</a>)</p>
-                  </li>
-                  <li>
-                  <p>Weld now provides correct metadata (via <code>@Decorated</code>) in cases where more than one decorator is applied to a single bean (<a href="https://issues.jboss.org/browse/WELD-2673" target="_blank" rel="noopener">WELD-2673</a>)</p>
-                  </li>
-                  <li>
-                  <p>We have decided to no longer provide WildFly patches for each release (<a href="https://issues.jboss.org/browse/WELD-2660" target="_blank" rel="noopener">WELD-2660</a>)</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>After discussion with WildFly team, we figured the current way is not going to work for anything beyond Weld 3</p>
-                  </li>
-                  <li>
-                  <p>And we aren&#8217;t even certain this feature is requested and/or used anymore; if you feel otherwise, please create a JIRA to let us know</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>&#91; <a href="/download/">Download</a> &#93;
-                  &#91; <a href="http://docs.jboss.org/weld/reference/4.0.2.Final/en-US/html_single/" target="_blank" rel="noopener">Documentation Weld 4.0.2.Final</a> &#93;
-                  &#91; <a href="http://docs.jboss.org/weld/reference/3.1.8.Final/en-US/html_single/" target="_blank" rel="noopener">Documentation Weld 3.1.8.Final</a> &#93;
-                  &#91; <a href="https://issues.redhat.com/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12356277" target="_blank" rel="noopener">Release notes for Weld 4.0.2.Final</a> &#93;
-                  &#91; <a href="https://issues.redhat.com/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12356276" target="_blank" rel="noopener">Release notes for Weld 3.1.8.Final</a> &#93;</p>
-                  </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/6.html" class="page-link">6</a> <a href="/news/tags/release/page/7.html" class="page-link">7</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 ad7fdad3..ef0f9e89 100644
--- a/news/tags/release/page/3.html
+++ b/news/tags/release/page/3.html
@@ -141,6 +141,71 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2021/07/14/weld-402Final-318Final/">Weld 4.0.2.Final and 3.1.8.Final</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2021-7-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>New maintenance releases for Weld 3 and 4 have been rolled out.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>There is only a handful of changes this time so let&#8217;s skid across them:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Prevent <code>WeldInvocationContext</code> from ever returning <code>null</code> when queried for interceptor bindings (<a href="https://issues.jboss.org/browse/WELD-2675" target="_blank" rel="noopener">WELD-2675</a>)</p>
+                  </li>
+                  <li>
+                  <p>Fix an NPE if there is an EJB bean with default package present (<a href="https://issues.jboss.org/browse/WELD-2674" target="_blank" rel="noopener">WELD-2674</a>)</p>
+                  </li>
+                  <li>
+                  <p>Weld wasn&#8217;t working on JDK 17 due to <code>jboss-classfilewriter</code> issue; this should no longer be the case (<a href="https://issues.jboss.org/browse/WELD-2671" target="_blank" rel="noopener">WELD-2671</a>)</p>
+                  </li>
+                  <li>
+                  <p>Correction to proxy name creation for producers based on interfaces - Weld should now use package and class of the most specific interface (<a href="https://issues.jboss.org/browse/WELD-2675" target="_blank" rel="noopener">WELD-2675</a>)</p>
+                  </li>
+                  <li>
+                  <p>Weld now provides correct metadata (via <code>@Decorated</code>) in cases where more than one decorator is applied to a single bean (<a href="https://issues.jboss.org/browse/WELD-2673" target="_blank" rel="noopener">WELD-2673</a>)</p>
+                  </li>
+                  <li>
+                  <p>We have decided to no longer provide WildFly patches for each release (<a href="https://issues.jboss.org/browse/WELD-2660" target="_blank" rel="noopener">WELD-2660</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>After discussion with WildFly team, we figured the current way is not going to work for anything beyond Weld 3</p>
+                  </li>
+                  <li>
+                  <p>And we aren&#8217;t even certain this feature is requested and/or used anymore; if you feel otherwise, please create a JIRA to let us know</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="/download/">Download</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/4.0.2.Final/en-US/html_single/" target="_blank" rel="noopener">Documentation Weld 4.0.2.Final</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/3.1.8.Final/en-US/html_single/" target="_blank" rel="noopener">Documentation Weld 3.1.8.Final</a> &#93;
+                  &#91; <a href="https://issues.redhat.com/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12356277" target="_blank" rel="noopener">Release notes for Weld 4.0.2.Final</a> &#93;
+                  &#91; <a href="https://issues.redhat.com/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12356276" target="_blank" rel="noopener">Release notes for Weld 3.1.8.Final</a> &#93;</p>
+                  </div>
+                </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>
@@ -1035,102 +1100,6 @@ <h2 id="_wildfly_patch">WildFly Patch</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2019/11/28/weld-313Final/">Weld 3.1.3.Final</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2019-11-28
-                  &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.3.Final arrives along with Weld API 3.1.SP2.
-                  This is a minor update which had a main goal of swapping whole Weld internals from Java EE 8 to Jakarta EE 8.</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>API was transferred to Jakarta EE GAVs (<a href="https://issues.jboss.org/browse/WELD-2598" target="_blank" rel="noopener">WELD-2598</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Weld Core</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Core and whole testing was transferred to Jakarta EE GAvs (<a href="https://issues.jboss.org/browse/WELD-2598" target="_blank" rel="noopener">WELD-2598</a>)</p>
-                  </li>
-                  <li>
-                  <p>Properties inside <code>beans.xml</code> now support spec-descriptor-property-replacement on WildFly (<a href="https://issues.jboss.org/browse/WELD-2600" target="_blank" rel="noopener">WELD-2600</a>)</p>
-                  </li>
-                  <li>
-                  <p>Rolling updates delimiter is now correctly ignored for external bean archives (<a href="https://issues.jboss.org/browse/WELD-2596" target="_blank" rel="noopener">WELD-2596</a>)</p>
-                  </li>
-                  <li>
-                  <p>Allow for <code>private final</code> method in intercepted beans, these methods are then ignored during interception but Weld no longer blows up (<a href="https://issues.jboss.org/browse/WELD-2595" target="_blank" rel="noopener">WELD-2595</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Weld Servlet</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Adjust Jetty attributes accordingly to how they were renamed (<a href="https://issues.jboss.org/browse/WELD-2597" target="_blank" rel="noopener">WELD-2597</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Other</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Fix several misplaced licenses that were causing confusion (<a href="https://issues.jboss.org/browse/WELD-2599" target="_blank" rel="noopener">WELD-2599</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>This time around, the <a href="http://download.jboss.org/weld/3.1.3.Final/wildfly-18.0.1.Final-weld-3.1.3.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly 18.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.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=12342783" 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> <span class="skip">...</span><a href="/news/tags/release/page/6.html" class="page-link">6</a> <a href="/news/tags/release/page/7.html" class="page-link">7</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 2e58a9b8..af5215d6 100644
--- a/news/tags/release/page/4.html
+++ b/news/tags/release/page/4.html
@@ -141,6 +141,102 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2019/11/28/weld-313Final/">Weld 3.1.3.Final</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2019-11-28
+                  &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.3.Final arrives along with Weld API 3.1.SP2.
+                  This is a minor update which had a main goal of swapping whole Weld internals from Java EE 8 to Jakarta EE 8.</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>API was transferred to Jakarta EE GAVs (<a href="https://issues.jboss.org/browse/WELD-2598" target="_blank" rel="noopener">WELD-2598</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Weld Core</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Core and whole testing was transferred to Jakarta EE GAvs (<a href="https://issues.jboss.org/browse/WELD-2598" target="_blank" rel="noopener">WELD-2598</a>)</p>
+                  </li>
+                  <li>
+                  <p>Properties inside <code>beans.xml</code> now support spec-descriptor-property-replacement on WildFly (<a href="https://issues.jboss.org/browse/WELD-2600" target="_blank" rel="noopener">WELD-2600</a>)</p>
+                  </li>
+                  <li>
+                  <p>Rolling updates delimiter is now correctly ignored for external bean archives (<a href="https://issues.jboss.org/browse/WELD-2596" target="_blank" rel="noopener">WELD-2596</a>)</p>
+                  </li>
+                  <li>
+                  <p>Allow for <code>private final</code> method in intercepted beans, these methods are then ignored during interception but Weld no longer blows up (<a href="https://issues.jboss.org/browse/WELD-2595" target="_blank" rel="noopener">WELD-2595</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Weld Servlet</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Adjust Jetty attributes accordingly to how they were renamed (<a href="https://issues.jboss.org/browse/WELD-2597" target="_blank" rel="noopener">WELD-2597</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Other</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Fix several misplaced licenses that were causing confusion (<a href="https://issues.jboss.org/browse/WELD-2599" target="_blank" rel="noopener">WELD-2599</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>This time around, the <a href="http://download.jboss.org/weld/3.1.3.Final/wildfly-18.0.1.Final-weld-3.1.3.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly 18.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.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=12342783" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2019/08/06/weld-312Final/">Weld 3.1.2.Final</a>
@@ -1442,130 +1538,6 @@ <h2 id="_wildfly_patch">WildFly Patch</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2017/11/23/weld-302Final/">Weld 3.0.2.Final</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2017-11-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>Weld 3.0.2.Final is out and targetting WildFly 11!
-                  Ever wished you could select events and instances in a truly generic way using just <code>java.lang.reflect.Type</code>?
-                  Looking for easier way to configure SE container?
-                  We have a bunch of bugfixes and improvements for you, so read on&#8230;&#8203;</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>Fixed OSGi bundling, we missed out one package on last release (<a href="https://issues.jboss.org/browse/WELD-2421" target="_blank" rel="noopener">WELD-2421</a>)</p>
-                  </li>
-                  <li>
-                  <p>Improved behaviour with no-interface EJB view with non-public methods (<a href="https://issues.jboss.org/browse/WELD-2430" target="_blank" rel="noopener">WELD-2430</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>
-                  </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 a <code>String</code> key used to obtain interceptors binding from <code>InvocationContext</code> (<a href="https://issues.jboss.org/browse/WELD-2436" target="_blank" rel="noopener">WELD-2436</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Other</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Probe now correctly recognizes beans which have <code>@Priority</code> but aren&#8217;t alternatives (<a href="https://issues.jboss.org/browse/WELD-2432" target="_blank" rel="noopener">WELD-2432</a>)</p>
-                  </li>
-                  <li>
-                  <p>Multiple documentation improvements regarding all things, old and new (<a href="https://issues.jboss.org/browse/WELD-2440" target="_blank" rel="noopener">WELD-2440</a>, <a href="https://issues.jboss.org/browse/WELD-2431" target="_blank" rel="noopener">WELD-2431</a>, <a href="https://issues.jboss.org/browse/WELD-2434" target="_blank" rel="noopener">WELD-2434</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, there is a <a href="http://download.jboss.org/weld/3.0.2.Final/wildfly-11.0.0.Final-weld-3.0.2.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly 11.0.0.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.0.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=12335442" 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/7.html" class="page-link">7</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 add456ab..405dcb82 100644
--- a/news/tags/release/page/5.html
+++ b/news/tags/release/page/5.html
@@ -141,6 +141,130 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2017/11/23/weld-302Final/">Weld 3.0.2.Final</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2017-11-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>Weld 3.0.2.Final is out and targetting WildFly 11!
+                  Ever wished you could select events and instances in a truly generic way using just <code>java.lang.reflect.Type</code>?
+                  Looking for easier way to configure SE container?
+                  We have a bunch of bugfixes and improvements for you, so read on&#8230;&#8203;</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>Fixed OSGi bundling, we missed out one package on last release (<a href="https://issues.jboss.org/browse/WELD-2421" target="_blank" rel="noopener">WELD-2421</a>)</p>
+                  </li>
+                  <li>
+                  <p>Improved behaviour with no-interface EJB view with non-public methods (<a href="https://issues.jboss.org/browse/WELD-2430" target="_blank" rel="noopener">WELD-2430</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>
+                  </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 a <code>String</code> key used to obtain interceptors binding from <code>InvocationContext</code> (<a href="https://issues.jboss.org/browse/WELD-2436" target="_blank" rel="noopener">WELD-2436</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Other</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Probe now correctly recognizes beans which have <code>@Priority</code> but aren&#8217;t alternatives (<a href="https://issues.jboss.org/browse/WELD-2432" target="_blank" rel="noopener">WELD-2432</a>)</p>
+                  </li>
+                  <li>
+                  <p>Multiple documentation improvements regarding all things, old and new (<a href="https://issues.jboss.org/browse/WELD-2440" target="_blank" rel="noopener">WELD-2440</a>, <a href="https://issues.jboss.org/browse/WELD-2431" target="_blank" rel="noopener">WELD-2431</a>, <a href="https://issues.jboss.org/browse/WELD-2434" target="_blank" rel="noopener">WELD-2434</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, there is a <a href="http://download.jboss.org/weld/3.0.2.Final/wildfly-11.0.0.Final-weld-3.0.2.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly 11.0.0.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.0.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=12335442" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2017/09/11/weld-245Final/">Weld 2.4.5.Final</a>
@@ -1075,85 +1199,6 @@ <h2 id="_wildfly_patch">WildFly Patch</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2016/11/18/weld-241Final/">Weld 2.4.1.Final</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2016-11-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>The development of <strong>Weld 3</strong> (CDI 2) is underway.
-                  However, we don&#8217;t forget about the maintenance of the stable branch of Weld!
-                  So I am very pleased to announce the first bugfix 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=12331553" target="_blank" rel="noopener">the release details</a>.
-                  Thanks to everyone involved in this release!</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Notable fixes and improvements:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>removed false positive warning about Jandex version used (<a href="https://issues.jboss.org/browse/WELD-2231" target="_blank" rel="noopener">WELD-2231</a>)</p>
-                  </li>
-                  <li>
-                  <p>fixed Groovy support - only filter out relevant methods from Groovy objects when generating bean proxies (<a href="https://issues.jboss.org/browse/WELD-2255" target="_blank" rel="noopener">WELD-2255</a>)</p>
-                  </li>
-                  <li>
-                  <p>optimized proxy class generation for "large classes" (<a href="https://issues.jboss.org/browse/WELD-2244" target="_blank" rel="noopener">WELD-2244</a>)</p>
-                  </li>
-                  <li>
-                  <p>improved the way Weld configuration info is logged (<a href="https://issues.jboss.org/browse/WELD-2238" target="_blank" rel="noopener">WELD-2238</a>)</p>
-                  </li>
-                  <li>
-                  <p>Weld SE</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>added support for nested directories in uber jars, e.g. Spring Boot jar (<a href="https://issues.jboss.org/browse/WELD-2254" target="_blank" rel="noopener">WELD-2254</a>)</p>
-                  </li>
-                  <li>
-                  <p>allow to use <code>CDI.getBeanManager()</code> after <code>BeforeBeanDiscovery</code> is fired (<a href="https://issues.jboss.org/browse/WELD-2256" target="_blank" rel="noopener">WELD-2256</a>)</p>
-                  </li>
-                  <li>
-                  <p>don&#8217;t abort container initialization if <code>JandexClassFileServices</code> is unable to load an annotation (<a href="https://issues.jboss.org/browse/WELD-2232" target="_blank" rel="noopener">WELD-2232</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Weld Servlet - document the usage of <code>org.jboss.weld.environment.container.class</code> init param (<a href="https://issues.jboss.org/browse/WELD-2236" target="_blank" rel="noopener">WELD-2236</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.4.1.Final/wildfly-10.1.0.Final-weld-2.4.1.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 <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.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=12331553" 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/7.html" class="page-link">7</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 dd80b5ac..b8da3646 100644
--- a/news/tags/release/page/6.html
+++ b/news/tags/release/page/6.html
@@ -141,6 +141,85 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2016/11/18/weld-241Final/">Weld 2.4.1.Final</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2016-11-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>The development of <strong>Weld 3</strong> (CDI 2) is underway.
+                  However, we don&#8217;t forget about the maintenance of the stable branch of Weld!
+                  So I am very pleased to announce the first bugfix 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=12331553" target="_blank" rel="noopener">the release details</a>.
+                  Thanks to everyone involved in this release!</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Notable fixes and improvements:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>removed false positive warning about Jandex version used (<a href="https://issues.jboss.org/browse/WELD-2231" target="_blank" rel="noopener">WELD-2231</a>)</p>
+                  </li>
+                  <li>
+                  <p>fixed Groovy support - only filter out relevant methods from Groovy objects when generating bean proxies (<a href="https://issues.jboss.org/browse/WELD-2255" target="_blank" rel="noopener">WELD-2255</a>)</p>
+                  </li>
+                  <li>
+                  <p>optimized proxy class generation for "large classes" (<a href="https://issues.jboss.org/browse/WELD-2244" target="_blank" rel="noopener">WELD-2244</a>)</p>
+                  </li>
+                  <li>
+                  <p>improved the way Weld configuration info is logged (<a href="https://issues.jboss.org/browse/WELD-2238" target="_blank" rel="noopener">WELD-2238</a>)</p>
+                  </li>
+                  <li>
+                  <p>Weld SE</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>added support for nested directories in uber jars, e.g. Spring Boot jar (<a href="https://issues.jboss.org/browse/WELD-2254" target="_blank" rel="noopener">WELD-2254</a>)</p>
+                  </li>
+                  <li>
+                  <p>allow to use <code>CDI.getBeanManager()</code> after <code>BeforeBeanDiscovery</code> is fired (<a href="https://issues.jboss.org/browse/WELD-2256" target="_blank" rel="noopener">WELD-2256</a>)</p>
+                  </li>
+                  <li>
+                  <p>don&#8217;t abort container initialization if <code>JandexClassFileServices</code> is unable to load an annotation (<a href="https://issues.jboss.org/browse/WELD-2232" target="_blank" rel="noopener">WELD-2232</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Weld Servlet - document the usage of <code>org.jboss.weld.environment.container.class</code> init param (<a href="https://issues.jboss.org/browse/WELD-2236" target="_blank" rel="noopener">WELD-2236</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.4.1.Final/wildfly-10.1.0.Final-weld-2.4.1.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 <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.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=12331553" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2016/09/13/weld-240Final/">Weld 2.4.0.Final</a>
@@ -1027,67 +1106,6 @@ <h2 id="_wildfly_patch">WildFly Patch</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2015/10/27/weld-231Final/">Weld 2.3.1.Final arrives...</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2015-10-27
-                  &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.1.Final has been released! The delivery: a few killed bugs, couple of Weld SE enhancements and several Weld Probe improvements.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Notable bug-fixes and enhancements:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Private producer, disposer and observer methods should be intercepted (<a href="https://issues.jboss.org/browse/WELD-2043">WELD-2043</a>)</p>
-                  </li>
-                  <li>
-                  <p>Specializing bean - remove @Default qualifier unless explicitly declared (<a href="https://issues.jboss.org/browse/WELD-2043">WELD-2046</a>)</p>
-                  </li>
-                  <li>
-                  <p>Weld SE</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Fix the development mode enablement</p>
-                  </li>
-                  <li>
-                  <p>Allow to pass a ResourceLoader to be used for scanning (<a href="https://issues.jboss.org/browse/WELD-2043">WELD-2044</a>)</p>
-                  </li>
-                  <li>
-                  <p>Allow to skip the registration of a shutdown hook (<a href="https://issues.jboss.org/browse/WELD-2043">WELD-2051</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Weld Probe now supports monitoring of container lifecycle events during bootstrap (see also <a href="http://docs.jboss.org/weld/reference/latest/html/configure.html#config-dev-mode">supported configuration properties</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.1.Final/en-US/html/">Documentation</a> &#93;
-                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12327517">Release notes</a> &#93;</p>
-                  </div>
-                </div>
-                <hr>
-              </div>
               <div class="pagination-links"><a href="/news/tags/release/page/5.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/5.html" class="page-link">5</a> <span class="current-page">6</span> <a href="/news/tags/release/page/7.html" class="page-link">7</a> <a href="/news/tags/release/page/7.html" class="next-link">Next</a> </div>
               <hr>
               <div>
diff --git a/news/tags/release/page/7.html b/news/tags/release/page/7.html
index cef02cc8..d094e401 100644
--- a/news/tags/release/page/7.html
+++ b/news/tags/release/page/7.html
@@ -141,6 +141,67 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2015/10/27/weld-231Final/">Weld 2.3.1.Final arrives...</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2015-10-27
+                  &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.1.Final has been released! The delivery: a few killed bugs, couple of Weld SE enhancements and several Weld Probe improvements.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Notable bug-fixes and enhancements:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Private producer, disposer and observer methods should be intercepted (<a href="https://issues.jboss.org/browse/WELD-2043">WELD-2043</a>)</p>
+                  </li>
+                  <li>
+                  <p>Specializing bean - remove @Default qualifier unless explicitly declared (<a href="https://issues.jboss.org/browse/WELD-2043">WELD-2046</a>)</p>
+                  </li>
+                  <li>
+                  <p>Weld SE</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Fix the development mode enablement</p>
+                  </li>
+                  <li>
+                  <p>Allow to pass a ResourceLoader to be used for scanning (<a href="https://issues.jboss.org/browse/WELD-2043">WELD-2044</a>)</p>
+                  </li>
+                  <li>
+                  <p>Allow to skip the registration of a shutdown hook (<a href="https://issues.jboss.org/browse/WELD-2043">WELD-2051</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Weld Probe now supports monitoring of container lifecycle events during bootstrap (see also <a href="http://docs.jboss.org/weld/reference/latest/html/configure.html#config-dev-mode">supported configuration properties</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.1.Final/en-US/html/">Documentation</a> &#93;
+                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12327517">Release notes</a> &#93;</p>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2015/09/18/weld-230Final/">Weld 2.3.0.Final released!</a>
diff --git a/sitemap.xml b/sitemap.xml
index 9706360a..6386dbc0 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>2024-11-28</lastmod>
+    <lastmod>2024-12-16</lastmod>
     <priority>0.5</priority>
     <changefreq>weekly</changefreq>
   </url>
   <url>
     <loc>https://weld.cdi-spec.org/community/</loc>
-    <lastmod>2024-11-28</lastmod>
+    <lastmod>2024-12-16</lastmod>
     <priority>0.5</priority>
     <changefreq>weekly</changefreq>
   </url>
   <url>
     <loc>https://weld.cdi-spec.org/dist/</loc>
-    <lastmod>2024-11-28</lastmod>
+    <lastmod>2024-12-16</lastmod>
     <priority>1</priority>
     <changefreq>daily</changefreq>
   </url>
   <url>
     <loc>https://weld.cdi-spec.org/documentation/</loc>
-    <lastmod>2024-11-28</lastmod>
+    <lastmod>2024-12-16</lastmod>
     <priority>0.5</priority>
     <changefreq>weekly</changefreq>
   </url>
   <url>
     <loc>https://weld.cdi-spec.org/download/</loc>
-    <lastmod>2024-11-28</lastmod>
+    <lastmod>2024-12-16</lastmod>
     <priority>0.5</priority>
     <changefreq>weekly</changefreq>
   </url>
   <url>
     <loc>https://weld.cdi-spec.org/</loc>
-    <lastmod>2024-11-28</lastmod>
+    <lastmod>2024-12-16</lastmod>
     <priority>0.5</priority>
     <changefreq>weekly</changefreq>
   </url>
@@ -600,9 +600,15 @@
     <priority>1</priority>
     <changefreq>weekly</changefreq>
   </url>
+  <url>
+    <loc>https://weld.cdi-spec.org/news/2024/12/16/weld-514Final/</loc>
+    <lastmod>2024-12-16</lastmod>
+    <priority>1</priority>
+    <changefreq>weekly</changefreq>
+  </url>
   <url>
     <loc>https://weld.cdi-spec.org/news/</loc>
-    <lastmod>2024-11-28</lastmod>
+    <lastmod>2024-12-16</lastmod>
     <priority>1</priority>
     <changefreq>daily</changefreq>
   </url>