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

---
 dist/index.html                          |  23 ++
 download/index.html                      |  48 +--
 index.html                               |  28 +-
 news.atom                                | 295 ++++++----------
 news/2024/12/16/weld-600Final/index.html | 242 +++++++++++++
 news/index.html                          | 163 +++------
 news/page/10.html                        | 246 +++++++------
 news/page/11.html                        | 196 ++++++-----
 news/page/12.html                        | 172 ++++-----
 news/page/13.html                        | 184 +++++-----
 news/page/14.html                        | 154 +++++---
 news/page/15.html                        | 189 +++-------
 news/page/16.html                        | 319 +++++++----------
 news/page/17.html                        | 371 ++++++++++---------
 news/page/18.html                        | 212 +++++++++--
 news/page/19.html                        |  62 ++--
 news/page/2.html                         | 163 ++++++---
 news/page/20.html                        | 224 ++++++++++++
 news/page/3.html                         |  90 +++--
 news/page/4.html                         | 347 ++----------------
 news/page/5.html                         | 430 ++++++++++++++++-------
 news/page/6.html                         | 212 ++++++-----
 news/page/7.html                         | 196 +++++------
 news/page/8.html                         | 206 +++++------
 news/page/9.html                         | 240 ++++++-------
 news/tags/release/index.html             | 104 +++---
 news/tags/release/page/2.html            | 361 +++----------------
 news/tags/release/page/3.html            | 400 ++++++++++++++++-----
 news/tags/release/page/4.html            | 221 +++++-------
 news/tags/release/page/5.html            | 217 +++++++-----
 news/tags/release/page/6.html            | 129 ++++---
 news/tags/release/page/7.html            |  42 +++
 sitemap.xml                              |   6 +
 33 files changed, 3497 insertions(+), 2995 deletions(-)
 create mode 100644 news/2024/12/16/weld-600Final/index.html
 create mode 100644 news/page/20.html

diff --git a/dist/index.html b/dist/index.html
index bc699659..52929fa3 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">
+                    6.0.0.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=12439250">
+                      Changelog
+                    </a>
+                  </td>
+                  <td>
+                    <a href="http://download.jboss.org/weld/6.0.0.Final">
+                      Download
+                    </a>
+                  </td>
+                </tr>
                 <tr>
                   <td class="version">
                     5.1.4.Final
diff --git a/download/index.html b/download/index.html
index a233558c..161631ba 100644
--- a/download/index.html
+++ b/download/index.html
@@ -207,6 +207,30 @@ <h2>Binary distribution</h2>
                     Download
                   </th>
                 </tr>
+                <tr>
+                  <td class="version">
+                    6.0.0.Final
+                  </td>
+                  <td>
+                    Final
+                  </td>
+                  <td>
+                    4.1
+                  </td>
+                  <td>
+                    16.12.2024
+                  </td>
+                  <td>
+                    <a href="https://issues.redhat.com/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12439250">
+                      Changelog
+                    </a>
+                  </td>
+                  <td>
+                    <a href="https://download.jboss.org/weld/6.0.0.Final">
+                      Download
+                    </a>
+                  </td>
+                </tr>
                 <tr>
                   <td class="version">
                     5.1.4.Final
@@ -429,30 +453,6 @@ <h2>Binary distribution</h2>
                     </a>
                   </td>
                 </tr>
-                <tr>
-                  <td class="version">
-                    5.1.1.SP1
-                  </td>
-                  <td>
-                    Final
-                  </td>
-                  <td>
-                    4.0
-                  </td>
-                  <td>
-                    11.07.2023
-                  </td>
-                  <td>
-                    <a href="https://issues.redhat.com/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12410330">
-                      Changelog
-                    </a>
-                  </td>
-                  <td>
-                    <a href="https://download.jboss.org/weld/5.1.1.SP1">
-                      Download
-                    </a>
-                  </td>
-                </tr>
               </table>
               <p></p>
               <a href="/dist">
diff --git a/index.html b/index.html
index 8d7a14d4..ef06d33a 100644
--- a/index.html
+++ b/index.html
@@ -549,7 +549,7 @@ <h2>
                     <ul class="newsColumn">
                       <li>
                         <h3>
-                          <a href="/news/2024/12/16/weld-514Final/">Weld 5.1.4.Final</a>
+                          <a href="/news/2024/12/16/weld-600Final/">Weld 6.0.0.Final</a>
                         </h3>
                         <div class="news-date news-boxed">
                           2024-12-16
@@ -560,16 +560,16 @@ <h3>
                           </span>
                         </div>
                         <p>
-                          Tiny update for Weld 5.1
+                          Weld 6.0.0.Final released
                         </p>
                         <hr>
                       </li>
                       <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>
@@ -577,16 +577,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>
@@ -594,16 +594,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>
@@ -611,16 +611,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>
@@ -628,7 +628,7 @@ <h3>
                           </span>
                         </div>
                         <p>
-                          Weld 6.0.0.Beta4 is now available
+                          Squashing bugs with Weld 5.1.3.Final!
                         </p>
                         <hr>
                       </li>
diff --git a/news.atom b/news.atom
index 1e5a829d..386e4fa4 100644
--- a/news.atom
+++ b/news.atom
@@ -2,13 +2,80 @@
 <feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
   <id>https://weld.cdi-spec.org/</id>
   <title>Weld</title>
-  <updated>2024-12-16T11:18:04+00:00</updated>
+  <updated>2024-12-16T14:16:37+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-600Final/</id>
+    <title>Weld 6.0.0.Final</title>
+    <updated>2024-12-16T14:16:37+00:00</updated>
+    <published>2024-12-16T00:00:00+00:00</published>
+    <link href="https://weld.cdi-spec.org/news/2024/12/16/weld-600Final/" rel="alternate" type="text/html" />
+    <author>
+      <name>Matej Novotny</name>
+    </author>
+    <category term="release"></category>
+    <summary>
+      Since there have been no further bugs reported, Weld 6.0.0.CR2 has evolved into its Final form.
+      Say hello to Weld API 6.0.Final as well as Weld Core 6.0.0.Final!
+      
+      
+      Since there are no changes from the previous CR2 version, early adopters shouldn&#8217;t encounter any unwelcome surprises.
+      
+      
+      Nonetheless, should you run into any bugs, do get in touch so that we can squash them as soon as possible!
+      
+      
+      And speaking of getting in touch, we recognize that JIRA can be a little daunting, so we are trying to make that easier by enabling GitHub discussions.
+      You can now ask your question in:
+      
+      
+      
+      
+      Weld Core GH discussions
+      
+      
+      Weld API GH...
+    </summary>
+    <content type="html">
+      &lt;div class=&quot;paragraph&quot;&gt;
+      &lt;p&gt;Since there have been no further bugs reported, Weld &lt;code&gt;6.0.0.CR2&lt;/code&gt; has evolved into its &lt;code&gt;Final&lt;/code&gt; form.
+      Say hello to &lt;code&gt;Weld API 6.0.Final&lt;/code&gt; as well as &lt;code&gt;Weld Core 6.0.0.Final&lt;/code&gt;!&lt;/p&gt;
+      &lt;/div&gt;
+      &lt;div class=&quot;paragraph&quot;&gt;
+      &lt;p&gt;Since there are no changes from the previous &lt;code&gt;CR2&lt;/code&gt; version, early adopters shouldn’t encounter any unwelcome surprises.&lt;/p&gt;
+      &lt;/div&gt;
+      &lt;div class=&quot;paragraph&quot;&gt;
+      &lt;p&gt;Nonetheless, should you run into any bugs, do get in touch so that we can squash them as soon as possible!&lt;/p&gt;
+      &lt;/div&gt;
+      &lt;div class=&quot;paragraph&quot;&gt;
+      &lt;p&gt;And speaking of getting in touch, we recognize that JIRA can be a little daunting, so we are trying to make that easier by &lt;strong&gt;enabling GitHub discussions&lt;/strong&gt;.
+      You can now ask your question in:&lt;/p&gt;
+      &lt;/div&gt;
+      &lt;div class=&quot;ulist&quot;&gt;
+      &lt;ul&gt;
+      &lt;li&gt;
+      &lt;p&gt;&lt;a href=&quot;https://github.com/weld/core/discussions&quot;&gt;Weld Core&lt;/a&gt; GH discussions&lt;/p&gt;
+      &lt;/li&gt;
+      &lt;li&gt;
+      &lt;p&gt;&lt;a href=&quot;https://github.com/weld/api/discussions&quot;&gt;Weld API&lt;/a&gt; GH discussions&lt;/p&gt;
+      &lt;/li&gt;
+      &lt;/ul&gt;
+      &lt;/div&gt;
+      &lt;div class=&quot;paragraph&quot;&gt;
+      &lt;p&gt;And don’t you worry, the &lt;code&gt;weld-dev&lt;/code&gt; mailing list is still kicking plus, for the time being, we are still using JIRA for per-release issue tracking.&lt;/p&gt;
+      &lt;/div&gt;
+      &lt;div class=&quot;paragraph&quot;&gt;
+      &lt;p&gt;[ &lt;a href=&quot;https://weld.cdi-spec.org/download/&quot;&gt;Download&lt;/a&gt; ]
+      [ &lt;a href=&quot;http://docs.jboss.org/weld/reference/6.0.0.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=12439250&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/12/16/weld-514Final/</id>
     <title>Weld 5.1.4.Final</title>
-    <updated>2024-12-16T11:18:04+00:00</updated>
+    <updated>2024-12-16T13:23:47+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>
@@ -89,7 +156,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2024/11/28/weld-600CR2/</id>
     <title>Weld 6.0.0.CR2</title>
-    <updated>2024-11-28T11:46:35+00:00</updated>
+    <updated>2024-12-16T13:23:47+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>
@@ -152,7 +219,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-28T11:46:27+00:00</updated>
+    <updated>2024-12-16T13:23:47+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>
@@ -250,7 +317,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-28T11:46:27+00:00</updated>
+    <updated>2024-12-16T13:23:47+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>
@@ -351,7 +418,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-28T11:46:27+00:00</updated>
+    <updated>2024-12-16T13:23:47+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>
@@ -468,7 +535,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-28T11:46:27+00:00</updated>
+    <updated>2024-12-16T13:23:47+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>
@@ -589,7 +656,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-28T11:46:27+00:00</updated>
+    <updated>2024-12-16T13:23:47+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>
@@ -726,7 +793,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-28T11:46:27+00:00</updated>
+    <updated>2024-12-16T13:23:47+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>
@@ -814,7 +881,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-28T11:46:27+00:00</updated>
+    <updated>2024-12-16T13:23:47+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>
@@ -857,7 +924,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-28T11:46:27+00:00</updated>
+    <updated>2024-12-16T13:23:47+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>
@@ -921,7 +988,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-28T11:46:27+00:00</updated>
+    <updated>2024-12-16T13:23:47+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>
@@ -1010,7 +1077,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-28T11:46:27+00:00</updated>
+    <updated>2024-12-16T13:23:47+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>
@@ -1102,7 +1169,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-28T11:46:27+00:00</updated>
+    <updated>2024-12-16T13:23:47+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>
@@ -1177,7 +1244,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-28T11:46:27+00:00</updated>
+    <updated>2024-12-16T13:23:47+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>
@@ -1222,7 +1289,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-28T11:46:27+00:00</updated>
+    <updated>2024-12-16T13:23:47+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>
@@ -1267,7 +1334,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-28T11:46:27+00:00</updated>
+    <updated>2024-12-16T13:23:47+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>
@@ -1350,7 +1417,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-28T11:46:27+00:00</updated>
+    <updated>2024-12-16T13:23:47+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>
@@ -1390,7 +1457,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-28T11:46:27+00:00</updated>
+    <updated>2024-12-16T13:23:47+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>
@@ -1459,7 +1526,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-28T11:46:27+00:00</updated>
+    <updated>2024-12-16T13:23:47+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>
@@ -1556,7 +1623,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-28T11:46:27+00:00</updated>
+    <updated>2024-12-16T13:23:47+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>
@@ -1867,7 +1934,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-28T11:46:27+00:00</updated>
+    <updated>2024-12-16T13:23:47+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>
@@ -1948,7 +2015,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-28T11:46:27+00:00</updated>
+    <updated>2024-12-16T13:23:47+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>
@@ -2028,7 +2095,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-28T11:46:27+00:00</updated>
+    <updated>2024-12-16T13:23:47+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>
@@ -2147,7 +2214,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-28T11:46:27+00:00</updated>
+    <updated>2024-12-16T13:23:47+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>
@@ -2261,7 +2328,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-28T11:46:27+00:00</updated>
+    <updated>2024-12-16T13:23:47+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>
@@ -2419,7 +2486,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-28T11:46:27+00:00</updated>
+    <updated>2024-12-16T13:23:47+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>
@@ -2497,7 +2564,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-28T11:46:27+00:00</updated>
+    <updated>2024-12-16T13:23:47+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>
@@ -2614,7 +2681,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-28T11:46:27+00:00</updated>
+    <updated>2024-12-16T13:23:47+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>
@@ -2752,7 +2819,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-28T11:46:27+00:00</updated>
+    <updated>2024-12-16T13:23:47+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>
@@ -2891,7 +2958,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-28T11:46:27+00:00</updated>
+    <updated>2024-12-16T13:23:47+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>
@@ -3003,7 +3070,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-28T11:46:27+00:00</updated>
+    <updated>2024-12-16T13:23:47+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>
@@ -3137,7 +3204,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-28T11:46:27+00:00</updated>
+    <updated>2024-12-16T13:23:47+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>
@@ -3291,7 +3358,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-28T11:46:27+00:00</updated>
+    <updated>2024-12-16T13:23:47+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>
@@ -3424,7 +3491,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-28T11:46:27+00:00</updated>
+    <updated>2024-12-16T13:23:47+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>
@@ -3676,7 +3743,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-28T11:46:27+00:00</updated>
+    <updated>2024-12-16T13:23:47+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>
@@ -3813,7 +3880,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-28T11:46:27+00:00</updated>
+    <updated>2024-12-16T13:23:47+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>
@@ -3977,7 +4044,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2018/07/10/weld-team-changes/</id>
     <title>Weld team changes</title>
-    <updated>2024-11-28T11:46:27+00:00</updated>
+    <updated>2024-12-16T13:23:47+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>
@@ -4026,7 +4093,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-28T11:46:27+00:00</updated>
+    <updated>2024-12-16T13:23:47+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>
@@ -4225,7 +4292,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-28T11:46:27+00:00</updated>
+    <updated>2024-12-16T13:23:47+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>
@@ -4408,7 +4475,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-28T11:46:27+00:00</updated>
+    <updated>2024-12-16T13:23:47+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>
@@ -4543,7 +4610,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-28T11:46:27+00:00</updated>
+    <updated>2024-12-16T13:23:47+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>
@@ -4720,7 +4787,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-28T11:46:27+00:00</updated>
+    <updated>2024-12-16T13:23:47+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>
@@ -4899,7 +4966,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-28T11:46:27+00:00</updated>
+    <updated>2024-12-16T13:23:47+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>
@@ -5074,7 +5141,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-28T11:46:27+00:00</updated>
+    <updated>2024-12-16T13:23:47+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>
@@ -5191,7 +5258,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-28T11:46:27+00:00</updated>
+    <updated>2024-12-16T13:23:47+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>
@@ -5342,7 +5409,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-28T11:46:27+00:00</updated>
+    <updated>2024-12-16T13:23:47+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>
@@ -5601,7 +5668,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-28T11:46:27+00:00</updated>
+    <updated>2024-12-16T13:23:47+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>
@@ -5753,7 +5820,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-28T11:46:27+00:00</updated>
+    <updated>2024-12-16T13:23:47+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>
@@ -6071,7 +6138,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-28T11:46:27+00:00</updated>
+    <updated>2024-12-16T13:23:47+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>
@@ -6246,132 +6313,4 @@
       &lt;/div&gt;
     </content>
   </entry>
-  <entry>
-    <id>https://weld.cdi-spec.org/news/2017/04/07/weld-243Final/</id>
-    <title>Weld 2.4.3.Final</title>
-    <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>
-      <name>Matej Novotny</name>
-    </author>
-    <category term="release"></category>
-    <summary>
-      Even as we get ever closer to CDI 2.0 final version, we shan&#8217;t forget about our stable 2.4 branch.
-      Ladies and gentlemen, here comes the next-in-line 2.4 release - Weld 2.4.3.Final!
-      
-      
-      Notable fixes and improvements:
-      
-      
-      
-      
-      Weld now shares proxy classes for built-in beans of the same type (WELD-2344)
-      
-      
-      Fixed usage of Jandex on Tomcat when using unpackWars=false (WELD-2357)
-      
-      
-      Weld now supports wider variety of non-portable extension observer methods (WELD-2338)
-      
-      
-      There is now new debug level logging during bootstrap which allows to monitor name, start, end and duration of all bootstrap phases (WELD-2336)
-      
-      
-      Session replication
-      
-      
-      
-      Built-in session and conversation scoped beans are not part of the bean identifier index...
-    </summary>
-    <content type="html">
-      &lt;div class=&quot;paragraph&quot;&gt;
-      &lt;p&gt;Even as we get ever closer to CDI 2.0 final version, we shan’t forget about our stable 2.4 branch.
-      Ladies and gentlemen, here comes the next-in-line 2.4 release - Weld 2.4.3.Final!&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;Weld now shares proxy classes for built-in beans of the same type (&lt;a href=&quot;https://issues.jboss.org/browse/WELD-2344&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;WELD-2344&lt;/a&gt;)&lt;/p&gt;
-      &lt;/li&gt;
-      &lt;li&gt;
-      &lt;p&gt;Fixed usage of Jandex on Tomcat when using &lt;code&gt;unpackWars=false&lt;/code&gt; (&lt;a href=&quot;https://issues.jboss.org/browse/WELD-2357&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;WELD-2357&lt;/a&gt;)&lt;/p&gt;
-      &lt;/li&gt;
-      &lt;li&gt;
-      &lt;p&gt;Weld now supports wider variety of non-portable extension observer methods (&lt;a href=&quot;https://issues.jboss.org/browse/WELD-2338&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;WELD-2338&lt;/a&gt;)&lt;/p&gt;
-      &lt;/li&gt;
-      &lt;li&gt;
-      &lt;p&gt;There is now new debug level logging during bootstrap which allows to monitor name, start, end and duration of all bootstrap phases (&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;Session replication&lt;/p&gt;
-      &lt;div class=&quot;ulist&quot;&gt;
-      &lt;ul&gt;
-      &lt;li&gt;
-      &lt;p&gt;Built-in session and conversation scoped beans are not part of the bean identifier index anymore (&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;Handle situation when &lt;code&gt;HTTPSessionBean&lt;/code&gt; might not be serializable (&lt;a href=&quot;https://issues.jboss.org/browse/WELD-2346&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;WELD-2346&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;/p&gt;
-      &lt;div class=&quot;ulist&quot;&gt;
-      &lt;ul&gt;
-      &lt;li&gt;
-      &lt;p&gt;You can now easily register new &lt;code&gt;org.jboss.weld.bootstrap.api.Service&lt;/code&gt; during container bootstrap (&lt;a href=&quot;https://issues.jboss.org/browse/WELD-2360&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;WELD-2360&lt;/a&gt;)&lt;/p&gt;
-      &lt;/li&gt;
-      &lt;li&gt;
-      &lt;p&gt;Any &lt;code&gt;javax.enterprise.inject.spi.CDI&lt;/code&gt; method can now be called during &lt;code&gt;AfterDeploymentValidation&lt;/code&gt; (&lt;a href=&quot;https://issues.jboss.org/browse/WELD-2371&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;WELD-2371&lt;/a&gt;)&lt;/p&gt;
-      &lt;/li&gt;
-      &lt;li&gt;
-      &lt;p&gt;&lt;code&gt;ContainerInitialized&lt;/code&gt; event is now correctly fired after registration of shutdown hook (&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;&lt;code&gt;ContainerInitialized&lt;/code&gt; and &lt;code&gt;ContainerShutdown&lt;/code&gt; now implement &lt;code&gt;toString()&lt;/code&gt; (&lt;a href=&quot;https://issues.jboss.org/browse/WELD-2354&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;WELD-2354&lt;/a&gt;)&lt;/p&gt;
-      &lt;/li&gt;
-      &lt;/ul&gt;
-      &lt;/div&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;Allow monitoring of bean instance creation using &lt;code&gt;AroundConstruct&lt;/code&gt; (&lt;a href=&quot;https://issues.jboss.org/browse/WELD-2332&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;WELD-2332&lt;/a&gt;)&lt;/p&gt;
-      &lt;/li&gt;
-      &lt;li&gt;
-      &lt;p&gt;Fixed a situation when bean was wrongly marked as unused when injected as parameter (&lt;a href=&quot;https://issues.jboss.org/browse/WELD-2342&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;WELD-2342&lt;/a&gt;)&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=12333607&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/2.4.3.Final/wildfly-10.1.0.Final-weld-2.4.3.Final-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/2.4.3.Final/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=12333607&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-600Final/index.html b/news/2024/12/16/weld-600Final/index.html
new file mode 100644
index 00000000..5e152028
--- /dev/null
+++ b/news/2024/12/16/weld-600Final/index.html
@@ -0,0 +1,242 @@
+<!DOCTYPE html>
+<html>
+  <head>
+    <meta charset="utf-8">
+    <title>
+      Weld: Weld 6.0.0.Final
+    </title>
+    <meta content="width=device-width, initial-scale=1.0" name="viewport">
+    <meta content="Weld 6.0.0.Final released" name="description">
+    <link href="/images/weld_icon_32x.ico" rel="shortcut icon" type="image/x-icon">
+    <link href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.5/css/bootstrap.min.css" rel="stylesheet" type="text/css">
+    <link href="https://maxcdn.bootstrapcdn.com/font-awesome/4.4.0/css/font-awesome.min.css" rel="stylesheet" type="text/css">
+    <link href="//static.jboss.org/css/tabzilla.css" media="screen" rel="stylesheet" type="text/css">
+    <link href="https://weld.cdi-spec.org/stylesheets/styles.css" rel="stylesheet" type="text/css">
+    <script src="//static.jboss.org/theme/js/libs/jquery/jquery-1.9.1.min.js" type="text/javascript"></script>
+    <script src="//static.jboss.org/js/_jbossorg-tabzilla.js" type="text/javascript"></script>
+    <!--[if lt IE 9]>
+      <script src="//html5shim.googlecode.com/svn/trunk/html5.js" type="text/javascript"></script>
+    <![endif]-->
+    <link href="https://weld.cdi-spec.org/news.atom" rel="alternate" type="application/atom+xml">
+    <link href="//cdn.jsdelivr.net/highlight.js/8.9.1/styles/hybrid.min.css" rel="stylesheet">
+    <script src="//cdn.jsdelivr.net/highlight.js/8.9.1/highlight.min.js" type="text/javascript"></script>
+    <script>
+      hljs.initHighlightingOnLoad();
+    </script>
+  </head>
+  <body>
+    <div class="container-fluid">
+      <div class="row">
+        <div class="col-md-2 col-sm-3">
+          <div class="sidebar-nav">
+            <div class="navbar navbar-default" role="navigation">
+              <div class="navbar-header">
+                <button ="button" class="navbar-toggle" data-target=".sidebar-navbar-collapse" data-toggle="collapse">
+                  <span class="sr-only">
+                    Toggle navigation
+                  </span>
+                  <span class="icon-bar"></span>
+                  <span class="icon-bar"></span>
+                  <span class="icon-bar"></span>
+                  <span class="icon-bar"></span>
+                </button>
+                <a ="#" class="visible-xs navbar-brand">
+                  <img alt="Weld Logo" src="/images/weld_logo_100x.png">
+                </a>
+              </div>
+              <div class="collapse navbar-collapse sidebar-navbar-collapse">
+                <ul class="nav navbar-nav">
+                  <li>
+                    <a href="/">
+                      <i class="fa fa-home"></i>
+                      &nbsp;Home
+                    </a>
+                  </li>
+                  <li>
+                    <a href="/download">
+                      <i class="fa fa-download"></i>
+                      &nbsp;Download
+                    </a>
+                  </li>
+                  <li>
+                    <a href="/news">
+                      <i class="fa fa-newspaper-o"></i>
+                      &nbsp;News
+                    </a>
+                  </li>
+                  <li>
+                    <a href="https://issues.jboss.org/projects/WELD?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page" target="_blank">
+                      <i class="fa fa-road"></i>
+                      &nbsp;Road Map
+                    </a>
+                  </li>
+                  <li>
+                    <a href="/documentation">
+                      <i class="fa fa-book"></i>
+                      &nbsp;Docs &amp; FAQ
+                    </a>
+                  </li>
+                  <li>
+                    <a href="/news/tags/tips">
+                      <i class="fa fa-lightbulb-o"></i>
+                      &nbsp;Tips and Tricks
+                    </a>
+                  </li>
+                  <li>
+                    <a href="/community">
+                      <i class="fa fa-group"></i>
+                      &nbsp;Community
+                    </a>
+                  </li>
+                  <li>
+                    <a href="http://github.com/weld" target="_blank">
+                      <i class="fa fa-github-alt"></i>
+                      &nbsp;Source Code
+                    </a>
+                  </li>
+                  <li>
+                    <a href="https://issues.jboss.org/browse/WELD#selectedTab=com.atlassian.jira.plugin.system.project%3Asummary-panel" target="_blank">
+                      <i class="fa fa-tasks"></i>
+                      &nbsp;Bug Tracker
+                    </a>
+                  </li>
+                  <li>
+                    <a href="https://twitter.com/jbossweld" target="_blank">
+                      <i class="fa fa-twitter"></i>
+                      &nbsp;Follow @jbossweld
+                    </a>
+                  </li>
+                </ul>
+              </div>
+            </div>
+          </div>
+        </div>
+        <div class="col-md-10 col-sm-9">
+          <div class="row hidden-xs">
+            <div class="dropup">
+              <div id="ajbossproject">
+                A JBoss Project
+              </div>
+              <a class="tabnav-closed" href="#" id="tab">Red Hat</a>
+              <script>
+                window.addEventListener('load', function() {renderTabzilla("Weld", "weld", false )}, false);
+              </script>
+            </div>
+          </div>
+          <div class="row">
+            <div class="col-md-4">
+              <a href="/">
+                <img alt="Weld Logo" class="hidden-xs weld-home-logo" src="/images/weld_logo_450x.png">
+              </a>
+            </div>
+            <div class="col-md-8">
+              <img alt="CDI tagcloud" class="hidden-xs hidden-sm cdi-background" src="/images/CDIbackground.png">
+            </div>
+          </div>
+          <div class="row content-wrapper">
+            <div class="col-md-12">
+              <div class="post">
+                <h1>
+                  Weld 6.0.0.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>Since there have been no further bugs reported, Weld <code>6.0.0.CR2</code> has evolved into its <code>Final</code> form.
+                  Say hello to <code>Weld API 6.0.Final</code> as well as <code>Weld Core 6.0.0.Final</code>!</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Since there are no changes from the previous <code>CR2</code> version, early adopters shouldn&#8217;t encounter any unwelcome surprises.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Nonetheless, should you run into any bugs, do get in touch so that we can squash them as soon as possible!</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>And speaking of getting in touch, we recognize that JIRA can be a little daunting, so we are trying to make that easier by <strong>enabling GitHub discussions</strong>.
+                  You can now ask your question in:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p><a href="https://github.com/weld/core/discussions">Weld Core</a> GH discussions</p>
+                  </li>
+                  <li>
+                  <p><a href="https://github.com/weld/api/discussions">Weld API</a> GH discussions</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>And don&#8217;t you worry, the <code>weld-dev</code> mailing list is still kicking plus, for the time being, we are still using JIRA for per-release issue tracking.</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.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=12439250" 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-600Final/";
+                            var disqus_developer = null;
+                            var disqus_identifier = "4baca060ebe04a950172806816e649225453b56c";
+                            (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 1895ef17..ee95ddb7 100644
--- a/news/index.html
+++ b/news/index.html
@@ -141,6 +141,58 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2024/12/16/weld-600Final/">Weld 6.0.0.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>Since there have been no further bugs reported, Weld <code>6.0.0.CR2</code> has evolved into its <code>Final</code> form.
+                  Say hello to <code>Weld API 6.0.Final</code> as well as <code>Weld Core 6.0.0.Final</code>!</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Since there are no changes from the previous <code>CR2</code> version, early adopters shouldn&#8217;t encounter any unwelcome surprises.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Nonetheless, should you run into any bugs, do get in touch so that we can squash them as soon as possible!</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>And speaking of getting in touch, we recognize that JIRA can be a little daunting, so we are trying to make that easier by <strong>enabling GitHub discussions</strong>.
+                  You can now ask your question in:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p><a href="https://github.com/weld/core/discussions">Weld Core</a> GH discussions</p>
+                  </li>
+                  <li>
+                  <p><a href="https://github.com/weld/api/discussions">Weld API</a> GH discussions</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>And don&#8217;t you worry, the <code>weld-dev</code> mailing list is still kicking plus, for the time being, we are still using JIRA for per-release issue tracking.</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.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=12439250" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2024/12/16/weld-514Final/">Weld 5.1.4.Final</a>
@@ -397,116 +449,7 @@ <h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2024/07/03/weld-600Beta4/">Weld 6.0.0.Beta4</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2024-7-3
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/release">release</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Matej Novotny
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>New versions of Weld artifacts are now available in Central - Weld Core <code>6.0.0.Beta4</code> accompanied by Weld API <code>6.0.Beta5</code>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Where applicable, <code>6.0.0.Beta4</code> bumps up Jakarta dependencies to their <code>Final</code> variants as well as implements remaining features from CDI spec, adds new Weld-specific API and addresses multiple backlog issues that were scheduled for this major release.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>You might be wondering where did Betas 2 and 3 go. While you can find their artifacts in Central, they bear no difference from <code>Beta4</code> apart from not having separate distributable ZIP and docs.
-                  With that in mind, below is the list of changes since Weld 6.0.0.Beta1:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Added the ability to register Build Compatible Extension in Weld SE without discovery (<a href="https://issues.redhat.com/browse/WELD-2772">WELD-2772</a>)</p>
-                  </li>
-                  <li>
-                  <p>Use <code>Lock</code> instead of <code>synchronized</code> within <code>ContextualInstanceStrategy</code> to be more virtual thread-friendly (<a href="https://issues.redhat.com/browse/WELD-2788">WELD-2788</a>)</p>
-                  </li>
-                  <li>
-                  <p>Skip superclass declarations of final methods when creating proxies (<a href="https://issues.redhat.com/browse/WELD-2785">WELD-2785</a>)</p>
-                  </li>
-                  <li>
-                  <p>Observer method confiurator now correctly allow to override <code>Reception</code> settings without changing its <code>notify()</code> method (<a href="https://issues.redhat.com/browse/WELD-2786">WELD-2786</a>)</p>
-                  </li>
-                  <li>
-                  <p>Correct <code>CommonLogger</code> to mention correct GAV for Jandex (<a href="https://issues.redhat.com/browse/WELD-2770">WELD-2770</a>)</p>
-                  </li>
-                  <li>
-                  <p>Invoker API enhancements (<a href="https://issues.redhat.com/browse/WELD-2780">WELD-2780</a>)</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Proper exception handling</p>
-                  </li>
-                  <li>
-                  <p>Document API Weld offer above what CDI specification has; Weld retains all parts of the initial design CDI had</p>
-                  </li>
-                  <li>
-                  <p>Added benchmarks to have a measure of our implementation versus direct invocation</p>
-                  </li>
-                  <li>
-                  <p>Code cleanup and other minor tweaks</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Remove <code>SecurityManager</code> related code from Weld (<a href="https://issues.redhat.com/browse/WELD-2789">WELD-2789</a>)</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p><code>SecurityManager</code> has been deprecated for quite a upcoming JDK versions plan to remove it completely so we remove it as part of the major release version</p>
-                  </li>
-                  <li>
-                  <p>This means Weld 6 no longer uses priviledged actions to perform various tasks, such as constructor invocations, reflection on classes etc.</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Remove <code>WARN</code> logging when an interceptor binding target of lifecycle interceptors targets anything other than <code>TYPE</code> (<a href="https://issues.redhat.com/browse/WELD-2790">WELD-2790</a>)</p>
-                  </li>
-                  <li>
-                  <p>Revise Weld 6 examples; only keep essentials (<a href="https://issues.redhat.com/browse/WELD-2771">WELD-2771</a>)</p>
-                  </li>
-                  <li>
-                  <p>Address Weld API javadoc warning (<a href="https://issues.redhat.com/browse/WELD-2779">WELD-2779</a>)</p>
-                  </li>
-                  <li>
-                  <p>Revisit servlet setup and testing (<a href="https://issues.redhat.com/browse/WELD-2784">WELD-2784</a>)</p>
-                  </li>
-                  <li>
-                  <p>Clean up legacy Jetty integration parts (<a href="https://issues.redhat.com/browse/WELD-2787">WELD-2787</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>Note that the latest <a href="http://docs.jboss.org/weld/reference/6.0.0.Beta4/en-US/html_single/" target="_blank" rel="noopener">documentation</a> incorrectly states that it is for <code>SNAPSHOT</code> which isn&#8217;t the case.
-                  It is built for Beta4 but due to incorrect script setup the version number wasn&#8217;t picked up properly.
-                  This will be corrected for the next release.</p>
-                  </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.Beta4/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=12423381" 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>
+              <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/19.html" class="page-link">19</a> <a href="/news/page/20.html" class="page-link">20</a> <a href="/news/page/2.html" class="next-link">Next</a> </div>
               <hr>
               <div>
                 <a href="http://weld.cdi-spec.org/news.atom">
diff --git a/news/page/10.html b/news/page/10.html
index 5f159b6c..93dc7e7b 100644
--- a/news/page/10.html
+++ b/news/page/10.html
@@ -141,6 +141,143 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2017/08/25/weld-301Final/">Weld 3.0.1.Final</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2017-8-25
+                  &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.1.Final is out and it brings some bugfixes as well as new version of Weld API - 3.0.SP1.
+                  Among the new things you can find sweet stuff such as an expansion to CDI 2 <code>BeanConfigurator</code> API or the ability to detect that injected object is Weld proxy.
+                  Wait, not only detect - you can also use it do get <code>Metadata</code> or even retrieve the actual contextual instance hidden beneath.
+                  So let&#8217;s see the summary of fixes and improvements, shall we?</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>Revised support for Java 8 default methods (<a href="https://issues.jboss.org/browse/WELD-2407" target="_blank" rel="noopener">WELD-2407</a> and <a href="https://issues.jboss.org/browse/WELD-2405" target="_blank" rel="noopener">WELD-2405</a>)</p>
+                  </li>
+                  <li>
+                  <p>Corrected MIME types for all POMs in Weld core - Nexus 3 will love us now! (<a href="https://issues.jboss.org/browse/WELD-2417" target="_blank" rel="noopener">WELD-2417</a>)</p>
+                  </li>
+                  <li>
+                  <p>Fixed how proxies are created for signed packages (<a href="https://issues.jboss.org/browse/WELD-2402" target="_blank" rel="noopener">WELD-2402</a>)</p>
+                  </li>
+                  <li>
+                  <p>Portable extension events should now be fired in accordance with specification <a href="https://issues.jboss.org/browse/WELD-2393" target="_blank" rel="noopener">WELD-2393</a></p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Weld SE</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Synthetic bean archive can now have discovery mode <code>annotated</code> (<a href="https://issues.jboss.org/browse/WELD-2386" target="_blank" rel="noopener">WELD-2386</a>)</p>
+                  </li>
+                  <li>
+                  <p>Added a convenient static method <code>WeldContainer.current()</code> allowing you to quickly grab your running instance (<a href="https://issues.jboss.org/browse/WELD-2399" target="_blank" rel="noopener">WELD-2399</a>)</p>
+                  </li>
+                  <li>
+                  <p>Fixed a glitch when starting SE container and adding packages via <code>Weld.addPackages()</code> <a href="https://issues.jboss.org/browse/WELD-2395" target="_blank" rel="noopener">WELD-2395</a></p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Weld API/SPI</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Added a way to detect proxies and subclasses (<a href="https://issues.jboss.org/browse/WELD-2407" target="_blank" rel="noopener">WELD-2407</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Every Weld-enhanced object (subclass/proxy) will now implement <a href="https://github.com/weld/api/tree/3.0.SP1/weld/src/main/java/org/jboss/weld/proxy">new marker interface(s)</a> which grant access to additional data about the bean</p>
+                  </li>
+                  <li>
+                  <p>This also allows to retrieve the underlying contextual instance</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Added <code>WeldBeanConfigurator</code> to API - allows to select an <code>@Alternative</code> which was created using <code>BeanConfigurator</code> (<a href="https://issues.jboss.org/browse/WELD-2412" target="_blank" rel="noopener">WELD-2412</a>)</p>
+                  </li>
+                  <li>
+                  <p>We have enhanced the <code>Environment</code> in Weld SPI so that integrators define whether their bean archives are "EE module aware" or not (<a href="https://issues.jboss.org/browse/WELD-2398" target="_blank" rel="noopener">WELD-2398</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Other</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Under the <code>jboss-as</code> directory of Weld source code, you can now make use of new profiles to create WildFly patches yourself <a href="https://issues.jboss.org/browse/WELD-2397" target="_blank" rel="noopener">WELD-2397</a></p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>To learn more about this, please refer to the <a href="https://github.com/weld/core/blob/3.0.1.Final/README.md#creating-a-patch-file-for-wildfly"><code>README</code> file in our repository</a></p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Weld SE and Weld Servlet now explicitly depends on <code>jboss-classfilewriter</code> in version 1.2+ <a href="https://issues.jboss.org/browse/WELD-2406" target="_blank" rel="noopener">WELD-2406</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.1.Final/wildfly-10.1.0.Final-weld-3.0.1.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly 10.1.0.Final</a> is available.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>But, for those of you who like to stay sharp, we have also created a <a href="http://download.jboss.org/weld/3.0.1.Final/wildfly-11.0.0.Beta1-weld-3.0.1.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly 11.0.0.Beta1</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Please note that there is currently a <a href="https://issues.jboss.org/browse/WFLY-9240">known issue</a> with security context propagation in Weld 3 for WildFly 11.
+                  Though this should only concern people who use the combination of Elytron subsystem and asynchronous CDI events.</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.1.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=12334698" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2017/08/07/weld-vertx-next/">Weld Vert.x Next?</a>
@@ -855,114 +992,7 @@ <h2 id="_wildfly_patch">WildFly Patch</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2017/04/07/weld-243Final/">Weld 2.4.3.Final</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2017-4-7
-                  &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>Even as we get ever closer to CDI 2.0 final version, we shan&#8217;t forget about our stable 2.4 branch.
-                  Ladies and gentlemen, here comes the next-in-line 2.4 release - Weld 2.4.3.Final!</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Notable fixes and improvements:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Weld now shares proxy classes for built-in beans of the same type (<a href="https://issues.jboss.org/browse/WELD-2344" target="_blank" rel="noopener">WELD-2344</a>)</p>
-                  </li>
-                  <li>
-                  <p>Fixed usage of Jandex on Tomcat when using <code>unpackWars=false</code> (<a href="https://issues.jboss.org/browse/WELD-2357" target="_blank" rel="noopener">WELD-2357</a>)</p>
-                  </li>
-                  <li>
-                  <p>Weld now supports wider variety of non-portable extension observer methods (<a href="https://issues.jboss.org/browse/WELD-2338" target="_blank" rel="noopener">WELD-2338</a>)</p>
-                  </li>
-                  <li>
-                  <p>There is now new debug level logging during bootstrap which allows to monitor name, start, end and duration of all bootstrap phases (<a href="https://issues.jboss.org/browse/WELD-2336" target="_blank" rel="noopener">WELD-2336</a>)</p>
-                  </li>
-                  <li>
-                  <p>Session replication</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Built-in session and conversation scoped beans are not part of the bean identifier index anymore (<a href="https://issues.jboss.org/browse/WELD-2343" target="_blank" rel="noopener">WELD-2343</a>)</p>
-                  </li>
-                  <li>
-                  <p>Handle situation when <code>HTTPSessionBean</code> might not be serializable (<a href="https://issues.jboss.org/browse/WELD-2346" target="_blank" rel="noopener">WELD-2346</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Weld SE</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>You can now easily register new <code>org.jboss.weld.bootstrap.api.Service</code> during container bootstrap (<a href="https://issues.jboss.org/browse/WELD-2360" target="_blank" rel="noopener">WELD-2360</a>)</p>
-                  </li>
-                  <li>
-                  <p>Any <code>javax.enterprise.inject.spi.CDI</code> method can now be called during <code>AfterDeploymentValidation</code> (<a href="https://issues.jboss.org/browse/WELD-2371" target="_blank" rel="noopener">WELD-2371</a>)</p>
-                  </li>
-                  <li>
-                  <p><code>ContainerInitialized</code> event is now correctly fired after registration of shutdown hook (<a href="https://issues.jboss.org/browse/WELD-2340" target="_blank" rel="noopener">WELD-2340</a>)</p>
-                  </li>
-                  <li>
-                  <p><code>ContainerInitialized</code> and <code>ContainerShutdown</code> now implement <code>toString()</code> (<a href="https://issues.jboss.org/browse/WELD-2354" target="_blank" rel="noopener">WELD-2354</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Probe development tool</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Allow monitoring of bean instance creation using <code>AroundConstruct</code> (<a href="https://issues.jboss.org/browse/WELD-2332" target="_blank" rel="noopener">WELD-2332</a>)</p>
-                  </li>
-                  <li>
-                  <p>Fixed a situation when bean was wrongly marked as unused when injected as parameter (<a href="https://issues.jboss.org/browse/WELD-2342" target="_blank" rel="noopener">WELD-2342</a>)</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=12333607" 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/2.4.3.Final/wildfly-10.1.0.Final-weld-2.4.3.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly</a> is available.
-                  This time the target platform is <strong>WildFly 10.1.0.Final</strong>.
-                  If you’re not familiar with patching WildFly, check the <a href="/documentation/#12">FAQ</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>&#91; <a href="/download/">Download</a> &#93;
-                  &#91; <a href="http://docs.jboss.org/weld/reference/2.4.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=12333607" 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>
+              <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/19.html" class="page-link">19</a> <a href="/news/page/20.html" class="page-link">20</a> <a href="/news/page/11.html" class="next-link">Next</a> </div>
               <hr>
               <div>
                 <a href="http://weld.cdi-spec.org/news.atom">
diff --git a/news/page/11.html b/news/page/11.html
index 62322632..98d44d16 100644
--- a/news/page/11.html
+++ b/news/page/11.html
@@ -141,6 +141,113 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2017/04/07/weld-243Final/">Weld 2.4.3.Final</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2017-4-7
+                  &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>Even as we get ever closer to CDI 2.0 final version, we shan&#8217;t forget about our stable 2.4 branch.
+                  Ladies and gentlemen, here comes the next-in-line 2.4 release - Weld 2.4.3.Final!</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Notable fixes and improvements:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Weld now shares proxy classes for built-in beans of the same type (<a href="https://issues.jboss.org/browse/WELD-2344" target="_blank" rel="noopener">WELD-2344</a>)</p>
+                  </li>
+                  <li>
+                  <p>Fixed usage of Jandex on Tomcat when using <code>unpackWars=false</code> (<a href="https://issues.jboss.org/browse/WELD-2357" target="_blank" rel="noopener">WELD-2357</a>)</p>
+                  </li>
+                  <li>
+                  <p>Weld now supports wider variety of non-portable extension observer methods (<a href="https://issues.jboss.org/browse/WELD-2338" target="_blank" rel="noopener">WELD-2338</a>)</p>
+                  </li>
+                  <li>
+                  <p>There is now new debug level logging during bootstrap which allows to monitor name, start, end and duration of all bootstrap phases (<a href="https://issues.jboss.org/browse/WELD-2336" target="_blank" rel="noopener">WELD-2336</a>)</p>
+                  </li>
+                  <li>
+                  <p>Session replication</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Built-in session and conversation scoped beans are not part of the bean identifier index anymore (<a href="https://issues.jboss.org/browse/WELD-2343" target="_blank" rel="noopener">WELD-2343</a>)</p>
+                  </li>
+                  <li>
+                  <p>Handle situation when <code>HTTPSessionBean</code> might not be serializable (<a href="https://issues.jboss.org/browse/WELD-2346" target="_blank" rel="noopener">WELD-2346</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Weld SE</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>You can now easily register new <code>org.jboss.weld.bootstrap.api.Service</code> during container bootstrap (<a href="https://issues.jboss.org/browse/WELD-2360" target="_blank" rel="noopener">WELD-2360</a>)</p>
+                  </li>
+                  <li>
+                  <p>Any <code>javax.enterprise.inject.spi.CDI</code> method can now be called during <code>AfterDeploymentValidation</code> (<a href="https://issues.jboss.org/browse/WELD-2371" target="_blank" rel="noopener">WELD-2371</a>)</p>
+                  </li>
+                  <li>
+                  <p><code>ContainerInitialized</code> event is now correctly fired after registration of shutdown hook (<a href="https://issues.jboss.org/browse/WELD-2340" target="_blank" rel="noopener">WELD-2340</a>)</p>
+                  </li>
+                  <li>
+                  <p><code>ContainerInitialized</code> and <code>ContainerShutdown</code> now implement <code>toString()</code> (<a href="https://issues.jboss.org/browse/WELD-2354" target="_blank" rel="noopener">WELD-2354</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Probe development tool</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Allow monitoring of bean instance creation using <code>AroundConstruct</code> (<a href="https://issues.jboss.org/browse/WELD-2332" target="_blank" rel="noopener">WELD-2332</a>)</p>
+                  </li>
+                  <li>
+                  <p>Fixed a situation when bean was wrongly marked as unused when injected as parameter (<a href="https://issues.jboss.org/browse/WELD-2342" target="_blank" rel="noopener">WELD-2342</a>)</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=12333607" 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/2.4.3.Final/wildfly-10.1.0.Final-weld-2.4.3.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly</a> is available.
+                  This time the target platform is <strong>WildFly 10.1.0.Final</strong>.
+                  If you’re not familiar with patching WildFly, check the <a href="/documentation/#12">FAQ</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="/download/">Download</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/2.4.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=12333607" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2017/03/03/weld-300CR2/">Weld 3.0.0.CR2</a>
@@ -580,94 +687,7 @@ <h2 id="_wildfly_patch">WildFly Patch</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2016/12/19/weld-300Beta1/">Weld 3.0.0.Beta1</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2016-12-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 class="paragraph">
-                  <p>I am very pleased to announce the first <strong>Beta</strong> version of Weld <strong>3.0.0</strong> (CDI 2.0).
-                  See also <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12331387" target="_blank" rel="noopener">the release details</a>.
-                  Thanks to everyone involved in this release!</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>This is an important milestone.
-                  CDI 2.0 is now considered "feature complete" and so the next Weld 3 versions should be mostly dedicated to cleanup and optimization.
-                  The next version will be Weld <strong>3.0.0.CR1</strong> (ETA in mid January).
-                  Finally, we would like to release Weld <strong>3.0.0.Final</strong> in early February.</p>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_new_and_noteworthy">New and noteworthy</h2>
-                  <div class="sectionbody">
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p><code>javax.enterprise.inject.spi.InterceptionFactory</code> implementation (<a href="https://issues.jboss.org/browse/WELD-2257" target="_blank" rel="noopener">WELD-2257</a>)</p>
-                  </li>
-                  <li>
-                  <p><code>ProcessSyntheticObserverMethod</code> container lifecycle event (<a href="https://issues.jboss.org/browse/WELD-2279" target="_blank" rel="noopener">WELD-2279</a>)</p>
-                  </li>
-                  <li>
-                  <p><code>BeforeDestroyed</code> event fired before a context is actually destroyed (<a href="https://issues.jboss.org/browse/WELD-2269" target="_blank" rel="noopener">WELD-2269</a>)</p>
-                  </li>
-                  <li>
-                  <p>"trimmed" bean archives (<a href="https://issues.jboss.org/browse/WELD-2268" target="_blank" rel="noopener">WELD-2268</a>)</p>
-                  </li>
-                  <li>
-                  <p>context control - <code>ActivateRequestContext</code> interceptor binding (<a href="https://issues.jboss.org/browse/WELD-2267" target="_blank" rel="noopener">WELD-2267</a>) and <code>RequestContextController</code> built-in bean (<a href="https://issues.jboss.org/browse/WELD-2266" target="_blank" rel="noopener">WELD-2266</a>)</p>
-                  </li>
-                  <li>
-                  <p><code>ProcessSyntheticBean</code> container lifecycle event (<a href="https://issues.jboss.org/browse/WELD-2265" target="_blank" rel="noopener">WELD-2265</a>)</p>
-                  </li>
-                  <li>
-                  <p>few proposals did not make it into CDI 2.0 and so we enhanced the Weld API:</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p><code>org.jboss.weld.inject.WeldInstance</code> (already part of Weld 2.4 API)</p>
-                  </li>
-                  <li>
-                  <p><code>org.jboss.weld.interceptor.WeldInvocationContext</code> allows to obtain a set of interceptor bindings for a lifecycle callback, business method, timeout method, or constructor (see also <a href="https://issues.jboss.org/browse/CDI-468" target="_blank" rel="noopener">CDI-468</a>)</p>
-                  </li>
-                  <li>
-                  <p><code>org.jboss.weld.bootstrap.event.WeldAfterBeanDiscovery</code> allows to obtain an <code>InterceptorConfigurator</code> to configure a new <code>Interceptor</code> bean</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  </ul>
-                  </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.Beta1/wildfly-10.1.0.Final-weld-3.0.0.Beta1-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="/download/">Download</a> &#93;
-                  &#91; <a href="http://docs.jboss.org/weld/reference/3.0.0.Beta1/en-US/html/" target="_blank" rel="noopener">Documentation</a> &#93;
-                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12331387" 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>
+              <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/19.html" class="page-link">19</a> <a href="/news/page/20.html" class="page-link">20</a> <a href="/news/page/12.html" class="next-link">Next</a> </div>
               <hr>
               <div>
                 <a href="http://weld.cdi-spec.org/news.atom">
diff --git a/news/page/12.html b/news/page/12.html
index 823df899..c61b5404 100644
--- a/news/page/12.html
+++ b/news/page/12.html
@@ -141,6 +141,93 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2016/12/19/weld-300Beta1/">Weld 3.0.0.Beta1</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2016-12-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 class="paragraph">
+                  <p>I am very pleased to announce the first <strong>Beta</strong> version of Weld <strong>3.0.0</strong> (CDI 2.0).
+                  See also <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12331387" target="_blank" rel="noopener">the release details</a>.
+                  Thanks to everyone involved in this release!</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>This is an important milestone.
+                  CDI 2.0 is now considered "feature complete" and so the next Weld 3 versions should be mostly dedicated to cleanup and optimization.
+                  The next version will be Weld <strong>3.0.0.CR1</strong> (ETA in mid January).
+                  Finally, we would like to release Weld <strong>3.0.0.Final</strong> in early February.</p>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_new_and_noteworthy">New and noteworthy</h2>
+                  <div class="sectionbody">
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p><code>javax.enterprise.inject.spi.InterceptionFactory</code> implementation (<a href="https://issues.jboss.org/browse/WELD-2257" target="_blank" rel="noopener">WELD-2257</a>)</p>
+                  </li>
+                  <li>
+                  <p><code>ProcessSyntheticObserverMethod</code> container lifecycle event (<a href="https://issues.jboss.org/browse/WELD-2279" target="_blank" rel="noopener">WELD-2279</a>)</p>
+                  </li>
+                  <li>
+                  <p><code>BeforeDestroyed</code> event fired before a context is actually destroyed (<a href="https://issues.jboss.org/browse/WELD-2269" target="_blank" rel="noopener">WELD-2269</a>)</p>
+                  </li>
+                  <li>
+                  <p>"trimmed" bean archives (<a href="https://issues.jboss.org/browse/WELD-2268" target="_blank" rel="noopener">WELD-2268</a>)</p>
+                  </li>
+                  <li>
+                  <p>context control - <code>ActivateRequestContext</code> interceptor binding (<a href="https://issues.jboss.org/browse/WELD-2267" target="_blank" rel="noopener">WELD-2267</a>) and <code>RequestContextController</code> built-in bean (<a href="https://issues.jboss.org/browse/WELD-2266" target="_blank" rel="noopener">WELD-2266</a>)</p>
+                  </li>
+                  <li>
+                  <p><code>ProcessSyntheticBean</code> container lifecycle event (<a href="https://issues.jboss.org/browse/WELD-2265" target="_blank" rel="noopener">WELD-2265</a>)</p>
+                  </li>
+                  <li>
+                  <p>few proposals did not make it into CDI 2.0 and so we enhanced the Weld API:</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p><code>org.jboss.weld.inject.WeldInstance</code> (already part of Weld 2.4 API)</p>
+                  </li>
+                  <li>
+                  <p><code>org.jboss.weld.interceptor.WeldInvocationContext</code> allows to obtain a set of interceptor bindings for a lifecycle callback, business method, timeout method, or constructor (see also <a href="https://issues.jboss.org/browse/CDI-468" target="_blank" rel="noopener">CDI-468</a>)</p>
+                  </li>
+                  <li>
+                  <p><code>org.jboss.weld.bootstrap.event.WeldAfterBeanDiscovery</code> allows to obtain an <code>InterceptorConfigurator</code> to configure a new <code>Interceptor</code> bean</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  </ul>
+                  </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.Beta1/wildfly-10.1.0.Final-weld-3.0.0.Beta1-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="/download/">Download</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/3.0.0.Beta1/en-US/html/" target="_blank" rel="noopener">Documentation</a> &#93;
+                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12331387" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2016/11/18/weld-241Final/">Weld 2.4.1.Final</a>
@@ -945,90 +1032,7 @@ <h3 id="_actions_performed_by_extensions">Actions performed by extensions</h3>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2016/09/13/weld-240Final/">Weld 2.4.0.Final</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2016-9-13
-                  &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 <strong>first stable version of Weld 2.4</strong> (CDI 1.2).
-                  See also <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12331363" target="_blank" rel="noopener">the release details</a>.
-                  From now on, 2.4 is the current stable version of Weld and 2.3 is not actively developed anymore.
-                  Thanks to everyone involved in this release!</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Most of the new features were already introduced in <a href="/news/2016/08/19/weld-240CR1" target="_blank" rel="noopener">First release candidate of Weld 2.4</a>.
-                  To sum it up:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Removed dependency on <code>com.google.guava:guava</code></p>
-                  </li>
-                  <li>
-                  <p>Enhanced version of <code>javax.enterprise.inject.Instance</code></p>
-                  </li>
-                  <li>
-                  <p>Veto <code>AnnotatedType</code> not annotated with a bean defining annotation</p>
-                  </li>
-                  <li>
-                  <p><code>@ActivateRequestScope</code> interceptor binding moved to Weld API and renamed to <code>@ActivateRequestContext</code></p>
-                  </li>
-                  <li>
-                  <p>Improved rolling upgrades support</p>
-                  </li>
-                  <li>
-                  <p>Events - reflect the output of CDI-494</p>
-                  </li>
-                  <li>
-                  <p>Probe - allow to filter unused beans</p>
-                  </li>
-                  <li>
-                  <p>Cleanup, cleanup, cleanup&#8230;&#8203;</p>
-                  </li>
-                  <li>
-                  <p>Initial Java 9 support</p>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>Moreover, 2.4.0.Final allows to export the Probe development tool data (to be discussed in one of the following blog posts) and fixes a minor problem in non-EE environments (see also <a href="https://issues.jboss.org/browse/WELD-2227">WELD-2227</a>).</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>In the coming weeks, the Weld team is also going to publish <strong>"Weld tips"</strong> - a series of concise articles.
-                  The intention is to familiarize developers with less known Weld features.
-                  There will be no hot news, just useful existing features (repetition is the mother of wisdom ;-).</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/2.4.0.Final/wildfly-10.1.0.Final-weld-2.4.0.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=12331363" 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>
+              <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/19.html" class="page-link">19</a> <a href="/news/page/20.html" class="page-link">20</a> <a href="/news/page/13.html" class="next-link">Next</a> </div>
               <hr>
               <div>
                 <a href="http://weld.cdi-spec.org/news.atom">
diff --git a/news/page/13.html b/news/page/13.html
index bb9d8ba0..d5143131 100644
--- a/news/page/13.html
+++ b/news/page/13.html
@@ -141,6 +141,89 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2016/09/13/weld-240Final/">Weld 2.4.0.Final</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2016-9-13
+                  &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 <strong>first stable version of Weld 2.4</strong> (CDI 1.2).
+                  See also <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12331363" target="_blank" rel="noopener">the release details</a>.
+                  From now on, 2.4 is the current stable version of Weld and 2.3 is not actively developed anymore.
+                  Thanks to everyone involved in this release!</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Most of the new features were already introduced in <a href="/news/2016/08/19/weld-240CR1" target="_blank" rel="noopener">First release candidate of Weld 2.4</a>.
+                  To sum it up:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Removed dependency on <code>com.google.guava:guava</code></p>
+                  </li>
+                  <li>
+                  <p>Enhanced version of <code>javax.enterprise.inject.Instance</code></p>
+                  </li>
+                  <li>
+                  <p>Veto <code>AnnotatedType</code> not annotated with a bean defining annotation</p>
+                  </li>
+                  <li>
+                  <p><code>@ActivateRequestScope</code> interceptor binding moved to Weld API and renamed to <code>@ActivateRequestContext</code></p>
+                  </li>
+                  <li>
+                  <p>Improved rolling upgrades support</p>
+                  </li>
+                  <li>
+                  <p>Events - reflect the output of CDI-494</p>
+                  </li>
+                  <li>
+                  <p>Probe - allow to filter unused beans</p>
+                  </li>
+                  <li>
+                  <p>Cleanup, cleanup, cleanup&#8230;&#8203;</p>
+                  </li>
+                  <li>
+                  <p>Initial Java 9 support</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>Moreover, 2.4.0.Final allows to export the Probe development tool data (to be discussed in one of the following blog posts) and fixes a minor problem in non-EE environments (see also <a href="https://issues.jboss.org/browse/WELD-2227">WELD-2227</a>).</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>In the coming weeks, the Weld team is also going to publish <strong>"Weld tips"</strong> - a series of concise articles.
+                  The intention is to familiarize developers with less known Weld features.
+                  There will be no hot news, just useful existing features (repetition is the mother of wisdom ;-).</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/2.4.0.Final/wildfly-10.1.0.Final-weld-2.4.0.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=12331363" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2016/08/19/weld-240CR1/">First release candidate of Weld 2.4</a>
@@ -529,106 +612,7 @@ <h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2016/05/18/enhanced-instance/">Programmatic lookup improvements</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2016-5-18
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/api">api</a>
-                    ,
-                    <a href="/news/tags/draft">draft</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Martin Kouba
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p><code>javax.enterprise.inject.Instance</code> is sometimes invaluable companion.
-                  For example, <code>Instance</code> allows you to handle unsatisfied and ambiguous dependencies gracefully.
-                  E.g. it&#8217;s possible to avoid unnecessary deployment problems:</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">interface OrderProcessor {&#x000A;      void process(Order order);&#x000A;      int getPriority();&#x000A;    }&#x000A;    &#x000A;    class OrderService {&#x000A;    &#x000A;      @Inject&#x000A;      Instance&lt;OrderProcessor&gt; instance;&#x000A;    &#x000A;      void create(Order order) {&#x000A;        if (!instance.isUnsatisfied() &amp;&amp; !instance.isAmbiguous()) {&#x000A;            instance.get().process(order);&#x000A;        } else {&#x000A;            // Log a warning or throw an exception&#x000A;        }&#x000A;      }&#x000A;    }</code></pre>
-                  </div>
-                  </div>
-                  <div class="paragraph">
-                  <p>It is less known that <code>Instance</code> extends <code>Iterable</code> and so it allows to iterate through contextual references of beans with the specified combination of required type and qualifiers.
-                  This might be useful if the set of beans satisfying the given type and qualifiers is not known beforehand.
-                  We may also need to resolve ambiguities manually, e.g. inspect all the instances and choose only those matching our needs.</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@ApplicationScoped&#x000A;    class OrderService {&#x000A;    &#x000A;      @Inject&#x000A;      @Any&#x000A;      Instance&lt;OrderProcessor&gt; instance;&#x000A;    &#x000A;      void create(Order order) {&#x000A;        for (OrderProcessor processor : instance) {&#x000A;            if (processor.getPriority() &gt; 10) {&#x000A;                processor.process(order);&#x000A;            }&#x000A;        }&#x000A;      }&#x000A;    }</code></pre>
-                  </div>
-                  </div>
-                  <div class="paragraph">
-                  <p>Another interesting use case might be selecting exactly one implementation:</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@ApplicationScoped&#x000A;    class OrderService {&#x000A;    &#x000A;      @Inject&#x000A;      @Any&#x000A;      Instance&lt;OrderProcessor&gt; instance;&#x000A;    &#x000A;      void create(Order order) {&#x000A;        List&lt;OrderProcessor&gt; processors = new ArrayList&lt;&gt;();&#x000A;        for (OrderProcessor processor : instance) {&#x000A;            processors.add(processor);&#x000A;        }&#x000A;        Collections.sort(processors, Comparator.&lt;OrderProcessor&gt; comparingInt(p -&gt; p.getPriority()).reversed());&#x000A;        // Use the processor with highest priority&#x000A;        processors.get(0).ping();&#x000A;      }&#x000A;    }</code></pre>
-                  </div>
-                  </div>
-                  <div class="paragraph">
-                  <p>This works nice.
-                  But we have to pay extra attention to the scopes.
-                  If a <code>Processor</code> implementation is <code>@Dependent</code> a similar usage results in memory leaks.
-                  What&#8217;s the reason?
-                  The <code>Processor</code> instance is the dependent object of <code>Instance&lt;OrderProcessor&gt;</code> which is the dependent object of <code>OrderService</code>.
-                  And so each <code>Instance.get()</code> will produce a new <code>Processor</code> bound to the lifecycle of the <code>OrderService</code>.
-                  To avoid the leak we should always call <code>Instance.destroy()</code> method in similar cases.
-                  However, <code>Instance.destroy()</code> always destroys the underlying contextual instance!
-                  Even if you pass e.g. a client proxy of an <code>@ApplicationScoped</code> bean.
-                  This is not always desirable.
-                  Currently, it&#8217;s quite complicated to detect a dependent bean inside the loop.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>To extend the possibilities the Weld team is experimenting with <code>org.jboss.weld.inject.WeldInstance</code> - an enhanced version of <code>javax.enterprise.inject.Instance</code>.
-                  There are three new methods we find useful. The first one - <code>getHandler()</code> - allows to obtain a contextual reference handler which not only holds the contextual reference but also allows to inspect the metadata of the relevant bean and to destroy the underlying contextual instance.
-                  Moreover, the handler implements <code>AutoCloseable</code>:</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">import org.jboss.weld.inject.WeldInstance;&#x000A;    &#x000A;    class Foo {&#x000A;    &#x000A;      @Inject&#x000A;      WeldInstance&lt;Bar&gt; instance;&#x000A;    &#x000A;      void doWork() {&#x000A;        try (Handler&lt;Bar&gt; bar = instance.getHandler()) {&#x000A;            bar.get().doBusiness();&#x000A;            // Note that Bar will be automatically destroyed at the end of the try-with-resources statement&#x000A;        }&#x000A;    &#x000A;        Handler&lt;Bar&gt; bar = instance.getHandler()&#x000A;        bar.get().doBusiness();&#x000A;        // Calls Instance.destroy()&#x000A;        bar.destroy();&#x000A;      }&#x000A;    &#x000A;    }</code></pre>
-                  </div>
-                  </div>
-                  <div class="paragraph">
-                  <p>The next method - <code>handlerIterator()</code> - returns an iterator over contextual reference handlers. This might be useful if you need more control over contextual references inside the loop:</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@ApplicationScoped&#x000A;    class OrderService {&#x000A;    &#x000A;      @Inject&#x000A;      @Any&#x000A;      WeldInstance&lt;OrderProcessor&gt; instance;&#x000A;    &#x000A;      void create(Order order) {&#x000A;        for (Iterator&lt;Handler&lt;OrderProcessor&gt;&gt; iterator = instance.handlerIterator(); iterator.hasNext();) {&#x000A;                Handler&lt;OrderProcessor&gt; processor = iterator.next();&#x000A;                processor.get().process(order);&#x000A;                if (processor.getBean().getScope().equals(Dependent.class)) {&#x000A;                    // Destroy only dependent processors&#x000A;                    processor.destroy();&#x000A;                }&#x000A;            }&#x000A;      }&#x000A;    }</code></pre>
-                  </div>
-                  </div>
-                  <div class="paragraph">
-                  <p>The last one is just a convenient method - <code>isResolvable()</code> - a replacement for <code>!isUnsatisfied() &amp;&amp; !isAmbiguous()</code> which is the expression most users are interested in:</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">class OrderService {&#x000A;    &#x000A;      @Inject&#x000A;      Instance&lt;OrderProcessor&gt; instance;&#x000A;    &#x000A;      void create(Order order) {&#x000A;        if (instance.isResolvable()) {&#x000A;            instance.get().process(order);&#x000A;        } else {&#x000A;            // Log a warning or throw an exception&#x000A;        }&#x000A;      }&#x000A;    }</code></pre>
-                  </div>
-                  </div>
-                  <div class="paragraph">
-                  <p>Weld team is considering adding <code>org.jboss.weld.inject.WeldInstance</code> to the Weld API (2.4 and 3.0).
-                  <code>WeldInstance</code> would be automatically available in Weld SE and Weld Servlet where the Weld API is always on the class path.
-                  It would be 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 <code>provided</code> scope in Maven).</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>See also <a href="https://issues.jboss.org/browse/WELD-2151" target="_blank" rel="noopener">WELD-2151</a> and the work in progress: <a href="https://github.com/mkouba/core/tree/WELD-2151" class="bare">https://github.com/mkouba/core/tree/WELD-2151</a>.
-                  And feel free to add comments to this blog post.
-                  Any feedback is appreciated!</p>
-                  </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>
+              <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/19.html" class="page-link">19</a> <a href="/news/page/20.html" class="page-link">20</a> <a href="/news/page/14.html" class="next-link">Next</a> </div>
               <hr>
               <div>
                 <a href="http://weld.cdi-spec.org/news.atom">
diff --git a/news/page/14.html b/news/page/14.html
index a92a627d..cd6e61f3 100644
--- a/news/page/14.html
+++ b/news/page/14.html
@@ -141,6 +141,105 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2016/05/18/enhanced-instance/">Programmatic lookup improvements</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2016-5-18
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/api">api</a>
+                    ,
+                    <a href="/news/tags/draft">draft</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Martin Kouba
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p><code>javax.enterprise.inject.Instance</code> is sometimes invaluable companion.
+                  For example, <code>Instance</code> allows you to handle unsatisfied and ambiguous dependencies gracefully.
+                  E.g. it&#8217;s possible to avoid unnecessary deployment problems:</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">interface OrderProcessor {&#x000A;      void process(Order order);&#x000A;      int getPriority();&#x000A;    }&#x000A;    &#x000A;    class OrderService {&#x000A;    &#x000A;      @Inject&#x000A;      Instance&lt;OrderProcessor&gt; instance;&#x000A;    &#x000A;      void create(Order order) {&#x000A;        if (!instance.isUnsatisfied() &amp;&amp; !instance.isAmbiguous()) {&#x000A;            instance.get().process(order);&#x000A;        } else {&#x000A;            // Log a warning or throw an exception&#x000A;        }&#x000A;      }&#x000A;    }</code></pre>
+                  </div>
+                  </div>
+                  <div class="paragraph">
+                  <p>It is less known that <code>Instance</code> extends <code>Iterable</code> and so it allows to iterate through contextual references of beans with the specified combination of required type and qualifiers.
+                  This might be useful if the set of beans satisfying the given type and qualifiers is not known beforehand.
+                  We may also need to resolve ambiguities manually, e.g. inspect all the instances and choose only those matching our needs.</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@ApplicationScoped&#x000A;    class OrderService {&#x000A;    &#x000A;      @Inject&#x000A;      @Any&#x000A;      Instance&lt;OrderProcessor&gt; instance;&#x000A;    &#x000A;      void create(Order order) {&#x000A;        for (OrderProcessor processor : instance) {&#x000A;            if (processor.getPriority() &gt; 10) {&#x000A;                processor.process(order);&#x000A;            }&#x000A;        }&#x000A;      }&#x000A;    }</code></pre>
+                  </div>
+                  </div>
+                  <div class="paragraph">
+                  <p>Another interesting use case might be selecting exactly one implementation:</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@ApplicationScoped&#x000A;    class OrderService {&#x000A;    &#x000A;      @Inject&#x000A;      @Any&#x000A;      Instance&lt;OrderProcessor&gt; instance;&#x000A;    &#x000A;      void create(Order order) {&#x000A;        List&lt;OrderProcessor&gt; processors = new ArrayList&lt;&gt;();&#x000A;        for (OrderProcessor processor : instance) {&#x000A;            processors.add(processor);&#x000A;        }&#x000A;        Collections.sort(processors, Comparator.&lt;OrderProcessor&gt; comparingInt(p -&gt; p.getPriority()).reversed());&#x000A;        // Use the processor with highest priority&#x000A;        processors.get(0).ping();&#x000A;      }&#x000A;    }</code></pre>
+                  </div>
+                  </div>
+                  <div class="paragraph">
+                  <p>This works nice.
+                  But we have to pay extra attention to the scopes.
+                  If a <code>Processor</code> implementation is <code>@Dependent</code> a similar usage results in memory leaks.
+                  What&#8217;s the reason?
+                  The <code>Processor</code> instance is the dependent object of <code>Instance&lt;OrderProcessor&gt;</code> which is the dependent object of <code>OrderService</code>.
+                  And so each <code>Instance.get()</code> will produce a new <code>Processor</code> bound to the lifecycle of the <code>OrderService</code>.
+                  To avoid the leak we should always call <code>Instance.destroy()</code> method in similar cases.
+                  However, <code>Instance.destroy()</code> always destroys the underlying contextual instance!
+                  Even if you pass e.g. a client proxy of an <code>@ApplicationScoped</code> bean.
+                  This is not always desirable.
+                  Currently, it&#8217;s quite complicated to detect a dependent bean inside the loop.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>To extend the possibilities the Weld team is experimenting with <code>org.jboss.weld.inject.WeldInstance</code> - an enhanced version of <code>javax.enterprise.inject.Instance</code>.
+                  There are three new methods we find useful. The first one - <code>getHandler()</code> - allows to obtain a contextual reference handler which not only holds the contextual reference but also allows to inspect the metadata of the relevant bean and to destroy the underlying contextual instance.
+                  Moreover, the handler implements <code>AutoCloseable</code>:</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">import org.jboss.weld.inject.WeldInstance;&#x000A;    &#x000A;    class Foo {&#x000A;    &#x000A;      @Inject&#x000A;      WeldInstance&lt;Bar&gt; instance;&#x000A;    &#x000A;      void doWork() {&#x000A;        try (Handler&lt;Bar&gt; bar = instance.getHandler()) {&#x000A;            bar.get().doBusiness();&#x000A;            // Note that Bar will be automatically destroyed at the end of the try-with-resources statement&#x000A;        }&#x000A;    &#x000A;        Handler&lt;Bar&gt; bar = instance.getHandler()&#x000A;        bar.get().doBusiness();&#x000A;        // Calls Instance.destroy()&#x000A;        bar.destroy();&#x000A;      }&#x000A;    &#x000A;    }</code></pre>
+                  </div>
+                  </div>
+                  <div class="paragraph">
+                  <p>The next method - <code>handlerIterator()</code> - returns an iterator over contextual reference handlers. This might be useful if you need more control over contextual references inside the loop:</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@ApplicationScoped&#x000A;    class OrderService {&#x000A;    &#x000A;      @Inject&#x000A;      @Any&#x000A;      WeldInstance&lt;OrderProcessor&gt; instance;&#x000A;    &#x000A;      void create(Order order) {&#x000A;        for (Iterator&lt;Handler&lt;OrderProcessor&gt;&gt; iterator = instance.handlerIterator(); iterator.hasNext();) {&#x000A;                Handler&lt;OrderProcessor&gt; processor = iterator.next();&#x000A;                processor.get().process(order);&#x000A;                if (processor.getBean().getScope().equals(Dependent.class)) {&#x000A;                    // Destroy only dependent processors&#x000A;                    processor.destroy();&#x000A;                }&#x000A;            }&#x000A;      }&#x000A;    }</code></pre>
+                  </div>
+                  </div>
+                  <div class="paragraph">
+                  <p>The last one is just a convenient method - <code>isResolvable()</code> - a replacement for <code>!isUnsatisfied() &amp;&amp; !isAmbiguous()</code> which is the expression most users are interested in:</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">class OrderService {&#x000A;    &#x000A;      @Inject&#x000A;      Instance&lt;OrderProcessor&gt; instance;&#x000A;    &#x000A;      void create(Order order) {&#x000A;        if (instance.isResolvable()) {&#x000A;            instance.get().process(order);&#x000A;        } else {&#x000A;            // Log a warning or throw an exception&#x000A;        }&#x000A;      }&#x000A;    }</code></pre>
+                  </div>
+                  </div>
+                  <div class="paragraph">
+                  <p>Weld team is considering adding <code>org.jboss.weld.inject.WeldInstance</code> to the Weld API (2.4 and 3.0).
+                  <code>WeldInstance</code> would be automatically available in Weld SE and Weld Servlet where the Weld API is always on the class path.
+                  It would be 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 <code>provided</code> scope in Maven).</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>See also <a href="https://issues.jboss.org/browse/WELD-2151" target="_blank" rel="noopener">WELD-2151</a> and the work in progress: <a href="https://github.com/mkouba/core/tree/WELD-2151" class="bare">https://github.com/mkouba/core/tree/WELD-2151</a>.
+                  And feel free to add comments to this blog post.
+                  Any feedback is appreciated!</p>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2016/04/28/weld-300Alpha16/">Weld 3.0.0.Alpha16</a>
@@ -568,60 +667,7 @@ <h2 id="_wildfly_patch">WildFly Patch</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2016/02/08/weld-se-synth-lifecycle-events/">Weld SE and synthetic container lifecycle event observers</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2016-2-8
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/api">api</a>
-                    ,
-                    <a href="/news/tags/draft">draft</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Martin Kouba
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>Last week Weld 3.0.0.Alpha15 was released and so it&#8217;s time to reveal the features that should go into the next experimental release.
-                  The main goal of Weld 3.0.0.Alpha16 is to reflect the output of <a href="https://issues.jboss.org/browse/CDI-558">CDI-558</a>.
-                  However, we would also like to continue to deliver experimental prototypes so that users could test a new functionality (that we find interesting and useful) and the CDI EG could eventually include this into CDI 2.0.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>It should be easier to start playing with extensions in Weld SE. Right now, it&#8217;s possible to pass an <code>Extension</code> instance to the <code>Weld</code> builder so that it&#8217;s not necessary to configure service providers (i.e. <code>META-INF/services/javax.enterprise.inject.spi.Extension</code> file).
-                  In such case, the extension class is automatically scanned for observer methods and the instance is used as the receiver of the notifications.
-                  We would like to make this even easier.
-                  It is now possible to add a <strong>synthetic container lifecycle event observer</strong> without declaring an extension class.
-                  The observer logic is represented as a lambda expression.
-                  This might be especially useful for prototyping and/or for discovering how extensions work.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>The starting point is the <code>org.jboss.weld.environment.se.ContainerLifecycleObserver</code> class.
-                  There are few static methods, each corresponding to a specific container lifecycle event (e.g. <code>beforeBeanDiscovery()</code>).
-                  Some variants return a builder so that it&#8217;s possible to customize the observer (observed type, priority, etc.).
-                  Others accept a lambda and return an observer instance direcly.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>A synthetic observer may be added to the builder directly - see <code>Weld.addContainerLifecycleObserver()</code> - or grouped in a synthetic extension - see <code>ContainerLifecycleObserver.extensionBuilder()</code>.</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">Extension testExtension = ContainerLifecycleObserver.extensionBuilder()&#x000A;        .add(afterBeanDiscovery((e) -&gt; System.out.println("Bean discovery completed!")))&#x000A;        .add(processAnnotatedType().notify((e) -&gt; {&#x000A;                if (e.getAnnotatedType().getJavaClass().getName().startsWith("com.foo")) {&#x000A;                    e.veto();&#x000A;                }&#x000A;            })).build();&#x000A;    &#x000A;    try (WeldContainer container = new Weld().addExtension(testExtension).initialize()) {&#x000A;        // Use the container...&#x000A;    }</code></pre>
-                  </div>
-                  </div>
-                  <div class="paragraph">
-                  <p>This feature is merged in the master branch. If you want to try it out, you&#8217;ll have to use a <strong>3.0.0-SNAPSHOT</strong> version or build the Weld from source: <code>mvn clean install</code>.
-                  Do you find it useful? Any feedback is appreciated! Feel free to add comments to this blog post or to the corresponding issue: <a href="https://issues.jboss.org/browse/WELD-2102">WELD-2012</a>.</p>
-                  </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>
+              <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/19.html" class="page-link">19</a> <a href="/news/page/20.html" class="page-link">20</a> <a href="/news/page/15.html" class="next-link">Next</a> </div>
               <hr>
               <div>
                 <a href="http://weld.cdi-spec.org/news.atom">
diff --git a/news/page/15.html b/news/page/15.html
index 9784c6ca..aebf4199 100644
--- a/news/page/15.html
+++ b/news/page/15.html
@@ -141,6 +141,59 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2016/02/08/weld-se-synth-lifecycle-events/">Weld SE and synthetic container lifecycle event observers</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2016-2-8
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/api">api</a>
+                    ,
+                    <a href="/news/tags/draft">draft</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Martin Kouba
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>Last week Weld 3.0.0.Alpha15 was released and so it&#8217;s time to reveal the features that should go into the next experimental release.
+                  The main goal of Weld 3.0.0.Alpha16 is to reflect the output of <a href="https://issues.jboss.org/browse/CDI-558">CDI-558</a>.
+                  However, we would also like to continue to deliver experimental prototypes so that users could test a new functionality (that we find interesting and useful) and the CDI EG could eventually include this into CDI 2.0.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>It should be easier to start playing with extensions in Weld SE. Right now, it&#8217;s possible to pass an <code>Extension</code> instance to the <code>Weld</code> builder so that it&#8217;s not necessary to configure service providers (i.e. <code>META-INF/services/javax.enterprise.inject.spi.Extension</code> file).
+                  In such case, the extension class is automatically scanned for observer methods and the instance is used as the receiver of the notifications.
+                  We would like to make this even easier.
+                  It is now possible to add a <strong>synthetic container lifecycle event observer</strong> without declaring an extension class.
+                  The observer logic is represented as a lambda expression.
+                  This might be especially useful for prototyping and/or for discovering how extensions work.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>The starting point is the <code>org.jboss.weld.environment.se.ContainerLifecycleObserver</code> class.
+                  There are few static methods, each corresponding to a specific container lifecycle event (e.g. <code>beforeBeanDiscovery()</code>).
+                  Some variants return a builder so that it&#8217;s possible to customize the observer (observed type, priority, etc.).
+                  Others accept a lambda and return an observer instance direcly.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>A synthetic observer may be added to the builder directly - see <code>Weld.addContainerLifecycleObserver()</code> - or grouped in a synthetic extension - see <code>ContainerLifecycleObserver.extensionBuilder()</code>.</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">Extension testExtension = ContainerLifecycleObserver.extensionBuilder()&#x000A;        .add(afterBeanDiscovery((e) -&gt; System.out.println("Bean discovery completed!")))&#x000A;        .add(processAnnotatedType().notify((e) -&gt; {&#x000A;                if (e.getAnnotatedType().getJavaClass().getName().startsWith("com.foo")) {&#x000A;                    e.veto();&#x000A;                }&#x000A;            })).build();&#x000A;    &#x000A;    try (WeldContainer container = new Weld().addExtension(testExtension).initialize()) {&#x000A;        // Use the container...&#x000A;    }</code></pre>
+                  </div>
+                  </div>
+                  <div class="paragraph">
+                  <p>This feature is merged in the master branch. If you want to try it out, you&#8217;ll have to use a <strong>3.0.0-SNAPSHOT</strong> version or build the Weld from source: <code>mvn clean install</code>.
+                  Do you find it useful? Any feedback is appreciated! Feel free to add comments to this blog post or to the corresponding issue: <a href="https://issues.jboss.org/browse/WELD-2102">WELD-2012</a>.</p>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2016/02/04/weld-300Alpha15/">Weld 3.0.0.Alpha15</a>
@@ -363,141 +416,7 @@ <h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2015/11/10/weld-probe-jmx/">Weld development mode and JMX support</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2015-11-10
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/probe">probe</a>
-                    ,
-                    <a href="/news/tags/jmx">jmx</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Martin Kouba
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>Weld comes with a special mode for application development.
-                  When enabled, some interesting data are collected so that it&#8217;s possible to inspect and monitor application components at runtime.
-                  Data in JSON format are available through the REST API,  eventually through the MXBean of name <code>org.jboss.weld.probe:type=JsonData,context=ID</code> where ID should be replaced with an identifier of an application.
-                  The JMX support might be especially useful for environments and applications which do not utilize a web container (Java SE, OSGi, etc.).</p>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_how_to_enable_jmx_support">How to enable JMX support</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>Simply use the <a href="http://docs.jboss.org/weld/reference/latest/en-US/html/configure.html#_weld_configuration">Weld configuration facility</a> and <code>org.jboss.weld.probe.jmxSupport</code> configuration property. If set to <code>true</code> one or more MBean components may be registered so that it is possible to use JMX to access the Probe development tool data.</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_jmx_client">JMX client</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>So for example if using Weld SE without a web container it&#8217;s still possible to access the Probe data.
-                  There is a lot of JMX clients out there (for example jconsole or jvisualvm from the Oracle JDK).
-                  The problem is not all of us prefer reading JSON data.
-                  Hey wait! Weld Probe already has an HTML client, right?
-                  Yes, but this client works with REST API.
-                  We would have to embed a web container (e.g. Undertow) and add Weld Servlet or do some configuration manually.
-                  But what if there are multiple Weld instances in the same JVM? The configuration might become quite complex.
-                  Luckily, there is another solution - a <strong>working prototype</strong> of <a href="https://github.com/weld/weld-probe-jmx">JMX client reusing the default HTML GUI</a>.</p>
-                  </div>
-                  <div class="sect2">
-                  <h3 id="_clone_build_and_run">Clone, build and run</h3>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code>    # Clone the git repo&#x000A;        git clone git@github.com:weld/weld-probe-jmx.git&#x000A;        # Specify the weld version used in your application and run the build&#x000A;        mvn clean package -Dversion.weld=2.3.1.Final&#x000A;        # Run the client&#x000A;        java -jar target/weld-probe-jmx-1.0.0-SNAPSHOT-shaded.jar</code></pre>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect2">
-                  <h3 id="_how_does_it_work">How does it work?</h3>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>First, the client attempts to connect to a JMX server (your application)</p>
-                  </li>
-                  <li>
-                  <p>User may select a Weld container to inspect</p>
-                  </li>
-                  <li>
-                  <p>Then the client starts an Undertow instance locally, HTML client is available at: <a href="http://127.0.0.1:8181/probe-jmx/weld-probe" class="bare">http://127.0.0.1:8181/probe-jmx/weld-probe</a></p>
-                  </li>
-                  <li>
-                  <p>Data are fetched remotely through JMX</p>
-                  </li>
-                  <li>
-                  <p>User may reconnect at any time</p>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>See also the JBoss Forge example below to see an example output.</p>
-                  </div>
-                  </div>
-                  <div class="sect2">
-                  <h3 id="_configuration">Configuration</h3>
-                  <div class="paragraph">
-                  <p>Moreover, it&#8217;s also possible to configure the JMX server URL, Undertow host and port - used to expose the HTML client. E.g. for WildFly (standalone mode) a different jmxServiceUrl must be specified and jboss-client.jar must be also on the class path, e.g.:</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code>java -Dorg.jboss.weld.probe.jmxServiceUrl="service:jmx:http-remoting-jmx://127.0.0.1:9990" -cp '/opt/jboss/wildfly/bin/client/jboss-client.jar:target/weld-probe-jmx-1.0.0-SNAPSHOT-shaded.jar' org.jboss.weld.probe.ProbeJmx</code></pre>
-                  </div>
-                  </div>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_jboss_forge_example">JBoss Forge example</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>An interesting use case would be to inspect JBoss Forge addons powered by CDI (works with <strong>Forge 2.20.1.Final</strong> and later).
-                  Before we start Forge we need to set some extra system properties:</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code>export FORGE_OPTS="-Dorg.jboss.weld.development=true -Dorg.jboss.weld.probe.jmxSupport=true -Dorg.jboss.weld.probe.eventMonitor.containerLifecycleEvents=true -Dcom.sun.management.jmxremote.port=9999 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false"</code></pre>
-                  </div>
-                  </div>
-                  <div class="paragraph">
-                  <p>System properties starting with <code>com.sun.management</code> simply allow to connect to JMX remotely.
-                  <code>org.jboss.weld.development</code> enables the development mode.
-                  <code>org.jboss.weld.probe.jmxSupport</code> enables the JMX support.
-                  Finally, If <code>org.jboss.weld.probe.eventMonitor.containerLifecycleEvents</code> is set to <code>true</code> all the container lifecycle events are monitored during bootstrap.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Then start the Forge as usually and run the prototype. You should see a similar output:</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre>Connecting to a remote JMX server: service:jmx:rmi:///jndi/rmi://127.0.0.1:9999/jmxrmi&#x000A;    Select a Weld container (JSON data provider):&#x000A;    [0] org.jboss.weld.probe:type=JsonData,context="org.jboss.forge.addon:shell_1447145001728"&#x000A;    [1] org.jboss.weld.probe:type=JsonData,context="org.jboss.forge.addon:configuration_1447145001592"&#x000A;    [2] org.jboss.weld.probe:type=JsonData,context="org.jboss.forge.addon:parser-java_1447145002037"&#x000A;    [3] org.jboss.weld.probe:type=JsonData,context="org.jboss.forge.addon:bean-validation_1447145001526"&#x000A;    [4] org.jboss.weld.probe:type=JsonData,context="org.jboss.forge.addon:javaee_1447145003135"&#x000A;    [5] org.jboss.weld.probe:type=JsonData,context="org.jboss.forge.addon:ui_1447145001709"&#x000A;    [6] org.jboss.weld.probe:type=JsonData,context="org.jboss.forge.addon:convert_1447145001526"&#x000A;    &#x000A;    [disconnected]$</pre>
-                  </div>
-                  </div>
-                  <div class="paragraph">
-                  <p>Now select a Weld container to inspect, e.g. <code>5</code>:</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre>[disconnected]$ 5&#x000A;    Connecting to the Weld container [5]: org.jboss.weld.probe:type=JsonData,context="org.jboss.forge.addon:ui_1447145001709"&#x000A;    Starting Undertow...&#x000A;    Lis 10, 2015 9:44:16 DOP. org.xnio.Xnio &lt;clinit&gt;&#x000A;    INFO: XNIO version 3.3.1.Final&#x000A;    Lis 10, 2015 9:44:16 DOP. org.xnio.nio.NioXnio &lt;clinit&gt;&#x000A;    INFO: XNIO NIO Implementation Version 3.3.1.Final&#x000A;    Weld Probe HTML client available at: http://127.0.0.1:8181/probe-jmx/weld-probe&#x000A;    &#x000A;    [connected #5]$</pre>
-                  </div>
-                  </div>
-                  <div class="paragraph">
-                  <p>The HTML client is available at <a href="http://127.0.0.1:8181/probe-jmx/weld-probe" class="bare">http://127.0.0.1:8181/probe-jmx/weld-probe</a>. It&#8217;s also possible to reconnect or exit. Type <code>help</code> to get a list of all possible commands.</p>
-                  </div>
-                  </div>
-                  </div>
-                </div>
-                <hr>
-              </div>
-              <div class="pagination-links"><a href="/news/page/14.html" class="previous-link">Previous</a> <a href="/news/" class="page-link">1</a> <a href="/news/page/2.html" class="page-link">2</a> <span class="skip">...</span><a href="/news/page/14.html" class="page-link">14</a> <span class="current-page">15</span> <a href="/news/page/16.html" class="page-link">16</a> <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>
+              <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/19.html" class="page-link">19</a> <a href="/news/page/20.html" class="page-link">20</a> <a href="/news/page/16.html" class="next-link">Next</a> </div>
               <hr>
               <div>
                 <a href="http://weld.cdi-spec.org/news.atom">
diff --git a/news/page/16.html b/news/page/16.html
index bca7b9ab..d28659c1 100644
--- a/news/page/16.html
+++ b/news/page/16.html
@@ -141,6 +141,140 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2015/11/10/weld-probe-jmx/">Weld development mode and JMX support</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2015-11-10
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/probe">probe</a>
+                    ,
+                    <a href="/news/tags/jmx">jmx</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Martin Kouba
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>Weld comes with a special mode for application development.
+                  When enabled, some interesting data are collected so that it&#8217;s possible to inspect and monitor application components at runtime.
+                  Data in JSON format are available through the REST API,  eventually through the MXBean of name <code>org.jboss.weld.probe:type=JsonData,context=ID</code> where ID should be replaced with an identifier of an application.
+                  The JMX support might be especially useful for environments and applications which do not utilize a web container (Java SE, OSGi, etc.).</p>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_how_to_enable_jmx_support">How to enable JMX support</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>Simply use the <a href="http://docs.jboss.org/weld/reference/latest/en-US/html/configure.html#_weld_configuration">Weld configuration facility</a> and <code>org.jboss.weld.probe.jmxSupport</code> configuration property. If set to <code>true</code> one or more MBean components may be registered so that it is possible to use JMX to access the Probe development tool data.</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_jmx_client">JMX client</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>So for example if using Weld SE without a web container it&#8217;s still possible to access the Probe data.
+                  There is a lot of JMX clients out there (for example jconsole or jvisualvm from the Oracle JDK).
+                  The problem is not all of us prefer reading JSON data.
+                  Hey wait! Weld Probe already has an HTML client, right?
+                  Yes, but this client works with REST API.
+                  We would have to embed a web container (e.g. Undertow) and add Weld Servlet or do some configuration manually.
+                  But what if there are multiple Weld instances in the same JVM? The configuration might become quite complex.
+                  Luckily, there is another solution - a <strong>working prototype</strong> of <a href="https://github.com/weld/weld-probe-jmx">JMX client reusing the default HTML GUI</a>.</p>
+                  </div>
+                  <div class="sect2">
+                  <h3 id="_clone_build_and_run">Clone, build and run</h3>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code>    # Clone the git repo&#x000A;        git clone git@github.com:weld/weld-probe-jmx.git&#x000A;        # Specify the weld version used in your application and run the build&#x000A;        mvn clean package -Dversion.weld=2.3.1.Final&#x000A;        # Run the client&#x000A;        java -jar target/weld-probe-jmx-1.0.0-SNAPSHOT-shaded.jar</code></pre>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect2">
+                  <h3 id="_how_does_it_work">How does it work?</h3>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>First, the client attempts to connect to a JMX server (your application)</p>
+                  </li>
+                  <li>
+                  <p>User may select a Weld container to inspect</p>
+                  </li>
+                  <li>
+                  <p>Then the client starts an Undertow instance locally, HTML client is available at: <a href="http://127.0.0.1:8181/probe-jmx/weld-probe" class="bare">http://127.0.0.1:8181/probe-jmx/weld-probe</a></p>
+                  </li>
+                  <li>
+                  <p>Data are fetched remotely through JMX</p>
+                  </li>
+                  <li>
+                  <p>User may reconnect at any time</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>See also the JBoss Forge example below to see an example output.</p>
+                  </div>
+                  </div>
+                  <div class="sect2">
+                  <h3 id="_configuration">Configuration</h3>
+                  <div class="paragraph">
+                  <p>Moreover, it&#8217;s also possible to configure the JMX server URL, Undertow host and port - used to expose the HTML client. E.g. for WildFly (standalone mode) a different jmxServiceUrl must be specified and jboss-client.jar must be also on the class path, e.g.:</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code>java -Dorg.jboss.weld.probe.jmxServiceUrl="service:jmx:http-remoting-jmx://127.0.0.1:9990" -cp '/opt/jboss/wildfly/bin/client/jboss-client.jar:target/weld-probe-jmx-1.0.0-SNAPSHOT-shaded.jar' org.jboss.weld.probe.ProbeJmx</code></pre>
+                  </div>
+                  </div>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_jboss_forge_example">JBoss Forge example</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>An interesting use case would be to inspect JBoss Forge addons powered by CDI (works with <strong>Forge 2.20.1.Final</strong> and later).
+                  Before we start Forge we need to set some extra system properties:</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code>export FORGE_OPTS="-Dorg.jboss.weld.development=true -Dorg.jboss.weld.probe.jmxSupport=true -Dorg.jboss.weld.probe.eventMonitor.containerLifecycleEvents=true -Dcom.sun.management.jmxremote.port=9999 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false"</code></pre>
+                  </div>
+                  </div>
+                  <div class="paragraph">
+                  <p>System properties starting with <code>com.sun.management</code> simply allow to connect to JMX remotely.
+                  <code>org.jboss.weld.development</code> enables the development mode.
+                  <code>org.jboss.weld.probe.jmxSupport</code> enables the JMX support.
+                  Finally, If <code>org.jboss.weld.probe.eventMonitor.containerLifecycleEvents</code> is set to <code>true</code> all the container lifecycle events are monitored during bootstrap.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Then start the Forge as usually and run the prototype. You should see a similar output:</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre>Connecting to a remote JMX server: service:jmx:rmi:///jndi/rmi://127.0.0.1:9999/jmxrmi&#x000A;    Select a Weld container (JSON data provider):&#x000A;    [0] org.jboss.weld.probe:type=JsonData,context="org.jboss.forge.addon:shell_1447145001728"&#x000A;    [1] org.jboss.weld.probe:type=JsonData,context="org.jboss.forge.addon:configuration_1447145001592"&#x000A;    [2] org.jboss.weld.probe:type=JsonData,context="org.jboss.forge.addon:parser-java_1447145002037"&#x000A;    [3] org.jboss.weld.probe:type=JsonData,context="org.jboss.forge.addon:bean-validation_1447145001526"&#x000A;    [4] org.jboss.weld.probe:type=JsonData,context="org.jboss.forge.addon:javaee_1447145003135"&#x000A;    [5] org.jboss.weld.probe:type=JsonData,context="org.jboss.forge.addon:ui_1447145001709"&#x000A;    [6] org.jboss.weld.probe:type=JsonData,context="org.jboss.forge.addon:convert_1447145001526"&#x000A;    &#x000A;    [disconnected]$</pre>
+                  </div>
+                  </div>
+                  <div class="paragraph">
+                  <p>Now select a Weld container to inspect, e.g. <code>5</code>:</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre>[disconnected]$ 5&#x000A;    Connecting to the Weld container [5]: org.jboss.weld.probe:type=JsonData,context="org.jboss.forge.addon:ui_1447145001709"&#x000A;    Starting Undertow...&#x000A;    Lis 10, 2015 9:44:16 DOP. org.xnio.Xnio &lt;clinit&gt;&#x000A;    INFO: XNIO version 3.3.1.Final&#x000A;    Lis 10, 2015 9:44:16 DOP. org.xnio.nio.NioXnio &lt;clinit&gt;&#x000A;    INFO: XNIO NIO Implementation Version 3.3.1.Final&#x000A;    Weld Probe HTML client available at: http://127.0.0.1:8181/probe-jmx/weld-probe&#x000A;    &#x000A;    [connected #5]$</pre>
+                  </div>
+                  </div>
+                  <div class="paragraph">
+                  <p>The HTML client is available at <a href="http://127.0.0.1:8181/probe-jmx/weld-probe" class="bare">http://127.0.0.1:8181/probe-jmx/weld-probe</a>. It&#8217;s also possible to reconnect or exit. Type <code>help</code> to get a list of all possible commands.</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2015/10/27/weld-231Final/">Weld 2.3.1.Final arrives...</a>
@@ -374,190 +508,7 @@ <h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2015/08/05/weld-300Alpha12/">Weld 3.0.0.Alpha12 - CDI 2.0 EDR1 Reference Implementation!</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2015-8-5
-                  &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.Alpha12 has been released. Compared to previous alpha releases this is an important milestone - it&#8217;s a reference implementation of <a href="http://docs.jboss.org/cdi/spec/2.0.EDR1/cdi-spec.html">CDI 2.0 Early Draft</a> (EDR1). You can read more about CDI 2.0 EDR1 on the official blog: <a href="http://www.cdi-spec.org/news/2015/07/03/CDI-2_0-EDR1-released/">CDI 2.0 Early Draft Review 1 released</a>.</p>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_bootstrapping_a_cdi_container_in_java_se">Bootstrapping a CDI container in Java SE</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>Starting a CDI container is now really that easy:</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">public static void main(String... args) {&#x000A;        try(CDI&lt;Object&gt; cdi = CDI.getCDIProvider().initialize()) {&#x000A;            ComputingService service = cdi.select(ComputingService.class).get();&#x000A;            service.compute();&#x000A;        }&#x000A;    }</code></pre>
-                  </div>
-                  </div>
-                  <div class="paragraph">
-                  <p><code>javax.enterprise.inject.spi.CDI</code> now implements <code>AutoCloseable</code> and can therefore be used in a <code>try-with-resources</code> block.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Note that the specification of the bean discovery process in Java SE is not finished yet. Therefore, bean archives which don&#8217;t contain a beans.xml file are not supported. The main reason is that we don&#8217;t want to implement a feature which is being discussed and will likely undergo some important changes. Nevertheless, the feature will be implemented in one of the next alpha versions.</p>
-                  </div>
-                  <div class="sect2">
-                  <h3 id="_weld_se_bootstrap_api">Weld SE bootstrap API</h3>
-                  <div class="paragraph">
-                  <p>How does it compare to Weld SE bootstrap API? Weld has provided support for the Java SE environment for a long time. Recently, the <code>org.jboss.weld.environment.se.Weld</code> class was turned into a powerful builder which allows to configure the Weld container before it is initialized.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Typical usage of the Weld SE API looks like this:</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">try (WeldContainer container = new Weld().initialize()) {&#x000A;        ComputingService service = container.select(ComputingService.class).get();&#x000A;        service.compute();&#x000A;    }</code></pre>
-                  </div>
-                  </div>
-                  <div class="paragraph">
-                  <p>This looks very similar to CDI SE, right? However, there are several advanced feratures available:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>automatic scanning can be disabled, classes or packages can be selected explicitly</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p><code>WeldContainer container = new Weld().disableDiscovery().beanClasses(Foo.class, Bar.class).alternatives(Bar.class).interceptors(FooInterceptor.class).initialize();</code></p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>WeldContainer allows to fire events easily</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p><code>container.event().select(Bar.class).fire(new Bar());</code></p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Weld-specific <a href="http://docs.jboss.org/weld/reference/latest/en-US/html/configure.html#_weld_configuration">configuration options</a> can be specified using the builder</p>
-                  </li>
-                  <li>
-                  <p>it is possible to start multiple independent Weld instances (specification does not require this)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>See also <a href="http://weld.cdi-spec.org/news/2015/04/21/weld-300Alpha8/">Weld 3.0.0.Alpha8 announcement</a> for more information.</p>
-                  </div>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_asynchronous_events">Asynchronous Events</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>An experimental support of asynchronous events is implemented in Weld since 3.0.0.Alpha3. However, in this release the API was aligned with CDI 2.0 EDR1:</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">class OrderProcessor {&#x000A;    &#x000A;        @Inject Event&lt;Order&gt; orderEvent;&#x000A;    &#x000A;        public void process(Order order) {&#x000A;            orderEvent.fireAsync(order).thenAccept((o)-&gt;System.out.println("Asynchronous processing finished: " + o.getId()));&#x000A;        }&#x000A;    &#x000A;        public void processingOrder(@Observes Order event) {&#x000A;            // This observer is notified synchronously, before the fireAsync() method returns&#x000A;        }&#x000A;    &#x000A;        public void asyncProcessingOrder(@ObservesAsync Order event) {&#x000A;            // This observer is notified asynchronously, in a different thread&#x000A;        }&#x000A;    }</code></pre>
-                  </div>
-                  </div>
-                  <div class="paragraph">
-                  <p>There are few important things to notice:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>the event was triggered with <code>fireAsync()</code></p>
-                  </li>
-                  <li>
-                  <p>the asynchronous observer is defined by <code>@ObservesAsync</code></p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>this is required because of backward compatibilty with previous versions of CDI, see also <a href="http://www.cdi-spec.org/news/2015/07/03/CDI-2_0-EDR1-released/#_why_this_double_activation_is_needed">Why this double activation is needed?</a></p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>synchronous observers defined by <code>@Observes</code> are also notified!</p>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>To sum it up:</p>
-                  </div>
-                  <table class="tableblock frame-all grid-all stretch">
-                  <colgroup>
-                  <col style="width: 33.3333%;">
-                  <col style="width: 33.3333%;">
-                  <col style="width: 33.3334%;">
-                  </colgroup>
-                  <thead>
-                  <tr>
-                  <th class="tableblock halign-left valign-top">Event method</th>
-                  <th class="tableblock halign-left valign-top"><code>@Observes</code> notified</th>
-                  <th class="tableblock halign-left valign-top"><code>@ObservesAsync</code> notified</th>
-                  </tr>
-                  </thead>
-                  <tbody>
-                  <tr>
-                  <td class="tableblock halign-left valign-top"><p class="tableblock"><code>fire()</code></p></td>
-                  <td class="tableblock halign-left valign-top"><p class="tableblock">yes, in the same thread</p></td>
-                  <td class="tableblock halign-left valign-top"><p class="tableblock">no</p></td>
-                  </tr>
-                  <tr>
-                  <td class="tableblock halign-left valign-top"><p class="tableblock"><code>fireAsync()</code></p></td>
-                  <td class="tableblock halign-left valign-top"><p class="tableblock">yes, in the same thread</p></td>
-                  <td class="tableblock halign-left valign-top"><p class="tableblock">yes, in a different thread</p></td>
-                  </tr>
-                  </tbody>
-                  </table>
-                  <div class="sect2">
-                  <h3 id="_observers_spi_changes">Observers SPI Changes</h3>
-                  <div class="paragraph">
-                  <p><code>javax.enterprise.inject.spi.ObserverMethod</code> now extends <code>javax.enterprise.inject.spi.Prioritized</code> and overrides the <code>ObserverMethod.getPriority()</code> method which is used to determine the notification order in which the event observer methods are invoked. <code>Prioritized</code> interface is currently only used for observers. However, the Weld team is working on a prototype where <code>Prioritized</code> can be used to globally select/enable custom alternative beans, interceptors and decorators, see also <a href="https://issues.jboss.org/browse/WELD-2000">WELD-2000</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Furthermore, <code>ObserverMethod.isAsync()</code> method was added to determine whether an observer method is asynchronous or not.</p>
-                  </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.Alpha12/wildfly-10.0.0.Alpha6-weld-3.0.0.Alpha12-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.Alpha6</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=12327471">Release notes</a> &#93;
-                  &#91; <a href="http://download.jboss.org/weld/3.0.0.Alpha12/weld-3.0.0.Alpha12.zip">Distribution</a> &#93;
-                  &#91; <a href="http://download.jboss.org/weld/3.0.0.Alpha12/wildfly-10.0.0.Alpha6-weld-3.0.0.Alpha12-patch.zip">Patch for Wildfly 10 Alpha</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>
+              <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> <span class="skip">...</span><a href="/news/page/19.html" class="page-link">19</a> <a href="/news/page/20.html" class="page-link">20</a> <a href="/news/page/17.html" class="next-link">Next</a> </div>
               <hr>
               <div>
                 <a href="http://weld.cdi-spec.org/news.atom">
diff --git a/news/page/17.html b/news/page/17.html
index 5ffe1455..1fd72f74 100644
--- a/news/page/17.html
+++ b/news/page/17.html
@@ -141,6 +141,189 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2015/08/05/weld-300Alpha12/">Weld 3.0.0.Alpha12 - CDI 2.0 EDR1 Reference Implementation!</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2015-8-5
+                  &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.Alpha12 has been released. Compared to previous alpha releases this is an important milestone - it&#8217;s a reference implementation of <a href="http://docs.jboss.org/cdi/spec/2.0.EDR1/cdi-spec.html">CDI 2.0 Early Draft</a> (EDR1). You can read more about CDI 2.0 EDR1 on the official blog: <a href="http://www.cdi-spec.org/news/2015/07/03/CDI-2_0-EDR1-released/">CDI 2.0 Early Draft Review 1 released</a>.</p>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_bootstrapping_a_cdi_container_in_java_se">Bootstrapping a CDI container in Java SE</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>Starting a CDI container is now really that easy:</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">public static void main(String... args) {&#x000A;        try(CDI&lt;Object&gt; cdi = CDI.getCDIProvider().initialize()) {&#x000A;            ComputingService service = cdi.select(ComputingService.class).get();&#x000A;            service.compute();&#x000A;        }&#x000A;    }</code></pre>
+                  </div>
+                  </div>
+                  <div class="paragraph">
+                  <p><code>javax.enterprise.inject.spi.CDI</code> now implements <code>AutoCloseable</code> and can therefore be used in a <code>try-with-resources</code> block.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Note that the specification of the bean discovery process in Java SE is not finished yet. Therefore, bean archives which don&#8217;t contain a beans.xml file are not supported. The main reason is that we don&#8217;t want to implement a feature which is being discussed and will likely undergo some important changes. Nevertheless, the feature will be implemented in one of the next alpha versions.</p>
+                  </div>
+                  <div class="sect2">
+                  <h3 id="_weld_se_bootstrap_api">Weld SE bootstrap API</h3>
+                  <div class="paragraph">
+                  <p>How does it compare to Weld SE bootstrap API? Weld has provided support for the Java SE environment for a long time. Recently, the <code>org.jboss.weld.environment.se.Weld</code> class was turned into a powerful builder which allows to configure the Weld container before it is initialized.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Typical usage of the Weld SE API looks like this:</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">try (WeldContainer container = new Weld().initialize()) {&#x000A;        ComputingService service = container.select(ComputingService.class).get();&#x000A;        service.compute();&#x000A;    }</code></pre>
+                  </div>
+                  </div>
+                  <div class="paragraph">
+                  <p>This looks very similar to CDI SE, right? However, there are several advanced feratures available:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>automatic scanning can be disabled, classes or packages can be selected explicitly</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p><code>WeldContainer container = new Weld().disableDiscovery().beanClasses(Foo.class, Bar.class).alternatives(Bar.class).interceptors(FooInterceptor.class).initialize();</code></p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>WeldContainer allows to fire events easily</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p><code>container.event().select(Bar.class).fire(new Bar());</code></p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Weld-specific <a href="http://docs.jboss.org/weld/reference/latest/en-US/html/configure.html#_weld_configuration">configuration options</a> can be specified using the builder</p>
+                  </li>
+                  <li>
+                  <p>it is possible to start multiple independent Weld instances (specification does not require this)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>See also <a href="http://weld.cdi-spec.org/news/2015/04/21/weld-300Alpha8/">Weld 3.0.0.Alpha8 announcement</a> for more information.</p>
+                  </div>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_asynchronous_events">Asynchronous Events</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>An experimental support of asynchronous events is implemented in Weld since 3.0.0.Alpha3. However, in this release the API was aligned with CDI 2.0 EDR1:</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">class OrderProcessor {&#x000A;    &#x000A;        @Inject Event&lt;Order&gt; orderEvent;&#x000A;    &#x000A;        public void process(Order order) {&#x000A;            orderEvent.fireAsync(order).thenAccept((o)-&gt;System.out.println("Asynchronous processing finished: " + o.getId()));&#x000A;        }&#x000A;    &#x000A;        public void processingOrder(@Observes Order event) {&#x000A;            // This observer is notified synchronously, before the fireAsync() method returns&#x000A;        }&#x000A;    &#x000A;        public void asyncProcessingOrder(@ObservesAsync Order event) {&#x000A;            // This observer is notified asynchronously, in a different thread&#x000A;        }&#x000A;    }</code></pre>
+                  </div>
+                  </div>
+                  <div class="paragraph">
+                  <p>There are few important things to notice:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>the event was triggered with <code>fireAsync()</code></p>
+                  </li>
+                  <li>
+                  <p>the asynchronous observer is defined by <code>@ObservesAsync</code></p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>this is required because of backward compatibilty with previous versions of CDI, see also <a href="http://www.cdi-spec.org/news/2015/07/03/CDI-2_0-EDR1-released/#_why_this_double_activation_is_needed">Why this double activation is needed?</a></p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>synchronous observers defined by <code>@Observes</code> are also notified!</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>To sum it up:</p>
+                  </div>
+                  <table class="tableblock frame-all grid-all stretch">
+                  <colgroup>
+                  <col style="width: 33.3333%;">
+                  <col style="width: 33.3333%;">
+                  <col style="width: 33.3334%;">
+                  </colgroup>
+                  <thead>
+                  <tr>
+                  <th class="tableblock halign-left valign-top">Event method</th>
+                  <th class="tableblock halign-left valign-top"><code>@Observes</code> notified</th>
+                  <th class="tableblock halign-left valign-top"><code>@ObservesAsync</code> notified</th>
+                  </tr>
+                  </thead>
+                  <tbody>
+                  <tr>
+                  <td class="tableblock halign-left valign-top"><p class="tableblock"><code>fire()</code></p></td>
+                  <td class="tableblock halign-left valign-top"><p class="tableblock">yes, in the same thread</p></td>
+                  <td class="tableblock halign-left valign-top"><p class="tableblock">no</p></td>
+                  </tr>
+                  <tr>
+                  <td class="tableblock halign-left valign-top"><p class="tableblock"><code>fireAsync()</code></p></td>
+                  <td class="tableblock halign-left valign-top"><p class="tableblock">yes, in the same thread</p></td>
+                  <td class="tableblock halign-left valign-top"><p class="tableblock">yes, in a different thread</p></td>
+                  </tr>
+                  </tbody>
+                  </table>
+                  <div class="sect2">
+                  <h3 id="_observers_spi_changes">Observers SPI Changes</h3>
+                  <div class="paragraph">
+                  <p><code>javax.enterprise.inject.spi.ObserverMethod</code> now extends <code>javax.enterprise.inject.spi.Prioritized</code> and overrides the <code>ObserverMethod.getPriority()</code> method which is used to determine the notification order in which the event observer methods are invoked. <code>Prioritized</code> interface is currently only used for observers. However, the Weld team is working on a prototype where <code>Prioritized</code> can be used to globally select/enable custom alternative beans, interceptors and decorators, see also <a href="https://issues.jboss.org/browse/WELD-2000">WELD-2000</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Furthermore, <code>ObserverMethod.isAsync()</code> method was added to determine whether an observer method is asynchronous or not.</p>
+                  </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.Alpha12/wildfly-10.0.0.Alpha6-weld-3.0.0.Alpha12-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.Alpha6</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=12327471">Release notes</a> &#93;
+                  &#91; <a href="http://download.jboss.org/weld/3.0.0.Alpha12/weld-3.0.0.Alpha12.zip">Distribution</a> &#93;
+                  &#91; <a href="http://download.jboss.org/weld/3.0.0.Alpha12/wildfly-10.0.0.Alpha6-weld-3.0.0.Alpha12-patch.zip">Patch for Wildfly 10 Alpha</a>
+                  &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2015/04/21/weld-300Alpha8/">Weld 3.0.0.Alpha8</a>
@@ -862,193 +1045,7 @@ <h2 id="_whats_next">What’s next?</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2014/10/02/weld-300Alpha1/">Weld 3.0.0.Alpha1 released!</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2014-10-2
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Jozef Hartinger
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>Today we are releasing Weld 3.0.0.Alpha1. This release serves as an <strong>early proof of concept</strong> of some of the ideas that are being discussed by the CDI Expert Group for the upcoming
-                  <a href="http://cdi-spec.org/">CDI 2.0 specification</a>. Furthermore, this is a great opportunity for the community to test-drive some of the proposed improvements and <strong>provide us with feedback</strong>.
-                  Be warned though that this released does not come with any guarantee of stability and that binary and functional compatibility is likely to be broken in the following releases.</p>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_ordering_of_observer_methods">Ordering of observer methods</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>The first of the new features are ordered observer methods. This requirement came up a long ago and several approaches were proposed in the meantime, as documented by
-                  <a href="https://issues.jboss.org/browse/CDI-4">CDI-4</a>.The Alpha1 release employs the general-purpose <code>@Priority</code> annotation to determine the order in which observer methods are to be notified.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>There are many open questions about this feature. Here are some of the rules we set for the purpose of this experimental implementation. These are by no means set in stone but instead we encourage you
-                  to give us feedback on these:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Each observer method has a certain priority value. An observer method that does not define a priority explicitly is given the default priority which is 2500 (in the middle of the <code>Interceptor.Priority.APPLICATION</code> range)</p>
-                  </li>
-                  <li>
-                  <p>The priority of an observer method determines the order. An observer method with lower value is called before an observer method with higher value</p>
-                  </li>
-                  <li>
-                  <p>If multiple observer methods define the same priority value, the order is undefined</p>
-                  </li>
-                  <li>
-                  <p>Observer methods priorities should match <a href="https://javaee-spec.java.net/nonav/javadocs/javax/interceptor/Interceptor.Priority.html">existing priority range convention</a></p>
-                  </li>
-                  <li>
-                  <p>The ordering applies to both transactional and non-transactional observer methods</p>
-                  </li>
-                  <li>
-                  <p>The priority annotation is applied on the event parameter (not the observer method)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>Here’s an example:</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">public void sendWelcome(@Observes @Priority(APPLICATION + 800) @Registered User user) {&#x000A;        // ...&#x000A;    }</code></pre>
-                  </div>
-                  </div>
-                  <div class="paragraph">
-                  <p>Note that <code>javax.annotation.Priority</code> can currently only be applied to types. Therefore, we temporarily created a substitute called <strong><code>org.jboss.weld.experimental.Priority</code></strong> which is identical
-                  to the original except that it can also be applied on parameters (of observer methods). The plan is to propagate this change back to <code>javax.annotation.Priority</code>. In the meantime, Weld’s twin
-                  gets the job done.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>In addition to the <code>@Priority</code> annotation, the SPI was also enhanced to expose the priority of an observer method. We are not touching <code>javax.enterprise</code> interfaces just yet. Instead,
-                  the <code>org.jboss.weld.experimental</code> package contains proposals for how the new SPI should look like. As the package name suggests, this SPI is good for a test-drive but do not expect it to be stable.
-                  To use the experimental SPIs, you&#8217;ll need to add a dependency on <a href="http://search.maven.org/#artifactdetails%7Corg.jboss.weld%7Cweld-api%7C3.0.Alpha1%7Cjar">weld-api</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Here’s an example of reading the observer method priority using the SPI in an Extension. <code>ExperimentalProcessObserverMethod</code> and <code>ExperimentalObserverMethod</code> interfaces come from the
-                  <code>org.jboss.weld.experimental package</code>.</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">public class SimpleExtension implements Extension {&#x000A;    &#x000A;        void observe(@Observes ExperimentalProcessObserverMethod&lt;User, ?&gt; event) {&#x000A;            ExperimentalObserverMethod&lt;User&gt; observerMethod = event.getObserverMethod();&#x000A;            this.priority = observerMethod.getPriority();&#x000A;        }&#x000A;    }</code></pre>
-                  </div>
-                  </div>
-                  <div class="paragraph">
-                  <p>Use the <a href="https://issues.jboss.org/browse/CDI-4">corresponding CDI ticket</a> for any feedback on these features.</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_vetoing_and_modifying_observer_methods">Vetoing and modifying observer methods</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>We’ll stay with observer methods for a few more paragraphs. A <a href="https://issues.jboss.org/browse/CDI-458">request</a> was raised in the CDI issue tracker for making it possible to disable an
-                  observer method using the <code>ProcessObserverMethod</code> SPI.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>This Alpha1 release introduces the <code>veto()</code> methods (aligned with <code>ProcessAnnotatedType.veto()</code>) for this:</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">void disableDebuggingObservers(@Observes ExperimentalProcessObserverMethod&lt;?, Debug&gt; event) {&#x000A;        if (projectStage != ProjectStage.Development) {&#x000A;            event.veto();&#x000A;        }&#x000A;    }</code></pre>
-                  </div>
-                  </div>
-                  <div class="paragraph">
-                  <p>In addition, the observer method metadata may be altered by an extension. This is done similarly to how <code>InjectionTarget</code>, <code>InjectionPoint</code> or <code>BeanAttribute</code> metadata are modified which
-                  is most often by wrapping the original object (decorator design pattern). Any piece of metadata (including aforementioned priority) can be altered. For example, the transaction phase:</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">void alterObserver(@Observes ExperimentalProcessObserverMethod&lt;User, ?&gt; event) {&#x000A;        event.setObserverMethod(new ForwardingExperimentalObserverMethod&lt;User&gt;(event.getObserverMethod()) {&#x000A;            @Override&#x000A;            public TransactionPhase getTransactionPhase() {&#x000A;                return TransactionPhase.AFTER_SUCCESS;&#x000A;            }&#x000A;        });&#x000A;    }</code></pre>
-                  </div>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_repeatable_qualifiers_and_interceptor_bindings">Repeatable qualifiers and interceptor bindings</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>This release serves as a proof of concept for supporting repeating qualifiers and interceptor bindings. You can now fully utilize Java 8 features and use multiple qualifiers or interceptor bindings
-                  of the same type in the same location, for example:</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">public class School {&#x000A;    &#x000A;        @Produces&#x000A;        @Speaks("English")&#x000A;        @Speaks("French")&#x000A;        public Student graduate() {&#x000A;            // ...&#x000A;        }&#x000A;    }</code></pre>
-                  </div>
-                  </div>
-                  <div class="paragraph">
-                  <p>Repeating qualifiers can be used for both bean and event resolution. See the <a href="http://docs.oracle.com/javase/tutorial/java/annotations/repeating.html">Java documentation</a> for how to define
-                  a repeating annotation.</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_interceptor_bindings_in_invocation_context">Interceptor bindings in invocation context</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>This is an often recurring scenario. An interceptor binding defines several <code>@NonBinding</code> members which serve as configuration for the interceptor. How does an interceptor get hold of these values?
-                  This is not easy as the interceptor binding may often appear on the intercepted method, the class that defined it or may be inherited from another interceptor binding or stereotype (even transitively!).
-                  This problem gave birth to utilities such as
-                  <a href="https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;a=blob;f=deltaspike/core/api/src/main/java/org/apache/deltaspike/core/util/AnnotationUtils.java;h=9d4c8e2f72936facf1ef0d8d9655c4186965afde;hb=HEAD">this one</a>.
-                  Still, even after all this effort the result is not entirely correct as it was obtained using Java reflection ignoring the fact that the interceptor binding may have been modified
-                  (e.g. using <code>ProcessAnnotatedType</code>).</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>This problem is being addressed as <a href="https://issues.jboss.org/browse/CDI-468">CDI-468</a>. The Alpha1 release of Weld implements this feature and exposes new methods for obtaining interceptor bindings
-                  that are in effect for the interception. This is done using <code>ExperimentalInvocationContext.getInterceptorBindings()</code> or <code>ExperimentalInvocationContext.getInterceptorBindingsByType()</code>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Again, <code>ExperimentalInvocationContext</code> can be found in the <code>org.jboss.weld.experimental</code> package and depicts how the future version of <code>javax.interceptor.InvocationContext</code> could look like.</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@Interceptor&#x000A;    @Secure&#x000A;    public class SecurityInterceptor {&#x000A;    &#x000A;        @Inject&#x000A;        private User user;&#x000A;    &#x000A;        @AroundInvoke&#x000A;        public Object intercept(ExperimentalInvocationContext ctx) throws Exception {&#x000A;            Secure binding = ctx.getInterceptorBindingsByType(Secure.class).iterator().next();&#x000A;            if (!user.getRoles().contains(binding.requireRole())) {&#x000A;                throw new SecurityException();&#x000A;            }&#x000A;            return ctx.proceed();&#x000A;        }&#x000A;    }</code></pre>
-                  </div>
-                  </div>
-                  <div class="paragraph">
-                  <p>Again, your feedback is welcome at <a href="https://issues.jboss.org/browse/CDI-468">CDI-468</a>.</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_changes_in_the_annotated_layer">Changes in the Annotated layer</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>CDI provides an abstraction over the Reflection API - <a href="http://docs.jboss.org/cdi/api/1.2/javax/enterprise/inject/spi/Annotated.html">AnnotatedType and friends</a> - which mostly allows extensions
-                  to alter the set of annotations present on a type, field, method, etc.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>The Alpha1 release contains two minor additions to this API. Firstly, the API now supports Java 8 repeating annotations with a new method <code>ExperimentalAnnotated.getAnnotationsByType(Class&lt;T&gt; annotationClass)</code></p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Secondly, it is now possible to access the <code>java.lang.reflect.Parameter</code> instance that is wrapped by <code>AnnotatedParameter</code> using <code>ExperimentalAnnotatedParameter.getJavaParameter();</code></p>
-                  </div>
-                  <div class="paragraph">
-                  <p>See <a href="https://issues.jboss.org/browse/CDI-471">CDI-471</a> and <a href="https://issues.jboss.org/browse/CDI-481">CDI-481</a> for details.</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_give_it_a_try">Give it a try!</h2>
-                  <div class="sectionbody">
-                  <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=12322333">Release notes</a> &#93;
-                  &#91; <a href="https://sourceforge.net/projects/jboss/files/Weld/3.0.0.Alpha1">Distribution</a> &#93;
-                  &#91; <a href="http://sourceforge.net/projects/jboss/files/Weld/3.0.0.Alpha1/wildfly-9.0.0.Alpha1-weld-3.0.0.Alpha1-patch.zip/download">Patch for WildFly 9</a> &#93;</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>
+              <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/20.html" class="page-link">20</a> <a href="/news/page/18.html" class="next-link">Next</a> </div>
               <hr>
               <div>
                 <a href="http://weld.cdi-spec.org/news.atom">
diff --git a/news/page/18.html b/news/page/18.html
index 1c941872..2b9a394c 100644
--- a/news/page/18.html
+++ b/news/page/18.html
@@ -141,6 +141,192 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2014/10/02/weld-300Alpha1/">Weld 3.0.0.Alpha1 released!</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2014-10-2
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Jozef Hartinger
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>Today we are releasing Weld 3.0.0.Alpha1. This release serves as an <strong>early proof of concept</strong> of some of the ideas that are being discussed by the CDI Expert Group for the upcoming
+                  <a href="http://cdi-spec.org/">CDI 2.0 specification</a>. Furthermore, this is a great opportunity for the community to test-drive some of the proposed improvements and <strong>provide us with feedback</strong>.
+                  Be warned though that this released does not come with any guarantee of stability and that binary and functional compatibility is likely to be broken in the following releases.</p>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_ordering_of_observer_methods">Ordering of observer methods</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>The first of the new features are ordered observer methods. This requirement came up a long ago and several approaches were proposed in the meantime, as documented by
+                  <a href="https://issues.jboss.org/browse/CDI-4">CDI-4</a>.The Alpha1 release employs the general-purpose <code>@Priority</code> annotation to determine the order in which observer methods are to be notified.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>There are many open questions about this feature. Here are some of the rules we set for the purpose of this experimental implementation. These are by no means set in stone but instead we encourage you
+                  to give us feedback on these:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Each observer method has a certain priority value. An observer method that does not define a priority explicitly is given the default priority which is 2500 (in the middle of the <code>Interceptor.Priority.APPLICATION</code> range)</p>
+                  </li>
+                  <li>
+                  <p>The priority of an observer method determines the order. An observer method with lower value is called before an observer method with higher value</p>
+                  </li>
+                  <li>
+                  <p>If multiple observer methods define the same priority value, the order is undefined</p>
+                  </li>
+                  <li>
+                  <p>Observer methods priorities should match <a href="https://javaee-spec.java.net/nonav/javadocs/javax/interceptor/Interceptor.Priority.html">existing priority range convention</a></p>
+                  </li>
+                  <li>
+                  <p>The ordering applies to both transactional and non-transactional observer methods</p>
+                  </li>
+                  <li>
+                  <p>The priority annotation is applied on the event parameter (not the observer method)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>Here’s an example:</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">public void sendWelcome(@Observes @Priority(APPLICATION + 800) @Registered User user) {&#x000A;        // ...&#x000A;    }</code></pre>
+                  </div>
+                  </div>
+                  <div class="paragraph">
+                  <p>Note that <code>javax.annotation.Priority</code> can currently only be applied to types. Therefore, we temporarily created a substitute called <strong><code>org.jboss.weld.experimental.Priority</code></strong> which is identical
+                  to the original except that it can also be applied on parameters (of observer methods). The plan is to propagate this change back to <code>javax.annotation.Priority</code>. In the meantime, Weld’s twin
+                  gets the job done.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>In addition to the <code>@Priority</code> annotation, the SPI was also enhanced to expose the priority of an observer method. We are not touching <code>javax.enterprise</code> interfaces just yet. Instead,
+                  the <code>org.jboss.weld.experimental</code> package contains proposals for how the new SPI should look like. As the package name suggests, this SPI is good for a test-drive but do not expect it to be stable.
+                  To use the experimental SPIs, you&#8217;ll need to add a dependency on <a href="http://search.maven.org/#artifactdetails%7Corg.jboss.weld%7Cweld-api%7C3.0.Alpha1%7Cjar">weld-api</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Here’s an example of reading the observer method priority using the SPI in an Extension. <code>ExperimentalProcessObserverMethod</code> and <code>ExperimentalObserverMethod</code> interfaces come from the
+                  <code>org.jboss.weld.experimental package</code>.</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">public class SimpleExtension implements Extension {&#x000A;    &#x000A;        void observe(@Observes ExperimentalProcessObserverMethod&lt;User, ?&gt; event) {&#x000A;            ExperimentalObserverMethod&lt;User&gt; observerMethod = event.getObserverMethod();&#x000A;            this.priority = observerMethod.getPriority();&#x000A;        }&#x000A;    }</code></pre>
+                  </div>
+                  </div>
+                  <div class="paragraph">
+                  <p>Use the <a href="https://issues.jboss.org/browse/CDI-4">corresponding CDI ticket</a> for any feedback on these features.</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_vetoing_and_modifying_observer_methods">Vetoing and modifying observer methods</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>We’ll stay with observer methods for a few more paragraphs. A <a href="https://issues.jboss.org/browse/CDI-458">request</a> was raised in the CDI issue tracker for making it possible to disable an
+                  observer method using the <code>ProcessObserverMethod</code> SPI.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>This Alpha1 release introduces the <code>veto()</code> methods (aligned with <code>ProcessAnnotatedType.veto()</code>) for this:</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">void disableDebuggingObservers(@Observes ExperimentalProcessObserverMethod&lt;?, Debug&gt; event) {&#x000A;        if (projectStage != ProjectStage.Development) {&#x000A;            event.veto();&#x000A;        }&#x000A;    }</code></pre>
+                  </div>
+                  </div>
+                  <div class="paragraph">
+                  <p>In addition, the observer method metadata may be altered by an extension. This is done similarly to how <code>InjectionTarget</code>, <code>InjectionPoint</code> or <code>BeanAttribute</code> metadata are modified which
+                  is most often by wrapping the original object (decorator design pattern). Any piece of metadata (including aforementioned priority) can be altered. For example, the transaction phase:</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">void alterObserver(@Observes ExperimentalProcessObserverMethod&lt;User, ?&gt; event) {&#x000A;        event.setObserverMethod(new ForwardingExperimentalObserverMethod&lt;User&gt;(event.getObserverMethod()) {&#x000A;            @Override&#x000A;            public TransactionPhase getTransactionPhase() {&#x000A;                return TransactionPhase.AFTER_SUCCESS;&#x000A;            }&#x000A;        });&#x000A;    }</code></pre>
+                  </div>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_repeatable_qualifiers_and_interceptor_bindings">Repeatable qualifiers and interceptor bindings</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>This release serves as a proof of concept for supporting repeating qualifiers and interceptor bindings. You can now fully utilize Java 8 features and use multiple qualifiers or interceptor bindings
+                  of the same type in the same location, for example:</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">public class School {&#x000A;    &#x000A;        @Produces&#x000A;        @Speaks("English")&#x000A;        @Speaks("French")&#x000A;        public Student graduate() {&#x000A;            // ...&#x000A;        }&#x000A;    }</code></pre>
+                  </div>
+                  </div>
+                  <div class="paragraph">
+                  <p>Repeating qualifiers can be used for both bean and event resolution. See the <a href="http://docs.oracle.com/javase/tutorial/java/annotations/repeating.html">Java documentation</a> for how to define
+                  a repeating annotation.</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_interceptor_bindings_in_invocation_context">Interceptor bindings in invocation context</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>This is an often recurring scenario. An interceptor binding defines several <code>@NonBinding</code> members which serve as configuration for the interceptor. How does an interceptor get hold of these values?
+                  This is not easy as the interceptor binding may often appear on the intercepted method, the class that defined it or may be inherited from another interceptor binding or stereotype (even transitively!).
+                  This problem gave birth to utilities such as
+                  <a href="https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;a=blob;f=deltaspike/core/api/src/main/java/org/apache/deltaspike/core/util/AnnotationUtils.java;h=9d4c8e2f72936facf1ef0d8d9655c4186965afde;hb=HEAD">this one</a>.
+                  Still, even after all this effort the result is not entirely correct as it was obtained using Java reflection ignoring the fact that the interceptor binding may have been modified
+                  (e.g. using <code>ProcessAnnotatedType</code>).</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>This problem is being addressed as <a href="https://issues.jboss.org/browse/CDI-468">CDI-468</a>. The Alpha1 release of Weld implements this feature and exposes new methods for obtaining interceptor bindings
+                  that are in effect for the interception. This is done using <code>ExperimentalInvocationContext.getInterceptorBindings()</code> or <code>ExperimentalInvocationContext.getInterceptorBindingsByType()</code>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Again, <code>ExperimentalInvocationContext</code> can be found in the <code>org.jboss.weld.experimental</code> package and depicts how the future version of <code>javax.interceptor.InvocationContext</code> could look like.</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@Interceptor&#x000A;    @Secure&#x000A;    public class SecurityInterceptor {&#x000A;    &#x000A;        @Inject&#x000A;        private User user;&#x000A;    &#x000A;        @AroundInvoke&#x000A;        public Object intercept(ExperimentalInvocationContext ctx) throws Exception {&#x000A;            Secure binding = ctx.getInterceptorBindingsByType(Secure.class).iterator().next();&#x000A;            if (!user.getRoles().contains(binding.requireRole())) {&#x000A;                throw new SecurityException();&#x000A;            }&#x000A;            return ctx.proceed();&#x000A;        }&#x000A;    }</code></pre>
+                  </div>
+                  </div>
+                  <div class="paragraph">
+                  <p>Again, your feedback is welcome at <a href="https://issues.jboss.org/browse/CDI-468">CDI-468</a>.</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_changes_in_the_annotated_layer">Changes in the Annotated layer</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>CDI provides an abstraction over the Reflection API - <a href="http://docs.jboss.org/cdi/api/1.2/javax/enterprise/inject/spi/Annotated.html">AnnotatedType and friends</a> - which mostly allows extensions
+                  to alter the set of annotations present on a type, field, method, etc.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>The Alpha1 release contains two minor additions to this API. Firstly, the API now supports Java 8 repeating annotations with a new method <code>ExperimentalAnnotated.getAnnotationsByType(Class&lt;T&gt; annotationClass)</code></p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Secondly, it is now possible to access the <code>java.lang.reflect.Parameter</code> instance that is wrapped by <code>AnnotatedParameter</code> using <code>ExperimentalAnnotatedParameter.getJavaParameter();</code></p>
+                  </div>
+                  <div class="paragraph">
+                  <p>See <a href="https://issues.jboss.org/browse/CDI-471">CDI-471</a> and <a href="https://issues.jboss.org/browse/CDI-481">CDI-481</a> for details.</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_give_it_a_try">Give it a try!</h2>
+                  <div class="sectionbody">
+                  <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=12322333">Release notes</a> &#93;
+                  &#91; <a href="https://sourceforge.net/projects/jboss/files/Weld/3.0.0.Alpha1">Distribution</a> &#93;
+                  &#91; <a href="http://sourceforge.net/projects/jboss/files/Weld/3.0.0.Alpha1/wildfly-9.0.0.Alpha1-weld-3.0.0.Alpha1-patch.zip/download">Patch for WildFly 9</a> &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2014/09/18/weld-next/">Weld.Next</a>
@@ -476,31 +662,7 @@ <h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2013/12/11/weld-211-final/">Weld 2.1.1.Final</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2013-12-11
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Jozef Hartinger
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>Weld 2.1.1.Final was released. More than 20 issues were addressed in this release. See the <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12322670">release notes</a> for details. Thanks to everyone involved in this release!</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>&#91; <a href="https://sourceforge.net/projects/jboss/files/Weld/2.1.1.Final">Distribution</a> &#93;
-                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12322670">Release notes</a> &#93;
-                  &#91; <a href="http://docs.jboss.org/weld/reference/2.1.1.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>
-                <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>
+              <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/20.html" class="page-link">20</a> <a href="/news/page/19.html" class="next-link">Next</a> </div>
               <hr>
               <div>
                 <a href="http://weld.cdi-spec.org/news.atom">
diff --git a/news/page/19.html b/news/page/19.html
index 895ee141..c990ecbb 100644
--- a/news/page/19.html
+++ b/news/page/19.html
@@ -141,6 +141,30 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2013/12/11/weld-211-final/">Weld 2.1.1.Final</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2013-12-11
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Jozef Hartinger
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>Weld 2.1.1.Final was released. More than 20 issues were addressed in this release. See the <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12322670">release notes</a> for details. Thanks to everyone involved in this release!</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="https://sourceforge.net/projects/jboss/files/Weld/2.1.1.Final">Distribution</a> &#93;
+                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12322670">Release notes</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/2.1.1.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>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2013/10/22/weld-210-final/">Weld 2.1.0.Final</a>
@@ -316,43 +340,7 @@ <h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2013/04/25/weld-200-final/">Weld 2.0.0.Final released</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2013-4-25
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Jozef Hartinger
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>I am pleased to announce the release of Weld 2.0.0.Final, the reference implementation of Contexts and Dependency Injection for Java EE 1.1 (<a href="http://www.jcp.org/en/jsr/detail?id=346">JSR 346</a>). For a list of major changes in CDI 1.1 see the <a href="http://docs.jboss.org/cdi/spec/1.1/cdi-spec.html#_major_changes">specification</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>The reference implementation will soon be available in <a href="https://glassfish.java.net/">GlassFish 4</a> and <a href="http://wildfly.org/">WildFly</a> (formerly JBoss Application Server). In the meantime you can check snapshots of the application servers.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>As always, Weld artifacts can be obtained from maven or you can use a distribution bundle.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Along with the Weld release comes the final release of the Technology Compatibility Kit (TCK) for CDI 1.1. Martin Kouba did an excellent job writing new tests and keeping the TCK in sync with the almost never-ending stream of specification changes. The TCK splits the specification into 1550 testable assertions out of which 96.71% is covered by TCK tests.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>I would like to thank to everyone who lent a hand and helped delivering these releases, especially: Martin Kouba, Pete Muir, Marko Lukša, Stuart Douglas, Marek Schmidt, Ron Šmeral, Tomáš Remeš, JJ Snyder, Phil Zampino, Tomaž Cerar, Hardy Ferentschik, Lincoln Baxter III, Matúš Abaffy and others.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>&#91; Distribution (<a href="http://sourceforge.net/projects/jboss/files/Weld/2.0.0.Final/">Weld</a>, <a href="https://sourceforge.net/projects/jboss/files/CDI-TCK/1.1.0.Final/">CDITCK</a>) &#93;
-                  &#91; Documentation (<a href="http://docs.jboss.org/weld/reference/2.0.0.Final/en-US/">Weld</a>, <a href="http://docs.jboss.org/cdi/tck/reference/1.1.0.Final/doc/">CDITCK</a>) &#93;
-                  &#91; Javadoc (<a href="http://docs.jboss.org/cdi/api/1.1/">CDI 1.1</a>, <a href="http://docs.jboss.org/weld/javadoc/2.0/">Weld SPI</a>) &#93;
-                  &#91; <a href="https://issues.jboss.org/browse/WELD">Issue tracker</a> &#93;</p>
-                  </div>
-                </div>
-                <hr>
-              </div>
-              <div class="pagination-links"><a href="/news/page/18.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/18.html" class="page-link">18</a> <span class="current-page">19</span> </div>
+              <div class="pagination-links"><a href="/news/page/18.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/18.html" class="page-link">18</a> <span class="current-page">19</span> <a href="/news/page/20.html" class="page-link">20</a> <a href="/news/page/20.html" class="next-link">Next</a> </div>
               <hr>
               <div>
                 <a href="http://weld.cdi-spec.org/news.atom">
diff --git a/news/page/2.html b/news/page/2.html
index f8a80e50..bc7536a5 100644
--- a/news/page/2.html
+++ b/news/page/2.html
@@ -141,6 +141,115 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2024/07/03/weld-600Beta4/">Weld 6.0.0.Beta4</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2024-7-3
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/release">release</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Matej Novotny
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>New versions of Weld artifacts are now available in Central - Weld Core <code>6.0.0.Beta4</code> accompanied by Weld API <code>6.0.Beta5</code>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Where applicable, <code>6.0.0.Beta4</code> bumps up Jakarta dependencies to their <code>Final</code> variants as well as implements remaining features from CDI spec, adds new Weld-specific API and addresses multiple backlog issues that were scheduled for this major release.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>You might be wondering where did Betas 2 and 3 go. While you can find their artifacts in Central, they bear no difference from <code>Beta4</code> apart from not having separate distributable ZIP and docs.
+                  With that in mind, below is the list of changes since Weld 6.0.0.Beta1:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Added the ability to register Build Compatible Extension in Weld SE without discovery (<a href="https://issues.redhat.com/browse/WELD-2772">WELD-2772</a>)</p>
+                  </li>
+                  <li>
+                  <p>Use <code>Lock</code> instead of <code>synchronized</code> within <code>ContextualInstanceStrategy</code> to be more virtual thread-friendly (<a href="https://issues.redhat.com/browse/WELD-2788">WELD-2788</a>)</p>
+                  </li>
+                  <li>
+                  <p>Skip superclass declarations of final methods when creating proxies (<a href="https://issues.redhat.com/browse/WELD-2785">WELD-2785</a>)</p>
+                  </li>
+                  <li>
+                  <p>Observer method confiurator now correctly allow to override <code>Reception</code> settings without changing its <code>notify()</code> method (<a href="https://issues.redhat.com/browse/WELD-2786">WELD-2786</a>)</p>
+                  </li>
+                  <li>
+                  <p>Correct <code>CommonLogger</code> to mention correct GAV for Jandex (<a href="https://issues.redhat.com/browse/WELD-2770">WELD-2770</a>)</p>
+                  </li>
+                  <li>
+                  <p>Invoker API enhancements (<a href="https://issues.redhat.com/browse/WELD-2780">WELD-2780</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Proper exception handling</p>
+                  </li>
+                  <li>
+                  <p>Document API Weld offer above what CDI specification has; Weld retains all parts of the initial design CDI had</p>
+                  </li>
+                  <li>
+                  <p>Added benchmarks to have a measure of our implementation versus direct invocation</p>
+                  </li>
+                  <li>
+                  <p>Code cleanup and other minor tweaks</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Remove <code>SecurityManager</code> related code from Weld (<a href="https://issues.redhat.com/browse/WELD-2789">WELD-2789</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p><code>SecurityManager</code> has been deprecated for quite a upcoming JDK versions plan to remove it completely so we remove it as part of the major release version</p>
+                  </li>
+                  <li>
+                  <p>This means Weld 6 no longer uses priviledged actions to perform various tasks, such as constructor invocations, reflection on classes etc.</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Remove <code>WARN</code> logging when an interceptor binding target of lifecycle interceptors targets anything other than <code>TYPE</code> (<a href="https://issues.redhat.com/browse/WELD-2790">WELD-2790</a>)</p>
+                  </li>
+                  <li>
+                  <p>Revise Weld 6 examples; only keep essentials (<a href="https://issues.redhat.com/browse/WELD-2771">WELD-2771</a>)</p>
+                  </li>
+                  <li>
+                  <p>Address Weld API javadoc warning (<a href="https://issues.redhat.com/browse/WELD-2779">WELD-2779</a>)</p>
+                  </li>
+                  <li>
+                  <p>Revisit servlet setup and testing (<a href="https://issues.redhat.com/browse/WELD-2784">WELD-2784</a>)</p>
+                  </li>
+                  <li>
+                  <p>Clean up legacy Jetty integration parts (<a href="https://issues.redhat.com/browse/WELD-2787">WELD-2787</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>Note that the latest <a href="http://docs.jboss.org/weld/reference/6.0.0.Beta4/en-US/html_single/" target="_blank" rel="noopener">documentation</a> incorrectly states that it is for <code>SNAPSHOT</code> which isn&#8217;t the case.
+                  It is built for Beta4 but due to incorrect script setup the version number wasn&#8217;t picked up properly.
+                  This will be corrected for the next release.</p>
+                  </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.Beta4/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=12423381" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2024/02/26/weld-600Beta1/">Weld 6.0.0.Beta1</a>
@@ -450,59 +559,7 @@ <h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2023/07/11/weld-511SP1/">Weld 5.1.1.SP1</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2023-7-11
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/release">release</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Matej Novotny
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>A new SP release of Weld 5 is now avaiable.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Latest release, Weld 5.1.1.Final, has shown that one of the changes (<a href="https://issues.redhat.com/browse/WELD-2743">WELD-2743</a>) had unforseen and, sadly, untested consequences.
-                  Some of the integrators and some of community were using <code>BeanManager#getReference</code> in scenarios which were broken by this change.
-                  While the use cases aren&#8217;t explicitly backed by the specification or its TCKs, we decided we don&#8217;t want to break them, especially not in a micro release.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>This SP release therefore aims to correct the above and only adds one other tiny change:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Revert the change of <code>BeanManager#getReference</code> and solve this issue differently (<a href="https://issues.redhat.com/browse/WELD-2745">WELD-2745</a>)</p>
-                  </li>
-                  <li>
-                  <p>Modify how <code>toString()</code> is invoked on proxies of removed EJB beans (<a href="https://issues.redhat.com/browse/WELD-2747">WELD-2747	</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>Big thanks for (<a href="https://github.com/ljnelson">Laird Nelson</a>) and (<a href="https://github.com/arjantijms">Arjan Tijms</a>) for bringing these cases to my attention as well as helping to understand and resolve them!</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>As always, if you find further issues with Weld 5, do let us know.</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.SP1/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=12410330" 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>
+              <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/19.html" class="page-link">19</a> <a href="/news/page/20.html" class="page-link">20</a> <a href="/news/page/3.html" class="next-link">Next</a> </div>
               <hr>
               <div>
                 <a href="http://weld.cdi-spec.org/news.atom">
diff --git a/news/page/20.html b/news/page/20.html
new file mode 100644
index 00000000..6b45a10f
--- /dev/null
+++ b/news/page/20.html
@@ -0,0 +1,224 @@
+<!DOCTYPE html>
+<html>
+  <head>
+    <meta charset="utf-8">
+    <title>
+      Weld: News
+    </title>
+    <meta content="width=device-width, initial-scale=1.0" name="viewport">
+    <meta content="Latest news about Weld." 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">
+              <h1>
+                News
+                <a href="http://weld.cdi-spec.org/news.atom">
+                  <i class="fa fa-rss"></i>
+                </a>
+              </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2013/04/25/weld-200-final/">Weld 2.0.0.Final released</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2013-4-25
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Jozef Hartinger
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>I am pleased to announce the release of Weld 2.0.0.Final, the reference implementation of Contexts and Dependency Injection for Java EE 1.1 (<a href="http://www.jcp.org/en/jsr/detail?id=346">JSR 346</a>). For a list of major changes in CDI 1.1 see the <a href="http://docs.jboss.org/cdi/spec/1.1/cdi-spec.html#_major_changes">specification</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>The reference implementation will soon be available in <a href="https://glassfish.java.net/">GlassFish 4</a> and <a href="http://wildfly.org/">WildFly</a> (formerly JBoss Application Server). In the meantime you can check snapshots of the application servers.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>As always, Weld artifacts can be obtained from maven or you can use a distribution bundle.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Along with the Weld release comes the final release of the Technology Compatibility Kit (TCK) for CDI 1.1. Martin Kouba did an excellent job writing new tests and keeping the TCK in sync with the almost never-ending stream of specification changes. The TCK splits the specification into 1550 testable assertions out of which 96.71% is covered by TCK tests.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>I would like to thank to everyone who lent a hand and helped delivering these releases, especially: Martin Kouba, Pete Muir, Marko Lukša, Stuart Douglas, Marek Schmidt, Ron Šmeral, Tomáš Remeš, JJ Snyder, Phil Zampino, Tomaž Cerar, Hardy Ferentschik, Lincoln Baxter III, Matúš Abaffy and others.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; Distribution (<a href="http://sourceforge.net/projects/jboss/files/Weld/2.0.0.Final/">Weld</a>, <a href="https://sourceforge.net/projects/jboss/files/CDI-TCK/1.1.0.Final/">CDITCK</a>) &#93;
+                  &#91; Documentation (<a href="http://docs.jboss.org/weld/reference/2.0.0.Final/en-US/">Weld</a>, <a href="http://docs.jboss.org/cdi/tck/reference/1.1.0.Final/doc/">CDITCK</a>) &#93;
+                  &#91; Javadoc (<a href="http://docs.jboss.org/cdi/api/1.1/">CDI 1.1</a>, <a href="http://docs.jboss.org/weld/javadoc/2.0/">Weld SPI</a>) &#93;
+                  &#91; <a href="https://issues.jboss.org/browse/WELD">Issue tracker</a> &#93;</p>
+                  </div>
+                </div>
+                <hr>
+              </div>
+              <div class="pagination-links"><a href="/news/page/19.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/19.html" class="page-link">19</a> <span class="current-page">20</span> </div>
+              <hr>
+              <div>
+                <a href="http://weld.cdi-spec.org/news.atom">
+                  <i class="fa fa-rss"></i>
+                  Subscribe to Weld news
+                </a>
+              </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/page/3.html b/news/page/3.html
index 23dca555..d260f972 100644
--- a/news/page/3.html
+++ b/news/page/3.html
@@ -141,6 +141,58 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2023/07/11/weld-511SP1/">Weld 5.1.1.SP1</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2023-7-11
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/release">release</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Matej Novotny
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>A new SP release of Weld 5 is now avaiable.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Latest release, Weld 5.1.1.Final, has shown that one of the changes (<a href="https://issues.redhat.com/browse/WELD-2743">WELD-2743</a>) had unforseen and, sadly, untested consequences.
+                  Some of the integrators and some of community were using <code>BeanManager#getReference</code> in scenarios which were broken by this change.
+                  While the use cases aren&#8217;t explicitly backed by the specification or its TCKs, we decided we don&#8217;t want to break them, especially not in a micro release.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>This SP release therefore aims to correct the above and only adds one other tiny change:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Revert the change of <code>BeanManager#getReference</code> and solve this issue differently (<a href="https://issues.redhat.com/browse/WELD-2745">WELD-2745</a>)</p>
+                  </li>
+                  <li>
+                  <p>Modify how <code>toString()</code> is invoked on proxies of removed EJB beans (<a href="https://issues.redhat.com/browse/WELD-2747">WELD-2747	</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>Big thanks for (<a href="https://github.com/ljnelson">Laird Nelson</a>) and (<a href="https://github.com/arjantijms">Arjan Tijms</a>) for bringing these cases to my attention as well as helping to understand and resolve them!</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>As always, if you find further issues with Weld 5, do let us know.</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.SP1/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=12410330" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2023/06/12/weld-511Final/">Weld 5.1.1.Final</a>
@@ -387,43 +439,7 @@ <h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2022/05/04/weld-500SP1/">Weld 5.0.0.SP1</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2022-5-4
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/release">release</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Matej Novotny
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>A new version of Weld core is now in Maven Central - 5.0.0.SP1.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>There have been reports of a bytecode verification error in certain scenarios reported by <a href="https://www.eclipse.org/lists/cdi-dev/msg00586.html">GlassFish</a> and <a href="https://github.com/wildfly/wildfly/pull/15474#issuecomment-1113505376">WildFly</a> trying to integrate Weld 5.0.0.Final.
-                  We have investigated the cause and identified the problematic change, you can read more about it in <a href="https://issues.redhat.com/browse/WELD-2719">WELD-2719</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Weld 5.0.0.SP1 release reverts the offending change (<a href="https://issues.redhat.com/browse/WELD-2712">WELD-2712</a>) and otherwise keeps Weld intant in terms of changes.
-                  In case you identify any further issues, don&#8217;t hesitate to reach out.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>&#91; <a href="/download/">Download</a> &#93;
-                  &#91; <a href="http://docs.jboss.org/weld/reference/5.0.0.SP1/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=12385753" 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>
+              <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/19.html" class="page-link">19</a> <a href="/news/page/20.html" class="page-link">20</a> <a href="/news/page/4.html" class="next-link">Next</a> </div>
               <hr>
               <div>
                 <a href="http://weld.cdi-spec.org/news.atom">
diff --git a/news/page/4.html b/news/page/4.html
index ce93e699..09f20bb1 100644
--- a/news/page/4.html
+++ b/news/page/4.html
@@ -141,6 +141,42 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2022/05/04/weld-500SP1/">Weld 5.0.0.SP1</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2022-5-4
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/release">release</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Matej Novotny
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>A new version of Weld core is now in Maven Central - 5.0.0.SP1.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>There have been reports of a bytecode verification error in certain scenarios reported by <a href="https://www.eclipse.org/lists/cdi-dev/msg00586.html">GlassFish</a> and <a href="https://github.com/wildfly/wildfly/pull/15474#issuecomment-1113505376">WildFly</a> trying to integrate Weld 5.0.0.Final.
+                  We have investigated the cause and identified the problematic change, you can read more about it in <a href="https://issues.redhat.com/browse/WELD-2719">WELD-2719</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Weld 5.0.0.SP1 release reverts the offending change (<a href="https://issues.redhat.com/browse/WELD-2712">WELD-2712</a>) and otherwise keeps Weld intant in terms of changes.
+                  In case you identify any further issues, don&#8217;t hesitate to reach out.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="/download/">Download</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/5.0.0.SP1/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=12385753" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2022/04/29/weld-500Final/">Weld 5.0.0.Final</a>
@@ -374,316 +410,7 @@ <h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2022/01/24/weld-500Beta1/">Weld 5.0.0.Beta1</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2022-1-24
-                  &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>Some of you might have noticed that Weld already had some version 5 releases, namely two Alphas.
-                  Those were a work-in-progress implementations so I didn&#8217;t post any actual release notes as the specification was still undergoing changes.
-                  CDI 4 is now in very much ready-to-fly state as its first CR release has recently landed in Maven Central.
-                  Therefore, here we are with a proper release of Weld API <code>5.0.Beta5</code> and Weld Core <code>5.0.0.Beta1</code> which implements all the bits and pieces of CDI 4.0 plus brings a few more changes and deprecation removals.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>This post will try to cover Weld-side of things meaning anything that changed and is Weld specific or influences integrators in any way.
-                  If you want to learn what&#8217;s new in CDI 4.0, I suggest taking a look at <a href="https://eclipse-ee4j.github.io/cdi/2021/10/25/way-to-cdi4.html">this detailed article</a> I wrote some time ago.
-                  It provides a good overview of all major changes, all of which are implemented in this Weld release.
-                  In case you want to check out the list of JIRA issues for Weld releases, the last chapter will provide links for both Alpha releases as well as this Beta release.
-                  Last but not least, you can also reach out to us via <a href="https://gitter.im/weld/user">Gitter channel</a> or <a href="https://lists.jboss.org/admin/lists/weld-dev.lists.jboss.org/"><code>weld-dev@lists.jboss.org</code> mailing list</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Without further ado, let&#8217;s dive into it!</p>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_target_jdk_version_for_weld_5_and_for_cdi_4_is_now_11">Target JDK version for Weld 5 (and for CDI 4) is now 11</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>Therefore, JDK 11 is now the minimal version required to run Weld.
-                  This is basically a requirement for all Jakarta EE 10 specifications.
-                  On the other hand, Weld 5 is also tested against and supports JDK 17 as well.</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_weld_5_is_no_longer_a_multi_release_mr_jars">Weld 5 is no longer a multi-release (MR) JARs</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>As you might know, Weld 3 and 4 are running some different class defining strategies for JDK 8 or 11+ resulting in an MR JAR solution.
-                  Since JDK 11 is the basis, this is no longer needed and similar workarounds were removed from code.</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_deprecations_and_removals">Deprecations and removals</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>Here is a list of all changes of this nature within Weld APIs:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Multiple methods from <code>org.jboss.weld.serialization.spi.ProxyServices</code> were removed.</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>If you are an integrator, you probably implemented this interface at some point in time; these methods weren&#8217;t used by Weld anyway, so they are now gone for good.</p>
-                  </li>
-                  <li>
-                  <p>Here is a <a href="https://issues.redhat.com/browse/WELD-2702">link to the issue removing it</a>.</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Any integrators basing their implementations of Jandex likely implemented <code>ClassFileInfo</code>; its <code>isTopLevelClass()</code> has been removed.</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Note that this method was redundant and can be replaced by <code>getClassNestingType()</code>.</p>
-                  </li>
-                  <li>
-                  <p>This was removed as part of the above mentioned issue.</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p><code>WeldInstance.Handler</code> class is now deprecated and so are multiple methods returning this type from <code>WeldInstance</code></p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>The reasons for this removal is that the very same feature was accepted into CDI specification so you can now use CDI API interfaces to achieve the same.</p>
-                  </li>
-                  <li>
-                  <p>For more information, take a look at <a href="https://github.com/eclipse-ee4j/cdi/blob/master/api/src/main/java/jakarta/enterprise/inject/Instance.java#L266-L315"><code>Instance.Handle</code> class from CDI API</a>.</p>
-                  </li>
-                  <li>
-                  <p>And again, a <a href="https://issues.redhat.com/browse/WELD-2685">link to the relevant issue</a>.</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>CDI has had a similar cleanup and some long deprecated API methods were removed; glance at <a href="https://github.com/eclipse-ee4j/cdi/issues/472">this GitHub issue</a> if you want to learn more about that.</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_empty_beans_xml_interpretation">Empty `beans.xml interpretation</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>There is one breaking change in CDI 4.0 that should be mentioned here - change of default interpretation of empty <code>beans.xml</code> descriptor.
-                  Up until CDI 3.0, leaving this file empty meant discovery mode <code>all</code> whereas starting with CDI 4 it now defaults to <code>annotated</code> discovery mode.
-                  As per specification, in <code>all</code> discovery mode, all classes in bean archive are scanned and if fitting, turned into beans.
-                  However, <code>annotated</code> discovery mode only scans classes with <em>bean defining annotations</em>.
-                  Therefore, this change can be breaking for lots of applications using empty <code>beans.xml</code> and relying on CDI to discover classes without annotations.
-                  In order to ease the transition to this new default, CDI 4 specification says the following:</p>
-                  </div>
-                  <div class="quoteblock">
-                  <blockquote>
-                  <div class="paragraph">
-                  <p>For compatibility with CDI versions prior to 4.0, CDI Full products must contain an option that causes an archive with empty beans.xml to be considered an explicit bean archive.</p>
-                  </div>
-                  </blockquote>
-                  </div>
-                  <div class="paragraph">
-                  <p>This option is vendor-dependent and integrators needs to define how to achieve it in their frameworks/platforms.
-                  That being said, Weld has been updated to allow for this.
-                  If you are using Weld tooling to parse <code>beans.xml</code>, chances are, you&#8217;re doing one of these:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Directly invoking parser via <a href="https://github.com/weld/core/blob/5.0.0.Beta1/impl/src/main/java/org/jboss/weld/xml/BeansXmlStreamParser.java"><code>org.jboss.weld.xml.BeansXmlStreamParser</code></a>.</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p><code>BeansXmlStreamParser</code> now has new constructor methods which allow passing <code>BeanDiscoveryMode</code> parameter telling Weld how to interpret empty <code>beans.xml</code>.</p>
-                  </li>
-                  <li>
-                  <p>All former constructors were retained and default to <code>BeanDiscoveryMode.ANNOTATED</code>.</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Indirectly invoking it via an implementation of <code>org.jboss.weld.bootstrap.api.Bootstrap</code> and its <code>parse</code> methods.</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>New variantions of the <code>parse</code> methods were added and accept <code>BeanDiscoveryMode</code> parameter telling Weld how to interpret empty <code>beans.xml</code>.</p>
-                  </li>
-                  <li>
-                  <p>All former variantion of <code>parse</code> methods were retained and default to <code>BeanDiscoveryMode.ANNOTATED</code>.</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>This should give integrators enough leeway to implement the backward compatibility switch.</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_weld_versus_cdi_lite_versus_cdi_full">Weld versus CDI Lite versus CDI Full</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>By far the biggest change in CDI 4.0 is the introduction of CDI Lite.
-                  At this point I should reiterate that I highly recommend looking <a href="https://eclipse-ee4j.github.io/cdi/2021/10/25/way-to-cdi4.html">this article</a> if you don&#8217;t know what CDI Lite is.
-                  In short, CDI Lite is a feature subset of CDI Full that broadens the amount of environments in which CDI can execute; more presicely, it enables CDI in build time oriented frameworks such as Micronaut or Quarkus.
-                  What does that means for Weld users? Nothing much, Weld is and will be a runtime oriented implementation and you can keep using CDI as you did up until now.
-                  More precisely, Weld is so called CDI Full implementation meaning it provides each and every CDI feature and while there were some deprecations and removals, the rest stays the same.</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_build_compatible_extensions">Build Compatible Extensions</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>One of the notable additions to CDI Lite  (and therefore into CDI Full as well) were Build Compatible Extensions (BCE).
-                  These are akin to Portable Extensions but tuned in a way so that they can be used in build time oriented environments as well.
-                  Along with it comes a different language model because <code>AnnotatedType</code> and friends are reflection-heavy and not a good fit for that API.
-                  If you want to learns more, <a href="https://eclipse-ee4j.github.io/cdi/2021/12/03/you-know-build-compatible-extensions.html">here is an excellent article</a> by Ladislav Thon that covers how they work.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>From Weld perspective, you can use BCE as much as you like although they are also executed at runtime, just as Portable Extensions are.
-                  It is still recommended to use Portable Extensions if possible because BCE are (in Weld) implemented via Portable Extensions.
-                  That being said, if you have some portability demands between Lite and Full, you should be able to use BCE as much as you like.</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_integrators_how_to_make_weld_understand_build_compatible_extensions">Integrators - how to make Weld understand Build Compatible Extensions?</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>This part focuses mainly on integrators and describes how Weld implements Build Compatible Extensions and what needs to be done by integrators in order to fully support CDI Lite.</p>
-                  </div>
-                  <div class="sect2">
-                  <h3 id="_weld_lite_extension_translator_module"><code>weld-lite-extension-translator</code> module</h3>
-                  <div class="paragraph">
-                  <p>Weld 5 has a new module that enables Build Compatible Extensions (BCE) and the new language model that goes along with it - <a href="https://github.com/weld/core/tree/5.0.0.Beta1/weld-lite-extension-translator"><code>weld-lite-extension-translator</code></a>.
-                  GAV of this new artifact is <code>org.jboss.weld:weld-lite-extension-translator:5.0.0.Beta1</code>.
-                  As I mentioned in previous point, BCE are executed via a Portable extension.
-                  More precisely, the key class is <a href="https://github.com/weld/core/blob/5.0.0.Beta1/weld-lite-extension-translator/src/main/java/org/jboss/weld/lite/extension/translator/LiteExtensionTranslator.java"><code>WeldLiteExtensionTranslator</code></a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Just like any Portable extension, it needs an entry in <code>META-INF</code> or an instance of this extensions has to be added programmaticaly during Weld bootstrap.
-                  This is where it gets tricky; <strong>it doesn&#8217;t work out of the box in all environments</strong>!</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Weld SE - works out of the box, the extension is automagically added</p>
-                  </li>
-                  <li>
-                  <p>Weld Servlet - works out of the box, the extensions is automagically added</p>
-                  </li>
-                  <li>
-                  <p>EE - <strong>doesn&#8217;t work without integrator registering the extension</strong></p>
-                  </li>
-                  <li>
-                  <p>Any other custom integration - <strong>doesn&#8217;t work without integrator registering the extension</strong></p>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>There is of course a reason for it - complex structured deployments (such as EAR or WAR) and the fact that Weld alone cannot know the deployment well enough to make sure this extension wouldn&#8217;t be registered multiple times.
-                  On top of that, you might also want to avoid registering this extension if there are no BCE found inside the deployment which can also be dependent on how the given platform performs such discovery.
-                  Therefore, Weld leaves it up to the integrator (WildFly, GF, Liberty,&#8230;&#8203;) to identify where and when to register this extension for each deployment.</p>
-                  </div>
-                  </div>
-                  <div class="sect2">
-                  <h3 id="_registering_liteextensiontranslator">Registering <code>LiteExtensionTranslator</code></h3>
-                  <div class="paragraph">
-                  <p>Registering the <code>LiteExtensionTranslator</code> can be as easy as adding a <code>META-INF</code> entry with it into some archive in the deployment.
-                  An example of this would be <code>arquillian-container-weld</code>, a test container for Weld applications.
-                  As you can see from <a href="https://github.com/arquillian/arquillian-container-weld/pull/114/files">this pull request</a>, it basically adds a <code>META-INF</code> entry which is sufficient to support new extension model.
-                  Since it a test tool, the extension is always registered without any attempt to optimize it.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>The above solution is nice and clean, but won&#8217;t cut it for any EE integrators.
-                  Instead, you will want to register this extension very similarly to how you currently register <a href="https://github.com/weld/core/blob/5.0.0.Beta1/probe/core/src/main/java/org/jboss/weld/probe/ProbeExtension.java"><code>ProbeExtension</code></a> - add it programmatically as part of the CDI deployment.
-                  As mentioned above, this extension should to be registered at most once per deployment, so I&#8217;d recommend welding (pun intended) this directly into your <code>org.jboss.weld.bootstrap.spi.CDI11Deployment</code> implementation.
-                  Because WildFly does not yet have a public branch with this, I can at least point to how <a href="https://github.com/wildfly/wildfly/blob/main/weld/subsystem/src/main/java/org/jboss/as/weld/deployment/processors/DevelopmentModeProcessor.java#L138-L139">it registers <code>ProbeExtension</code></a>.
-                  With a little bit of digging, it boils down to <a href="https://github.com/wildfly/wildfly/blob/main/weld/subsystem/src/main/java/org/jboss/as/weld/deployment/WeldDeployment.java#L97">creating <code>CDI11Deployment</code> impl</a> with list of extensions already containing this one.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Which brings us to the second point - I&#8217;d recommend integrators to optimize this process and only register/include <code>LiteExtensionTranslator</code> when there is at least one BCE present in any given deployment.
-                  The reason being that this extension has to monitor a very wide range of events including <code>ProcessAnnotatedType&lt;?&gt;</code> for all types in order to properly implement BCE.
-                  Many integrators can perform BCE detection in their own ways (such as Jandex in WildFly) but for those that want a generic solution, take a look at <code>org.jboss.weld.lite.extension.translator.BuildCompatibleExtensionLoader</code> which is a utility class alowing to perform a standard service discovery process with given <code>ClassLoader</code> and returns the set of discovered BCE classes.
-                  You can then instantiate <code>LiteExtensionTranslator</code> via a constructor that takes this set as an input; or skip registering it if you haven&#8217;t found any BCE at all.</p>
-                  </div>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_tck_structural_changes_and_lang_model_tcks">TCK structural changes and lang model TCKs</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>Few paragraphs above I mentioned new language model used by Build Compatible Extensions.
-                  Obviously, this needed some testing and so CDI TCK has a separate module for it; see <a href="https://github.com/eclipse-ee4j/cdi-tck/tree/4.0.0-RC2/lang-model"><code>lang-model</code> module and its README</a>.
-                  Weld tests and passes these TCKs via <a href="https://github.com/weld/core/tree/5.0.0.Beta1/lang-model-tck"><code>lang-model-tck</code> module</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Next change was a separation of tests between pure CDI tests and tests requiring other Jakarta EE technologies such as JSF, EL and other.
-                  Many of these are candidates for move into their respective specifications but are for now still hosted in CDI TCK.
-                  All of these tests now reside under a <a href="https://github.com/eclipse-ee4j/cdi-tck/tree/4.0.0-RC2/web">separate module</a> with GAV <code>jakarta.enterprise:cdi-tck-web-impl</code>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Lastly, due to the split between CDI Lite and Full and the ability to have CDI implementations only for Lite, all TCKs had to be reviewed and a new test category was added - <a href="https://github.com/eclipse-ee4j/cdi-tck/blob/4.0.0-RC2/impl/src/main/java/org/jboss/cdi/tck/TestGroups.java#L37"><code>cdi-full</code></a>.
-                  It is easy to guess that this category was assigned to tests that are supposed to only execute in CDI Full implementations; i.e. tests containing features that aren&#8217;t present in CDI Lite.
-                  Weld, as noted before, is a CDI Full implementation and as such passes all TCKs.
-                  The current setup used for TCK execution can be read from <a href="https://github.com/weld/core/blob/5.0.0.Beta1/jboss-tck-runner/pom.xml">this POM file</a>.</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_more_in_depth_overview_of_resolved_issues_in_weld_5">More in-depth overview of resolved issues in Weld 5</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>Finally, for those who would like to inspect a more detailed list of changes, here are links to release notes of all version 5 releases up to and including Beta1:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p><a href="https://issues.redhat.com/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12358586">Weld 5.0.0.Alpha1 Release Notes</a></p>
-                  </li>
-                  <li>
-                  <p><a href="https://issues.redhat.com/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12378774">Weld 5.0.0.Alpha2 Release Notes</a></p>
-                  </li>
-                  <li>
-                  <p><a href="https://issues.redhat.com/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12378495">Weld 5.0.0.Beta1 Release Notes</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.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=12378495" target="_blank" rel="noopener">Release notes</a> &#93;</p>
-                  </div>
-                  </div>
-                  </div>
-                </div>
-                <hr>
-              </div>
-              <div class="pagination-links"><a href="/news/page/3.html" class="previous-link">Previous</a> <a href="/news/" class="page-link">1</a> <a href="/news/page/2.html" class="page-link">2</a> <a href="/news/page/3.html" class="page-link">3</a> <span class="current-page">4</span> <a href="/news/page/5.html" class="page-link">5</a> <span class="skip">...</span><a href="/news/page/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>
+              <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/19.html" class="page-link">19</a> <a href="/news/page/20.html" class="page-link">20</a> <a href="/news/page/5.html" class="next-link">Next</a> </div>
               <hr>
               <div>
                 <a href="http://weld.cdi-spec.org/news.atom">
diff --git a/news/page/5.html b/news/page/5.html
index 011fbfa3..966972d8 100644
--- a/news/page/5.html
+++ b/news/page/5.html
@@ -141,6 +141,315 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2022/01/24/weld-500Beta1/">Weld 5.0.0.Beta1</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2022-1-24
+                  &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>Some of you might have noticed that Weld already had some version 5 releases, namely two Alphas.
+                  Those were a work-in-progress implementations so I didn&#8217;t post any actual release notes as the specification was still undergoing changes.
+                  CDI 4 is now in very much ready-to-fly state as its first CR release has recently landed in Maven Central.
+                  Therefore, here we are with a proper release of Weld API <code>5.0.Beta5</code> and Weld Core <code>5.0.0.Beta1</code> which implements all the bits and pieces of CDI 4.0 plus brings a few more changes and deprecation removals.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>This post will try to cover Weld-side of things meaning anything that changed and is Weld specific or influences integrators in any way.
+                  If you want to learn what&#8217;s new in CDI 4.0, I suggest taking a look at <a href="https://eclipse-ee4j.github.io/cdi/2021/10/25/way-to-cdi4.html">this detailed article</a> I wrote some time ago.
+                  It provides a good overview of all major changes, all of which are implemented in this Weld release.
+                  In case you want to check out the list of JIRA issues for Weld releases, the last chapter will provide links for both Alpha releases as well as this Beta release.
+                  Last but not least, you can also reach out to us via <a href="https://gitter.im/weld/user">Gitter channel</a> or <a href="https://lists.jboss.org/admin/lists/weld-dev.lists.jboss.org/"><code>weld-dev@lists.jboss.org</code> mailing list</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Without further ado, let&#8217;s dive into it!</p>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_target_jdk_version_for_weld_5_and_for_cdi_4_is_now_11">Target JDK version for Weld 5 (and for CDI 4) is now 11</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>Therefore, JDK 11 is now the minimal version required to run Weld.
+                  This is basically a requirement for all Jakarta EE 10 specifications.
+                  On the other hand, Weld 5 is also tested against and supports JDK 17 as well.</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_weld_5_is_no_longer_a_multi_release_mr_jars">Weld 5 is no longer a multi-release (MR) JARs</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>As you might know, Weld 3 and 4 are running some different class defining strategies for JDK 8 or 11+ resulting in an MR JAR solution.
+                  Since JDK 11 is the basis, this is no longer needed and similar workarounds were removed from code.</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_deprecations_and_removals">Deprecations and removals</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>Here is a list of all changes of this nature within Weld APIs:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Multiple methods from <code>org.jboss.weld.serialization.spi.ProxyServices</code> were removed.</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>If you are an integrator, you probably implemented this interface at some point in time; these methods weren&#8217;t used by Weld anyway, so they are now gone for good.</p>
+                  </li>
+                  <li>
+                  <p>Here is a <a href="https://issues.redhat.com/browse/WELD-2702">link to the issue removing it</a>.</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Any integrators basing their implementations of Jandex likely implemented <code>ClassFileInfo</code>; its <code>isTopLevelClass()</code> has been removed.</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Note that this method was redundant and can be replaced by <code>getClassNestingType()</code>.</p>
+                  </li>
+                  <li>
+                  <p>This was removed as part of the above mentioned issue.</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p><code>WeldInstance.Handler</code> class is now deprecated and so are multiple methods returning this type from <code>WeldInstance</code></p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>The reasons for this removal is that the very same feature was accepted into CDI specification so you can now use CDI API interfaces to achieve the same.</p>
+                  </li>
+                  <li>
+                  <p>For more information, take a look at <a href="https://github.com/eclipse-ee4j/cdi/blob/master/api/src/main/java/jakarta/enterprise/inject/Instance.java#L266-L315"><code>Instance.Handle</code> class from CDI API</a>.</p>
+                  </li>
+                  <li>
+                  <p>And again, a <a href="https://issues.redhat.com/browse/WELD-2685">link to the relevant issue</a>.</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>CDI has had a similar cleanup and some long deprecated API methods were removed; glance at <a href="https://github.com/eclipse-ee4j/cdi/issues/472">this GitHub issue</a> if you want to learn more about that.</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_empty_beans_xml_interpretation">Empty `beans.xml interpretation</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>There is one breaking change in CDI 4.0 that should be mentioned here - change of default interpretation of empty <code>beans.xml</code> descriptor.
+                  Up until CDI 3.0, leaving this file empty meant discovery mode <code>all</code> whereas starting with CDI 4 it now defaults to <code>annotated</code> discovery mode.
+                  As per specification, in <code>all</code> discovery mode, all classes in bean archive are scanned and if fitting, turned into beans.
+                  However, <code>annotated</code> discovery mode only scans classes with <em>bean defining annotations</em>.
+                  Therefore, this change can be breaking for lots of applications using empty <code>beans.xml</code> and relying on CDI to discover classes without annotations.
+                  In order to ease the transition to this new default, CDI 4 specification says the following:</p>
+                  </div>
+                  <div class="quoteblock">
+                  <blockquote>
+                  <div class="paragraph">
+                  <p>For compatibility with CDI versions prior to 4.0, CDI Full products must contain an option that causes an archive with empty beans.xml to be considered an explicit bean archive.</p>
+                  </div>
+                  </blockquote>
+                  </div>
+                  <div class="paragraph">
+                  <p>This option is vendor-dependent and integrators needs to define how to achieve it in their frameworks/platforms.
+                  That being said, Weld has been updated to allow for this.
+                  If you are using Weld tooling to parse <code>beans.xml</code>, chances are, you&#8217;re doing one of these:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Directly invoking parser via <a href="https://github.com/weld/core/blob/5.0.0.Beta1/impl/src/main/java/org/jboss/weld/xml/BeansXmlStreamParser.java"><code>org.jboss.weld.xml.BeansXmlStreamParser</code></a>.</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p><code>BeansXmlStreamParser</code> now has new constructor methods which allow passing <code>BeanDiscoveryMode</code> parameter telling Weld how to interpret empty <code>beans.xml</code>.</p>
+                  </li>
+                  <li>
+                  <p>All former constructors were retained and default to <code>BeanDiscoveryMode.ANNOTATED</code>.</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Indirectly invoking it via an implementation of <code>org.jboss.weld.bootstrap.api.Bootstrap</code> and its <code>parse</code> methods.</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>New variantions of the <code>parse</code> methods were added and accept <code>BeanDiscoveryMode</code> parameter telling Weld how to interpret empty <code>beans.xml</code>.</p>
+                  </li>
+                  <li>
+                  <p>All former variantion of <code>parse</code> methods were retained and default to <code>BeanDiscoveryMode.ANNOTATED</code>.</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>This should give integrators enough leeway to implement the backward compatibility switch.</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_weld_versus_cdi_lite_versus_cdi_full">Weld versus CDI Lite versus CDI Full</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>By far the biggest change in CDI 4.0 is the introduction of CDI Lite.
+                  At this point I should reiterate that I highly recommend looking <a href="https://eclipse-ee4j.github.io/cdi/2021/10/25/way-to-cdi4.html">this article</a> if you don&#8217;t know what CDI Lite is.
+                  In short, CDI Lite is a feature subset of CDI Full that broadens the amount of environments in which CDI can execute; more presicely, it enables CDI in build time oriented frameworks such as Micronaut or Quarkus.
+                  What does that means for Weld users? Nothing much, Weld is and will be a runtime oriented implementation and you can keep using CDI as you did up until now.
+                  More precisely, Weld is so called CDI Full implementation meaning it provides each and every CDI feature and while there were some deprecations and removals, the rest stays the same.</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_build_compatible_extensions">Build Compatible Extensions</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>One of the notable additions to CDI Lite  (and therefore into CDI Full as well) were Build Compatible Extensions (BCE).
+                  These are akin to Portable Extensions but tuned in a way so that they can be used in build time oriented environments as well.
+                  Along with it comes a different language model because <code>AnnotatedType</code> and friends are reflection-heavy and not a good fit for that API.
+                  If you want to learns more, <a href="https://eclipse-ee4j.github.io/cdi/2021/12/03/you-know-build-compatible-extensions.html">here is an excellent article</a> by Ladislav Thon that covers how they work.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>From Weld perspective, you can use BCE as much as you like although they are also executed at runtime, just as Portable Extensions are.
+                  It is still recommended to use Portable Extensions if possible because BCE are (in Weld) implemented via Portable Extensions.
+                  That being said, if you have some portability demands between Lite and Full, you should be able to use BCE as much as you like.</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_integrators_how_to_make_weld_understand_build_compatible_extensions">Integrators - how to make Weld understand Build Compatible Extensions?</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>This part focuses mainly on integrators and describes how Weld implements Build Compatible Extensions and what needs to be done by integrators in order to fully support CDI Lite.</p>
+                  </div>
+                  <div class="sect2">
+                  <h3 id="_weld_lite_extension_translator_module"><code>weld-lite-extension-translator</code> module</h3>
+                  <div class="paragraph">
+                  <p>Weld 5 has a new module that enables Build Compatible Extensions (BCE) and the new language model that goes along with it - <a href="https://github.com/weld/core/tree/5.0.0.Beta1/weld-lite-extension-translator"><code>weld-lite-extension-translator</code></a>.
+                  GAV of this new artifact is <code>org.jboss.weld:weld-lite-extension-translator:5.0.0.Beta1</code>.
+                  As I mentioned in previous point, BCE are executed via a Portable extension.
+                  More precisely, the key class is <a href="https://github.com/weld/core/blob/5.0.0.Beta1/weld-lite-extension-translator/src/main/java/org/jboss/weld/lite/extension/translator/LiteExtensionTranslator.java"><code>WeldLiteExtensionTranslator</code></a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Just like any Portable extension, it needs an entry in <code>META-INF</code> or an instance of this extensions has to be added programmaticaly during Weld bootstrap.
+                  This is where it gets tricky; <strong>it doesn&#8217;t work out of the box in all environments</strong>!</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Weld SE - works out of the box, the extension is automagically added</p>
+                  </li>
+                  <li>
+                  <p>Weld Servlet - works out of the box, the extensions is automagically added</p>
+                  </li>
+                  <li>
+                  <p>EE - <strong>doesn&#8217;t work without integrator registering the extension</strong></p>
+                  </li>
+                  <li>
+                  <p>Any other custom integration - <strong>doesn&#8217;t work without integrator registering the extension</strong></p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>There is of course a reason for it - complex structured deployments (such as EAR or WAR) and the fact that Weld alone cannot know the deployment well enough to make sure this extension wouldn&#8217;t be registered multiple times.
+                  On top of that, you might also want to avoid registering this extension if there are no BCE found inside the deployment which can also be dependent on how the given platform performs such discovery.
+                  Therefore, Weld leaves it up to the integrator (WildFly, GF, Liberty,&#8230;&#8203;) to identify where and when to register this extension for each deployment.</p>
+                  </div>
+                  </div>
+                  <div class="sect2">
+                  <h3 id="_registering_liteextensiontranslator">Registering <code>LiteExtensionTranslator</code></h3>
+                  <div class="paragraph">
+                  <p>Registering the <code>LiteExtensionTranslator</code> can be as easy as adding a <code>META-INF</code> entry with it into some archive in the deployment.
+                  An example of this would be <code>arquillian-container-weld</code>, a test container for Weld applications.
+                  As you can see from <a href="https://github.com/arquillian/arquillian-container-weld/pull/114/files">this pull request</a>, it basically adds a <code>META-INF</code> entry which is sufficient to support new extension model.
+                  Since it a test tool, the extension is always registered without any attempt to optimize it.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>The above solution is nice and clean, but won&#8217;t cut it for any EE integrators.
+                  Instead, you will want to register this extension very similarly to how you currently register <a href="https://github.com/weld/core/blob/5.0.0.Beta1/probe/core/src/main/java/org/jboss/weld/probe/ProbeExtension.java"><code>ProbeExtension</code></a> - add it programmatically as part of the CDI deployment.
+                  As mentioned above, this extension should to be registered at most once per deployment, so I&#8217;d recommend welding (pun intended) this directly into your <code>org.jboss.weld.bootstrap.spi.CDI11Deployment</code> implementation.
+                  Because WildFly does not yet have a public branch with this, I can at least point to how <a href="https://github.com/wildfly/wildfly/blob/main/weld/subsystem/src/main/java/org/jboss/as/weld/deployment/processors/DevelopmentModeProcessor.java#L138-L139">it registers <code>ProbeExtension</code></a>.
+                  With a little bit of digging, it boils down to <a href="https://github.com/wildfly/wildfly/blob/main/weld/subsystem/src/main/java/org/jboss/as/weld/deployment/WeldDeployment.java#L97">creating <code>CDI11Deployment</code> impl</a> with list of extensions already containing this one.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Which brings us to the second point - I&#8217;d recommend integrators to optimize this process and only register/include <code>LiteExtensionTranslator</code> when there is at least one BCE present in any given deployment.
+                  The reason being that this extension has to monitor a very wide range of events including <code>ProcessAnnotatedType&lt;?&gt;</code> for all types in order to properly implement BCE.
+                  Many integrators can perform BCE detection in their own ways (such as Jandex in WildFly) but for those that want a generic solution, take a look at <code>org.jboss.weld.lite.extension.translator.BuildCompatibleExtensionLoader</code> which is a utility class alowing to perform a standard service discovery process with given <code>ClassLoader</code> and returns the set of discovered BCE classes.
+                  You can then instantiate <code>LiteExtensionTranslator</code> via a constructor that takes this set as an input; or skip registering it if you haven&#8217;t found any BCE at all.</p>
+                  </div>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_tck_structural_changes_and_lang_model_tcks">TCK structural changes and lang model TCKs</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>Few paragraphs above I mentioned new language model used by Build Compatible Extensions.
+                  Obviously, this needed some testing and so CDI TCK has a separate module for it; see <a href="https://github.com/eclipse-ee4j/cdi-tck/tree/4.0.0-RC2/lang-model"><code>lang-model</code> module and its README</a>.
+                  Weld tests and passes these TCKs via <a href="https://github.com/weld/core/tree/5.0.0.Beta1/lang-model-tck"><code>lang-model-tck</code> module</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Next change was a separation of tests between pure CDI tests and tests requiring other Jakarta EE technologies such as JSF, EL and other.
+                  Many of these are candidates for move into their respective specifications but are for now still hosted in CDI TCK.
+                  All of these tests now reside under a <a href="https://github.com/eclipse-ee4j/cdi-tck/tree/4.0.0-RC2/web">separate module</a> with GAV <code>jakarta.enterprise:cdi-tck-web-impl</code>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Lastly, due to the split between CDI Lite and Full and the ability to have CDI implementations only for Lite, all TCKs had to be reviewed and a new test category was added - <a href="https://github.com/eclipse-ee4j/cdi-tck/blob/4.0.0-RC2/impl/src/main/java/org/jboss/cdi/tck/TestGroups.java#L37"><code>cdi-full</code></a>.
+                  It is easy to guess that this category was assigned to tests that are supposed to only execute in CDI Full implementations; i.e. tests containing features that aren&#8217;t present in CDI Lite.
+                  Weld, as noted before, is a CDI Full implementation and as such passes all TCKs.
+                  The current setup used for TCK execution can be read from <a href="https://github.com/weld/core/blob/5.0.0.Beta1/jboss-tck-runner/pom.xml">this POM file</a>.</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_more_in_depth_overview_of_resolved_issues_in_weld_5">More in-depth overview of resolved issues in Weld 5</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>Finally, for those who would like to inspect a more detailed list of changes, here are links to release notes of all version 5 releases up to and including Beta1:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p><a href="https://issues.redhat.com/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12358586">Weld 5.0.0.Alpha1 Release Notes</a></p>
+                  </li>
+                  <li>
+                  <p><a href="https://issues.redhat.com/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12378774">Weld 5.0.0.Alpha2 Release Notes</a></p>
+                  </li>
+                  <li>
+                  <p><a href="https://issues.redhat.com/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12378495">Weld 5.0.0.Beta1 Release Notes</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.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=12378495" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </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>
@@ -472,126 +781,7 @@ <h2 id="_wildfly_patch">WildFly Patch</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2021/01/13/weld-316Final/">Weld 3.1.6.Final</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2021-1-13
-                  &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.6.Final is now available and brings a dosage of bug fixes and updates with it.
-                  Without further due, let&#8217;s dive straight into it!</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>Fix for decorators operating on interfaces with default methods (<a href="https://issues.jboss.org/browse/WELD-2647" target="_blank" rel="noopener">WELD-2647</a>)</p>
-                  </li>
-                  <li>
-                  <p>Weld will no longer try to load classes for specific JDK version when using multi-release JARs (<a href="https://issues.jboss.org/browse/WELD-2652" target="_blank" rel="noopener">WELD-2652</a>)</p>
-                  </li>
-                  <li>
-                  <p><code>ProxyFactory</code> was changed to produce more deterministic and sensible names when based off interfaces (<a href="https://issues.jboss.org/browse/WELD-2618" target="_blank" rel="noopener">WELD-2618</a>)</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>NOTE: this slightly changes names of generated proxy classes but has no effect on the functionality itself</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Weld Servlet</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Detect Jetty server in GWT 2.8+ test environment (<a href="https://issues.jboss.org/browse/WELD-2635" target="_blank" rel="noopener">WELD-2635</a>)</p>
-                  </li>
-                  <li>
-                  <p>Injection into Undertow servlet listener now works as intended (<a href="https://issues.jboss.org/browse/WELD-2636" target="_blank" rel="noopener">WELD-2636</a>)</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>This should work from Undertow 2.2.0.Final onwards</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Weld SE</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Bean defining annotation can be specified as generic <code>SeContainerInitializer</code> property (<a href="https://issues.jboss.org/browse/WELD-2639" target="_blank" rel="noopener">WELD-2639</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Other bits</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Fixed issue preventing upgrade of surefire plugin in our testsuite (<a href="https://issues.jboss.org/browse/WELD-2634" target="_blank" rel="noopener">WELD-2634</a>)</p>
-                  </li>
-                  <li>
-                  <p>Several corrections to OSGi package configuration (<a href="https://issues.jboss.org/browse/WELD-2642" target="_blank" rel="noopener">WELD-2642</a>, <a href="https://issues.jboss.org/browse/WELD-2644" target="_blank" rel="noopener">WELD-2644</a>, <a href="https://issues.jboss.org/browse/WELD-2645" target="_blank" rel="noopener">WELD-2645</a>, <a href="https://issues.jboss.org/browse/WELD-2646" target="_blank" rel="noopener">WELD-2646</a>)</p>
-                  </li>
-                  <li>
-                  <p>Re-introduce multi HTML documentation output in best-effort mode; this is mainly to keep old links working (<a href="https://issues.jboss.org/browse/WELD-2640" target="_blank" rel="noopener">WELD-2640</a>)</p>
-                  </li>
-                  <li>
-                  <p>Fix intermittent test failure in <code>DispatchingTest</code> caused by race condition (<a href="https://issues.jboss.org/browse/WELD-2650" target="_blank" rel="noopener">WELD-2650</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.6.Final/wildfly-21.0.2.Final-weld-3.1.6.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly 21.0.2.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.6.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=12346955" 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>
+              <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/19.html" class="page-link">19</a> <a href="/news/page/20.html" class="page-link">20</a> <a href="/news/page/6.html" class="next-link">Next</a> </div>
               <hr>
               <div>
                 <a href="http://weld.cdi-spec.org/news.atom">
diff --git a/news/page/6.html b/news/page/6.html
index b7e3ac0e..6b599320 100644
--- a/news/page/6.html
+++ b/news/page/6.html
@@ -141,6 +141,125 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2021/01/13/weld-316Final/">Weld 3.1.6.Final</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2021-1-13
+                  &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.6.Final is now available and brings a dosage of bug fixes and updates with it.
+                  Without further due, let&#8217;s dive straight into it!</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>Fix for decorators operating on interfaces with default methods (<a href="https://issues.jboss.org/browse/WELD-2647" target="_blank" rel="noopener">WELD-2647</a>)</p>
+                  </li>
+                  <li>
+                  <p>Weld will no longer try to load classes for specific JDK version when using multi-release JARs (<a href="https://issues.jboss.org/browse/WELD-2652" target="_blank" rel="noopener">WELD-2652</a>)</p>
+                  </li>
+                  <li>
+                  <p><code>ProxyFactory</code> was changed to produce more deterministic and sensible names when based off interfaces (<a href="https://issues.jboss.org/browse/WELD-2618" target="_blank" rel="noopener">WELD-2618</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>NOTE: this slightly changes names of generated proxy classes but has no effect on the functionality itself</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Weld Servlet</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Detect Jetty server in GWT 2.8+ test environment (<a href="https://issues.jboss.org/browse/WELD-2635" target="_blank" rel="noopener">WELD-2635</a>)</p>
+                  </li>
+                  <li>
+                  <p>Injection into Undertow servlet listener now works as intended (<a href="https://issues.jboss.org/browse/WELD-2636" target="_blank" rel="noopener">WELD-2636</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>This should work from Undertow 2.2.0.Final onwards</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Weld SE</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Bean defining annotation can be specified as generic <code>SeContainerInitializer</code> property (<a href="https://issues.jboss.org/browse/WELD-2639" target="_blank" rel="noopener">WELD-2639</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Other bits</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Fixed issue preventing upgrade of surefire plugin in our testsuite (<a href="https://issues.jboss.org/browse/WELD-2634" target="_blank" rel="noopener">WELD-2634</a>)</p>
+                  </li>
+                  <li>
+                  <p>Several corrections to OSGi package configuration (<a href="https://issues.jboss.org/browse/WELD-2642" target="_blank" rel="noopener">WELD-2642</a>, <a href="https://issues.jboss.org/browse/WELD-2644" target="_blank" rel="noopener">WELD-2644</a>, <a href="https://issues.jboss.org/browse/WELD-2645" target="_blank" rel="noopener">WELD-2645</a>, <a href="https://issues.jboss.org/browse/WELD-2646" target="_blank" rel="noopener">WELD-2646</a>)</p>
+                  </li>
+                  <li>
+                  <p>Re-introduce multi HTML documentation output in best-effort mode; this is mainly to keep old links working (<a href="https://issues.jboss.org/browse/WELD-2640" target="_blank" rel="noopener">WELD-2640</a>)</p>
+                  </li>
+                  <li>
+                  <p>Fix intermittent test failure in <code>DispatchingTest</code> caused by race condition (<a href="https://issues.jboss.org/browse/WELD-2650" target="_blank" rel="noopener">WELD-2650</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.6.Final/wildfly-21.0.2.Final-weld-3.1.6.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly 21.0.2.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.6.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=12346955" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2020/12/16/weld-400Final/">Weld 4.0.0.Final</a>
@@ -559,98 +678,7 @@ <h2 id="_development_plans">Development Plans</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2020/03/28/weld-314Final/">Weld 3.1.4.Final</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2020-3-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>New Weld version is here, say hello to Weld 3.1.4.Final.
-                  There are only few issues included in this release, so let&#8217;s take a look at them.</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><code>ObserverMethodConfigurator</code> initialized by reading an <code>AnnotatedType</code> previously didn&#8217;t set the method as async when it should (<a href="https://issues.jboss.org/browse/WELD-2609" target="_blank" rel="noopener">WELD-2609</a>)</p>
-                  </li>
-                  <li>
-                  <p>Fixed observability of <code>@Destroyed</code> events for Conversation context when there are multiple WARs deployed (<a href="https://issues.jboss.org/browse/WELD-2610" target="_blank" rel="noopener">WELD-2610</a>)</p>
-                  </li>
-                  <li>
-                  <p>After a failed attempt to restore a conversation, Weld could omit firing <code>@Initialized</code> event; this is now working properly (<a href="https://issues.jboss.org/browse/WELD-2611" target="_blank" rel="noopener">WELD-2611</a>)</p>
-                  </li>
-                  <li>
-                  <p>Cleanup of stored conversations required unnecessarily many locks simultaneously which could lead to deadlock on some servers (<a href="https://issues.jboss.org/browse/WELD-2612" target="_blank" rel="noopener">WELD-2612</a>)</p>
-                  </li>
-                  <li>
-                  <p>Removed <code>Unsafe</code> usage as means of cracking open <code>ClassLoader</code> for proxy definition (<a href="https://issues.jboss.org/browse/WELD-2613" target="_blank" rel="noopener">WELD-2613</a>)</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>This only helped to hide <code>IllegalAccess</code> warning on JDK 11 (which will now show again)</p>
-                  </li>
-                  <li>
-                  <p>Starting with JDK 12 and newer, <code>Unsafe</code> doesn&#8217;t work at all making this solution obsolete</p>
-                  </li>
-                  <li>
-                  <p>We&#8217;ve created (<a href="https://issues.jboss.org/browse/WELD-2619" target="_blank" rel="noopener">WELD-2619</a>) in order to search for better solution that would work across all JDK versions</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Using <code>HttpSessionContext.destroy()</code> could sometimes not destroy the instance if it wasn&#8217;t used in current request (<a href="https://issues.jboss.org/browse/WELD-2615" target="_blank" rel="noopener">WELD-2615</a>)</p>
-                  </li>
-                  <li>
-                  <p>Fix OSGi versions for EE dependencies (<a href="https://issues.jboss.org/browse/WELD-2616" target="_blank" rel="noopener">WELD-2616</a>)</p>
-                  </li>
-                  <li>
-                  <p>Properly close stream after reading <code>weld.properties</code> (<a href="https://issues.jboss.org/browse/WELD-2606" target="_blank" rel="noopener">WELD-2606</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.4.Final/wildfly-19.0.0.Final-weld-3.1.4.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly 19.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.1.4.Final/en-US/html/" target="_blank" rel="noopener">Documentation</a> &#93;
-                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12343306" 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>
+              <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/19.html" class="page-link">19</a> <a href="/news/page/20.html" class="page-link">20</a> <a href="/news/page/7.html" class="next-link">Next</a> </div>
               <hr>
               <div>
                 <a href="http://weld.cdi-spec.org/news.atom">
diff --git a/news/page/7.html b/news/page/7.html
index ddbe3e94..4d415dde 100644
--- a/news/page/7.html
+++ b/news/page/7.html
@@ -141,6 +141,97 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2020/03/28/weld-314Final/">Weld 3.1.4.Final</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2020-3-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>New Weld version is here, say hello to Weld 3.1.4.Final.
+                  There are only few issues included in this release, so let&#8217;s take a look at them.</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><code>ObserverMethodConfigurator</code> initialized by reading an <code>AnnotatedType</code> previously didn&#8217;t set the method as async when it should (<a href="https://issues.jboss.org/browse/WELD-2609" target="_blank" rel="noopener">WELD-2609</a>)</p>
+                  </li>
+                  <li>
+                  <p>Fixed observability of <code>@Destroyed</code> events for Conversation context when there are multiple WARs deployed (<a href="https://issues.jboss.org/browse/WELD-2610" target="_blank" rel="noopener">WELD-2610</a>)</p>
+                  </li>
+                  <li>
+                  <p>After a failed attempt to restore a conversation, Weld could omit firing <code>@Initialized</code> event; this is now working properly (<a href="https://issues.jboss.org/browse/WELD-2611" target="_blank" rel="noopener">WELD-2611</a>)</p>
+                  </li>
+                  <li>
+                  <p>Cleanup of stored conversations required unnecessarily many locks simultaneously which could lead to deadlock on some servers (<a href="https://issues.jboss.org/browse/WELD-2612" target="_blank" rel="noopener">WELD-2612</a>)</p>
+                  </li>
+                  <li>
+                  <p>Removed <code>Unsafe</code> usage as means of cracking open <code>ClassLoader</code> for proxy definition (<a href="https://issues.jboss.org/browse/WELD-2613" target="_blank" rel="noopener">WELD-2613</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>This only helped to hide <code>IllegalAccess</code> warning on JDK 11 (which will now show again)</p>
+                  </li>
+                  <li>
+                  <p>Starting with JDK 12 and newer, <code>Unsafe</code> doesn&#8217;t work at all making this solution obsolete</p>
+                  </li>
+                  <li>
+                  <p>We&#8217;ve created (<a href="https://issues.jboss.org/browse/WELD-2619" target="_blank" rel="noopener">WELD-2619</a>) in order to search for better solution that would work across all JDK versions</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Using <code>HttpSessionContext.destroy()</code> could sometimes not destroy the instance if it wasn&#8217;t used in current request (<a href="https://issues.jboss.org/browse/WELD-2615" target="_blank" rel="noopener">WELD-2615</a>)</p>
+                  </li>
+                  <li>
+                  <p>Fix OSGi versions for EE dependencies (<a href="https://issues.jboss.org/browse/WELD-2616" target="_blank" rel="noopener">WELD-2616</a>)</p>
+                  </li>
+                  <li>
+                  <p>Properly close stream after reading <code>weld.properties</code> (<a href="https://issues.jboss.org/browse/WELD-2606" target="_blank" rel="noopener">WELD-2606</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.4.Final/wildfly-19.0.0.Final-weld-3.1.4.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly 19.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.1.4.Final/en-US/html/" target="_blank" rel="noopener">Documentation</a> &#93;
+                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12343306" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2019/11/28/weld-313Final/">Weld 3.1.3.Final</a>
@@ -711,110 +802,7 @@ <h2 id="_wildfly_patch">WildFly Patch</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2018/09/26/weld-248Final/">Weld 2.4.8.Final</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2018-9-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 2 has entered maintenance mode with its 2.4.7.Final release earlier this year.
-                  Now we are coming with a maintenance release containing fixes to several nuisances you might have come across.</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>Opt-in enhancement in HTTP session replication, more eager approach (<a href="https://issues.jboss.org/browse/WELD-1130" target="_blank" rel="noopener">WELD-1130</a>)</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Note that WildFly does not need to use this</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p><code>AfterTypeDiscovery</code> did not allow to remove declared interceptors/decorators/alternatives correctly (<a href="https://issues.jboss.org/browse/WELD-2479" target="_blank" rel="noopener">WELD-2479</a>)</p>
-                  </li>
-                  <li>
-                  <p>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-2531" target="_blank" rel="noopener">WELD-2531</a>)</p>
-                  </li>
-                  <li>
-                  <p>Fixed possible race condition appearing during bean index creation (<a href="https://issues.jboss.org/browse/WELD-2532" target="_blank" rel="noopener">WELD-2532</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Weld SE</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Fix NPE which could occur if trying to intercept a method called by constructor (<a href="https://issues.jboss.org/browse/WELD-2473" target="_blank" rel="noopener">WELD-2473</a> and <a href="https://issues.jboss.org/browse/WELD-2478" target="_blank" rel="noopener">WELD-2478</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Other</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Correction to licenses in Probe (<a href="https://issues.jboss.org/browse/WELD-2480" target="_blank" rel="noopener">WELD-2480</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_wildfly_patch">WildFly Patch</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>As usual, a <a href="http://download.jboss.org/weld/2.4.8.Final/wildfly-11.0.0.Final-weld-2.4.8.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly 11.0.0.Final</a> is available.
-                  If you’re not familiar with patching WildFly, check the <a href="/documentation/#12">FAQ</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>&#91; <a href="/download/">Download</a> &#93;
-                  &#91; <a href="http://docs.jboss.org/weld/reference/2.4.8.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=12337222" target="_blank" rel="noopener">Release notes</a> &#93;</p>
-                  </div>
-                  </div>
-                  </div>
-                </div>
-                <hr>
-              </div>
-              <div class="pagination-links"><a href="/news/page/6.html" class="previous-link">Previous</a> <a href="/news/" class="page-link">1</a> <a href="/news/page/2.html" class="page-link">2</a> <span class="skip">...</span><a href="/news/page/6.html" class="page-link">6</a> <span class="current-page">7</span> <a href="/news/page/8.html" class="page-link">8</a> <span class="skip">...</span><a href="/news/page/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>
+              <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/19.html" class="page-link">19</a> <a href="/news/page/20.html" class="page-link">20</a> <a href="/news/page/8.html" class="next-link">Next</a> </div>
               <hr>
               <div>
                 <a href="http://weld.cdi-spec.org/news.atom">
diff --git a/news/page/8.html b/news/page/8.html
index f60a5876..598d5e32 100644
--- a/news/page/8.html
+++ b/news/page/8.html
@@ -141,6 +141,109 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2018/09/26/weld-248Final/">Weld 2.4.8.Final</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2018-9-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 2 has entered maintenance mode with its 2.4.7.Final release earlier this year.
+                  Now we are coming with a maintenance release containing fixes to several nuisances you might have come across.</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>Opt-in enhancement in HTTP session replication, more eager approach (<a href="https://issues.jboss.org/browse/WELD-1130" target="_blank" rel="noopener">WELD-1130</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Note that WildFly does not need to use this</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p><code>AfterTypeDiscovery</code> did not allow to remove declared interceptors/decorators/alternatives correctly (<a href="https://issues.jboss.org/browse/WELD-2479" target="_blank" rel="noopener">WELD-2479</a>)</p>
+                  </li>
+                  <li>
+                  <p>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-2531" target="_blank" rel="noopener">WELD-2531</a>)</p>
+                  </li>
+                  <li>
+                  <p>Fixed possible race condition appearing during bean index creation (<a href="https://issues.jboss.org/browse/WELD-2532" target="_blank" rel="noopener">WELD-2532</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Weld SE</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Fix NPE which could occur if trying to intercept a method called by constructor (<a href="https://issues.jboss.org/browse/WELD-2473" target="_blank" rel="noopener">WELD-2473</a> and <a href="https://issues.jboss.org/browse/WELD-2478" target="_blank" rel="noopener">WELD-2478</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Other</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Correction to licenses in Probe (<a href="https://issues.jboss.org/browse/WELD-2480" target="_blank" rel="noopener">WELD-2480</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_wildfly_patch">WildFly Patch</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>As usual, a <a href="http://download.jboss.org/weld/2.4.8.Final/wildfly-11.0.0.Final-weld-2.4.8.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly 11.0.0.Final</a> is available.
+                  If you’re not familiar with patching WildFly, check the <a href="/documentation/#12">FAQ</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="/download/">Download</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/2.4.8.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=12337222" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2018/07/26/weld-305Final/">Weld 3.0.5.Final</a>
@@ -675,108 +778,7 @@ <h2 id="_wildfly_patch">WildFly Patch</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2018/02/09/weld-303Final/">Weld 3.0.3.Final</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2018-2-9
-                  &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>How do you cook Weld 3.0.3.Final?
-                  You start with a speck of bug fixes add some proxy generation improvements top it off with adjustments for integrators.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Notable fixes and improvements:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Weld Core</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Fixed invocation of private observer method in some very specific cases (<a href="https://issues.jboss.org/browse/WELD-2443" target="_blank" rel="noopener">WELD-2443</a>)</p>
-                  </li>
-                  <li>
-                  <p>Container agnostic proxy serialization (<a href="https://issues.jboss.org/browse/WELD-2447" target="_blank" rel="noopener">WELD-2447</a>)</p>
-                  </li>
-                  <li>
-                  <p>Improve shared proxy class instantiation for multiple deployments with relaxed construction enabled (<a href="https://issues.jboss.org/browse/WELD-2448" target="_blank" rel="noopener">WELD-2448</a>)</p>
-                  </li>
-                  <li>
-                  <p><code>beans_1_1.xsd</code> is now known to Weld once again (<a href="https://issues.jboss.org/browse/WELD-2445" target="_blank" rel="noopener">WELD-2445</a>)</p>
-                  </li>
-                  <li>
-                  <p><code>module-info</code> is now ignored during discovery and won&#8217;t give you warnings in log (<a href="https://issues.jboss.org/browse/WELD-2459" target="_blank" rel="noopener">WELD-2459</a>)</p>
-                  </li>
-                  <li>
-                  <p>Enhanced logging of <code>DeploymentException</code>, it should now be possible to glance more from suppressed exceptions (<a href="https://issues.jboss.org/browse/WELD-2453" target="_blank" rel="noopener">WELD-2453</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Weld SE &amp;&amp; Servlet</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>You can now register additional <code>BeanArchiveHandler</code> via <code>ServiceLoader</code> (<a href="https://issues.jboss.org/browse/WELD-2450" target="_blank" rel="noopener">WELD-2450</a>)</p>
-                  </li>
-                  <li>
-                  <p>Multitude of fields/method in <code>Weld</code> SE builder are now <code>protected</code> and hence extendable (<a href="https://issues.jboss.org/browse/WELD-2451" target="_blank" rel="noopener">WELD-2451</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Other</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Improvements in documentation (<a href="https://issues.jboss.org/browse/WELD-2449" target="_blank" rel="noopener">WELD-2449</a>)</p>
-                  </li>
-                  <li>
-                  <p>Weld project now uses SpotBugs instead of FindBugs (<a href="https://issues.jboss.org/browse/WELD-2462" target="_blank" rel="noopener">WELD-2462</a>)</p>
-                  </li>
-                  <li>
-                  <p>OSGi now requires <code>javax.ejb</code> only optionally (<a href="https://issues.jboss.org/browse/WELD-2458" target="_blank" rel="noopener">WELD-2458</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.3.Final/wildfly-11.0.0.Final-weld-3.0.3.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.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=12336197" target="_blank" rel="noopener">Release notes</a> &#93;</p>
-                  </div>
-                  </div>
-                  </div>
-                </div>
-                <hr>
-              </div>
-              <div class="pagination-links"><a href="/news/page/7.html" class="previous-link">Previous</a> <a href="/news/" class="page-link">1</a> <a href="/news/page/2.html" class="page-link">2</a> <span class="skip">...</span><a href="/news/page/7.html" class="page-link">7</a> <span class="current-page">8</span> <a href="/news/page/9.html" class="page-link">9</a> <span class="skip">...</span><a href="/news/page/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>
+              <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/19.html" class="page-link">19</a> <a href="/news/page/20.html" class="page-link">20</a> <a href="/news/page/9.html" class="next-link">Next</a> </div>
               <hr>
               <div>
                 <a href="http://weld.cdi-spec.org/news.atom">
diff --git a/news/page/9.html b/news/page/9.html
index d55fe64f..194d632c 100644
--- a/news/page/9.html
+++ b/news/page/9.html
@@ -141,6 +141,107 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2018/02/09/weld-303Final/">Weld 3.0.3.Final</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2018-2-9
+                  &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>How do you cook Weld 3.0.3.Final?
+                  You start with a speck of bug fixes add some proxy generation improvements top it off with adjustments for integrators.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Notable fixes and improvements:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Weld Core</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Fixed invocation of private observer method in some very specific cases (<a href="https://issues.jboss.org/browse/WELD-2443" target="_blank" rel="noopener">WELD-2443</a>)</p>
+                  </li>
+                  <li>
+                  <p>Container agnostic proxy serialization (<a href="https://issues.jboss.org/browse/WELD-2447" target="_blank" rel="noopener">WELD-2447</a>)</p>
+                  </li>
+                  <li>
+                  <p>Improve shared proxy class instantiation for multiple deployments with relaxed construction enabled (<a href="https://issues.jboss.org/browse/WELD-2448" target="_blank" rel="noopener">WELD-2448</a>)</p>
+                  </li>
+                  <li>
+                  <p><code>beans_1_1.xsd</code> is now known to Weld once again (<a href="https://issues.jboss.org/browse/WELD-2445" target="_blank" rel="noopener">WELD-2445</a>)</p>
+                  </li>
+                  <li>
+                  <p><code>module-info</code> is now ignored during discovery and won&#8217;t give you warnings in log (<a href="https://issues.jboss.org/browse/WELD-2459" target="_blank" rel="noopener">WELD-2459</a>)</p>
+                  </li>
+                  <li>
+                  <p>Enhanced logging of <code>DeploymentException</code>, it should now be possible to glance more from suppressed exceptions (<a href="https://issues.jboss.org/browse/WELD-2453" target="_blank" rel="noopener">WELD-2453</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Weld SE &amp;&amp; Servlet</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>You can now register additional <code>BeanArchiveHandler</code> via <code>ServiceLoader</code> (<a href="https://issues.jboss.org/browse/WELD-2450" target="_blank" rel="noopener">WELD-2450</a>)</p>
+                  </li>
+                  <li>
+                  <p>Multitude of fields/method in <code>Weld</code> SE builder are now <code>protected</code> and hence extendable (<a href="https://issues.jboss.org/browse/WELD-2451" target="_blank" rel="noopener">WELD-2451</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Other</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Improvements in documentation (<a href="https://issues.jboss.org/browse/WELD-2449" target="_blank" rel="noopener">WELD-2449</a>)</p>
+                  </li>
+                  <li>
+                  <p>Weld project now uses SpotBugs instead of FindBugs (<a href="https://issues.jboss.org/browse/WELD-2462" target="_blank" rel="noopener">WELD-2462</a>)</p>
+                  </li>
+                  <li>
+                  <p>OSGi now requires <code>javax.ejb</code> only optionally (<a href="https://issues.jboss.org/browse/WELD-2458" target="_blank" rel="noopener">WELD-2458</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.3.Final/wildfly-11.0.0.Final-weld-3.0.3.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.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=12336197" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2017/12/19/weld-meets-junit5/">Weld meets JUnit 5</a>
@@ -619,144 +720,7 @@ <h2 id="_wildfly_patch">WildFly Patch</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2017/08/25/weld-301Final/">Weld 3.0.1.Final</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2017-8-25
-                  &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.1.Final is out and it brings some bugfixes as well as new version of Weld API - 3.0.SP1.
-                  Among the new things you can find sweet stuff such as an expansion to CDI 2 <code>BeanConfigurator</code> API or the ability to detect that injected object is Weld proxy.
-                  Wait, not only detect - you can also use it do get <code>Metadata</code> or even retrieve the actual contextual instance hidden beneath.
-                  So let&#8217;s see the summary of fixes and improvements, shall we?</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>Revised support for Java 8 default methods (<a href="https://issues.jboss.org/browse/WELD-2407" target="_blank" rel="noopener">WELD-2407</a> and <a href="https://issues.jboss.org/browse/WELD-2405" target="_blank" rel="noopener">WELD-2405</a>)</p>
-                  </li>
-                  <li>
-                  <p>Corrected MIME types for all POMs in Weld core - Nexus 3 will love us now! (<a href="https://issues.jboss.org/browse/WELD-2417" target="_blank" rel="noopener">WELD-2417</a>)</p>
-                  </li>
-                  <li>
-                  <p>Fixed how proxies are created for signed packages (<a href="https://issues.jboss.org/browse/WELD-2402" target="_blank" rel="noopener">WELD-2402</a>)</p>
-                  </li>
-                  <li>
-                  <p>Portable extension events should now be fired in accordance with specification <a href="https://issues.jboss.org/browse/WELD-2393" target="_blank" rel="noopener">WELD-2393</a></p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Weld SE</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Synthetic bean archive can now have discovery mode <code>annotated</code> (<a href="https://issues.jboss.org/browse/WELD-2386" target="_blank" rel="noopener">WELD-2386</a>)</p>
-                  </li>
-                  <li>
-                  <p>Added a convenient static method <code>WeldContainer.current()</code> allowing you to quickly grab your running instance (<a href="https://issues.jboss.org/browse/WELD-2399" target="_blank" rel="noopener">WELD-2399</a>)</p>
-                  </li>
-                  <li>
-                  <p>Fixed a glitch when starting SE container and adding packages via <code>Weld.addPackages()</code> <a href="https://issues.jboss.org/browse/WELD-2395" target="_blank" rel="noopener">WELD-2395</a></p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Weld API/SPI</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Added a way to detect proxies and subclasses (<a href="https://issues.jboss.org/browse/WELD-2407" target="_blank" rel="noopener">WELD-2407</a>)</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Every Weld-enhanced object (subclass/proxy) will now implement <a href="https://github.com/weld/api/tree/3.0.SP1/weld/src/main/java/org/jboss/weld/proxy">new marker interface(s)</a> which grant access to additional data about the bean</p>
-                  </li>
-                  <li>
-                  <p>This also allows to retrieve the underlying contextual instance</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Added <code>WeldBeanConfigurator</code> to API - allows to select an <code>@Alternative</code> which was created using <code>BeanConfigurator</code> (<a href="https://issues.jboss.org/browse/WELD-2412" target="_blank" rel="noopener">WELD-2412</a>)</p>
-                  </li>
-                  <li>
-                  <p>We have enhanced the <code>Environment</code> in Weld SPI so that integrators define whether their bean archives are "EE module aware" or not (<a href="https://issues.jboss.org/browse/WELD-2398" target="_blank" rel="noopener">WELD-2398</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Other</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Under the <code>jboss-as</code> directory of Weld source code, you can now make use of new profiles to create WildFly patches yourself <a href="https://issues.jboss.org/browse/WELD-2397" target="_blank" rel="noopener">WELD-2397</a></p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>To learn more about this, please refer to the <a href="https://github.com/weld/core/blob/3.0.1.Final/README.md#creating-a-patch-file-for-wildfly"><code>README</code> file in our repository</a></p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Weld SE and Weld Servlet now explicitly depends on <code>jboss-classfilewriter</code> in version 1.2+ <a href="https://issues.jboss.org/browse/WELD-2406" target="_blank" rel="noopener">WELD-2406</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.1.Final/wildfly-10.1.0.Final-weld-3.0.1.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly 10.1.0.Final</a> is available.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>But, for those of you who like to stay sharp, we have also created a <a href="http://download.jboss.org/weld/3.0.1.Final/wildfly-11.0.0.Beta1-weld-3.0.1.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly 11.0.0.Beta1</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Please note that there is currently a <a href="https://issues.jboss.org/browse/WFLY-9240">known issue</a> with security context propagation in Weld 3 for WildFly 11.
-                  Though this should only concern people who use the combination of Elytron subsystem and asynchronous CDI events.</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.1.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=12334698" target="_blank" rel="noopener">Release notes</a> &#93;</p>
-                  </div>
-                  </div>
-                  </div>
-                </div>
-                <hr>
-              </div>
-              <div class="pagination-links"><a href="/news/page/8.html" class="previous-link">Previous</a> <a href="/news/" class="page-link">1</a> <a href="/news/page/2.html" class="page-link">2</a> <span class="skip">...</span><a href="/news/page/8.html" class="page-link">8</a> <span class="current-page">9</span> <a href="/news/page/10.html" class="page-link">10</a> <span class="skip">...</span><a href="/news/page/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>
+              <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/19.html" class="page-link">19</a> <a href="/news/page/20.html" class="page-link">20</a> <a href="/news/page/10.html" class="next-link">Next</a> </div>
               <hr>
               <div>
                 <a href="http://weld.cdi-spec.org/news.atom">
diff --git a/news/tags/release/index.html b/news/tags/release/index.html
index f4959503..76064ad9 100644
--- a/news/tags/release/index.html
+++ b/news/tags/release/index.html
@@ -141,6 +141,58 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2024/12/16/weld-600Final/">Weld 6.0.0.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>Since there have been no further bugs reported, Weld <code>6.0.0.CR2</code> has evolved into its <code>Final</code> form.
+                  Say hello to <code>Weld API 6.0.Final</code> as well as <code>Weld Core 6.0.0.Final</code>!</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Since there are no changes from the previous <code>CR2</code> version, early adopters shouldn&#8217;t encounter any unwelcome surprises.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Nonetheless, should you run into any bugs, do get in touch so that we can squash them as soon as possible!</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>And speaking of getting in touch, we recognize that JIRA can be a little daunting, so we are trying to make that easier by <strong>enabling GitHub discussions</strong>.
+                  You can now ask your question in:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p><a href="https://github.com/weld/core/discussions">Weld Core</a> GH discussions</p>
+                  </li>
+                  <li>
+                  <p><a href="https://github.com/weld/api/discussions">Weld API</a> GH discussions</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>And don&#8217;t you worry, the <code>weld-dev</code> mailing list is still kicking plus, for the time being, we are still using JIRA for per-release issue tracking.</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.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=12439250" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2024/12/16/weld-514Final/">Weld 5.1.4.Final</a>
@@ -815,58 +867,6 @@ <h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2023/07/11/weld-511SP1/">Weld 5.1.1.SP1</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2023-7-11
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/release">release</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Matej Novotny
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>A new SP release of Weld 5 is now avaiable.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Latest release, Weld 5.1.1.Final, has shown that one of the changes (<a href="https://issues.redhat.com/browse/WELD-2743">WELD-2743</a>) had unforseen and, sadly, untested consequences.
-                  Some of the integrators and some of community were using <code>BeanManager#getReference</code> in scenarios which were broken by this change.
-                  While the use cases aren&#8217;t explicitly backed by the specification or its TCKs, we decided we don&#8217;t want to break them, especially not in a micro release.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>This SP release therefore aims to correct the above and only adds one other tiny change:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Revert the change of <code>BeanManager#getReference</code> and solve this issue differently (<a href="https://issues.redhat.com/browse/WELD-2745">WELD-2745</a>)</p>
-                  </li>
-                  <li>
-                  <p>Modify how <code>toString()</code> is invoked on proxies of removed EJB beans (<a href="https://issues.redhat.com/browse/WELD-2747">WELD-2747	</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>Big thanks for (<a href="https://github.com/ljnelson">Laird Nelson</a>) and (<a href="https://github.com/arjantijms">Arjan Tijms</a>) for bringing these cases to my attention as well as helping to understand and resolve them!</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>As always, if you find further issues with Weld 5, do let us know.</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.SP1/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=12410330" 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 8d6d1c4c..4f32d025 100644
--- a/news/tags/release/page/2.html
+++ b/news/tags/release/page/2.html
@@ -141,6 +141,58 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2023/07/11/weld-511SP1/">Weld 5.1.1.SP1</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2023-7-11
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/release">release</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Matej Novotny
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>A new SP release of Weld 5 is now avaiable.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Latest release, Weld 5.1.1.Final, has shown that one of the changes (<a href="https://issues.redhat.com/browse/WELD-2743">WELD-2743</a>) had unforseen and, sadly, untested consequences.
+                  Some of the integrators and some of community were using <code>BeanManager#getReference</code> in scenarios which were broken by this change.
+                  While the use cases aren&#8217;t explicitly backed by the specification or its TCKs, we decided we don&#8217;t want to break them, especially not in a micro release.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>This SP release therefore aims to correct the above and only adds one other tiny change:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Revert the change of <code>BeanManager#getReference</code> and solve this issue differently (<a href="https://issues.redhat.com/browse/WELD-2745">WELD-2745</a>)</p>
+                  </li>
+                  <li>
+                  <p>Modify how <code>toString()</code> is invoked on proxies of removed EJB beans (<a href="https://issues.redhat.com/browse/WELD-2747">WELD-2747	</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>Big thanks for (<a href="https://github.com/ljnelson">Laird Nelson</a>) and (<a href="https://github.com/arjantijms">Arjan Tijms</a>) for bringing these cases to my attention as well as helping to understand and resolve them!</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>As always, if you find further issues with Weld 5, do let us know.</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.SP1/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=12410330" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2023/06/12/weld-511Final/">Weld 5.1.1.Final</a>
@@ -656,315 +708,6 @@ <h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2022/01/24/weld-500Beta1/">Weld 5.0.0.Beta1</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2022-1-24
-                  &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>Some of you might have noticed that Weld already had some version 5 releases, namely two Alphas.
-                  Those were a work-in-progress implementations so I didn&#8217;t post any actual release notes as the specification was still undergoing changes.
-                  CDI 4 is now in very much ready-to-fly state as its first CR release has recently landed in Maven Central.
-                  Therefore, here we are with a proper release of Weld API <code>5.0.Beta5</code> and Weld Core <code>5.0.0.Beta1</code> which implements all the bits and pieces of CDI 4.0 plus brings a few more changes and deprecation removals.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>This post will try to cover Weld-side of things meaning anything that changed and is Weld specific or influences integrators in any way.
-                  If you want to learn what&#8217;s new in CDI 4.0, I suggest taking a look at <a href="https://eclipse-ee4j.github.io/cdi/2021/10/25/way-to-cdi4.html">this detailed article</a> I wrote some time ago.
-                  It provides a good overview of all major changes, all of which are implemented in this Weld release.
-                  In case you want to check out the list of JIRA issues for Weld releases, the last chapter will provide links for both Alpha releases as well as this Beta release.
-                  Last but not least, you can also reach out to us via <a href="https://gitter.im/weld/user">Gitter channel</a> or <a href="https://lists.jboss.org/admin/lists/weld-dev.lists.jboss.org/"><code>weld-dev@lists.jboss.org</code> mailing list</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Without further ado, let&#8217;s dive into it!</p>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_target_jdk_version_for_weld_5_and_for_cdi_4_is_now_11">Target JDK version for Weld 5 (and for CDI 4) is now 11</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>Therefore, JDK 11 is now the minimal version required to run Weld.
-                  This is basically a requirement for all Jakarta EE 10 specifications.
-                  On the other hand, Weld 5 is also tested against and supports JDK 17 as well.</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_weld_5_is_no_longer_a_multi_release_mr_jars">Weld 5 is no longer a multi-release (MR) JARs</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>As you might know, Weld 3 and 4 are running some different class defining strategies for JDK 8 or 11+ resulting in an MR JAR solution.
-                  Since JDK 11 is the basis, this is no longer needed and similar workarounds were removed from code.</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_deprecations_and_removals">Deprecations and removals</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>Here is a list of all changes of this nature within Weld APIs:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Multiple methods from <code>org.jboss.weld.serialization.spi.ProxyServices</code> were removed.</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>If you are an integrator, you probably implemented this interface at some point in time; these methods weren&#8217;t used by Weld anyway, so they are now gone for good.</p>
-                  </li>
-                  <li>
-                  <p>Here is a <a href="https://issues.redhat.com/browse/WELD-2702">link to the issue removing it</a>.</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Any integrators basing their implementations of Jandex likely implemented <code>ClassFileInfo</code>; its <code>isTopLevelClass()</code> has been removed.</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Note that this method was redundant and can be replaced by <code>getClassNestingType()</code>.</p>
-                  </li>
-                  <li>
-                  <p>This was removed as part of the above mentioned issue.</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p><code>WeldInstance.Handler</code> class is now deprecated and so are multiple methods returning this type from <code>WeldInstance</code></p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>The reasons for this removal is that the very same feature was accepted into CDI specification so you can now use CDI API interfaces to achieve the same.</p>
-                  </li>
-                  <li>
-                  <p>For more information, take a look at <a href="https://github.com/eclipse-ee4j/cdi/blob/master/api/src/main/java/jakarta/enterprise/inject/Instance.java#L266-L315"><code>Instance.Handle</code> class from CDI API</a>.</p>
-                  </li>
-                  <li>
-                  <p>And again, a <a href="https://issues.redhat.com/browse/WELD-2685">link to the relevant issue</a>.</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>CDI has had a similar cleanup and some long deprecated API methods were removed; glance at <a href="https://github.com/eclipse-ee4j/cdi/issues/472">this GitHub issue</a> if you want to learn more about that.</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_empty_beans_xml_interpretation">Empty `beans.xml interpretation</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>There is one breaking change in CDI 4.0 that should be mentioned here - change of default interpretation of empty <code>beans.xml</code> descriptor.
-                  Up until CDI 3.0, leaving this file empty meant discovery mode <code>all</code> whereas starting with CDI 4 it now defaults to <code>annotated</code> discovery mode.
-                  As per specification, in <code>all</code> discovery mode, all classes in bean archive are scanned and if fitting, turned into beans.
-                  However, <code>annotated</code> discovery mode only scans classes with <em>bean defining annotations</em>.
-                  Therefore, this change can be breaking for lots of applications using empty <code>beans.xml</code> and relying on CDI to discover classes without annotations.
-                  In order to ease the transition to this new default, CDI 4 specification says the following:</p>
-                  </div>
-                  <div class="quoteblock">
-                  <blockquote>
-                  <div class="paragraph">
-                  <p>For compatibility with CDI versions prior to 4.0, CDI Full products must contain an option that causes an archive with empty beans.xml to be considered an explicit bean archive.</p>
-                  </div>
-                  </blockquote>
-                  </div>
-                  <div class="paragraph">
-                  <p>This option is vendor-dependent and integrators needs to define how to achieve it in their frameworks/platforms.
-                  That being said, Weld has been updated to allow for this.
-                  If you are using Weld tooling to parse <code>beans.xml</code>, chances are, you&#8217;re doing one of these:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Directly invoking parser via <a href="https://github.com/weld/core/blob/5.0.0.Beta1/impl/src/main/java/org/jboss/weld/xml/BeansXmlStreamParser.java"><code>org.jboss.weld.xml.BeansXmlStreamParser</code></a>.</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p><code>BeansXmlStreamParser</code> now has new constructor methods which allow passing <code>BeanDiscoveryMode</code> parameter telling Weld how to interpret empty <code>beans.xml</code>.</p>
-                  </li>
-                  <li>
-                  <p>All former constructors were retained and default to <code>BeanDiscoveryMode.ANNOTATED</code>.</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Indirectly invoking it via an implementation of <code>org.jboss.weld.bootstrap.api.Bootstrap</code> and its <code>parse</code> methods.</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>New variantions of the <code>parse</code> methods were added and accept <code>BeanDiscoveryMode</code> parameter telling Weld how to interpret empty <code>beans.xml</code>.</p>
-                  </li>
-                  <li>
-                  <p>All former variantion of <code>parse</code> methods were retained and default to <code>BeanDiscoveryMode.ANNOTATED</code>.</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>This should give integrators enough leeway to implement the backward compatibility switch.</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_weld_versus_cdi_lite_versus_cdi_full">Weld versus CDI Lite versus CDI Full</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>By far the biggest change in CDI 4.0 is the introduction of CDI Lite.
-                  At this point I should reiterate that I highly recommend looking <a href="https://eclipse-ee4j.github.io/cdi/2021/10/25/way-to-cdi4.html">this article</a> if you don&#8217;t know what CDI Lite is.
-                  In short, CDI Lite is a feature subset of CDI Full that broadens the amount of environments in which CDI can execute; more presicely, it enables CDI in build time oriented frameworks such as Micronaut or Quarkus.
-                  What does that means for Weld users? Nothing much, Weld is and will be a runtime oriented implementation and you can keep using CDI as you did up until now.
-                  More precisely, Weld is so called CDI Full implementation meaning it provides each and every CDI feature and while there were some deprecations and removals, the rest stays the same.</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_build_compatible_extensions">Build Compatible Extensions</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>One of the notable additions to CDI Lite  (and therefore into CDI Full as well) were Build Compatible Extensions (BCE).
-                  These are akin to Portable Extensions but tuned in a way so that they can be used in build time oriented environments as well.
-                  Along with it comes a different language model because <code>AnnotatedType</code> and friends are reflection-heavy and not a good fit for that API.
-                  If you want to learns more, <a href="https://eclipse-ee4j.github.io/cdi/2021/12/03/you-know-build-compatible-extensions.html">here is an excellent article</a> by Ladislav Thon that covers how they work.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>From Weld perspective, you can use BCE as much as you like although they are also executed at runtime, just as Portable Extensions are.
-                  It is still recommended to use Portable Extensions if possible because BCE are (in Weld) implemented via Portable Extensions.
-                  That being said, if you have some portability demands between Lite and Full, you should be able to use BCE as much as you like.</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_integrators_how_to_make_weld_understand_build_compatible_extensions">Integrators - how to make Weld understand Build Compatible Extensions?</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>This part focuses mainly on integrators and describes how Weld implements Build Compatible Extensions and what needs to be done by integrators in order to fully support CDI Lite.</p>
-                  </div>
-                  <div class="sect2">
-                  <h3 id="_weld_lite_extension_translator_module"><code>weld-lite-extension-translator</code> module</h3>
-                  <div class="paragraph">
-                  <p>Weld 5 has a new module that enables Build Compatible Extensions (BCE) and the new language model that goes along with it - <a href="https://github.com/weld/core/tree/5.0.0.Beta1/weld-lite-extension-translator"><code>weld-lite-extension-translator</code></a>.
-                  GAV of this new artifact is <code>org.jboss.weld:weld-lite-extension-translator:5.0.0.Beta1</code>.
-                  As I mentioned in previous point, BCE are executed via a Portable extension.
-                  More precisely, the key class is <a href="https://github.com/weld/core/blob/5.0.0.Beta1/weld-lite-extension-translator/src/main/java/org/jboss/weld/lite/extension/translator/LiteExtensionTranslator.java"><code>WeldLiteExtensionTranslator</code></a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Just like any Portable extension, it needs an entry in <code>META-INF</code> or an instance of this extensions has to be added programmaticaly during Weld bootstrap.
-                  This is where it gets tricky; <strong>it doesn&#8217;t work out of the box in all environments</strong>!</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Weld SE - works out of the box, the extension is automagically added</p>
-                  </li>
-                  <li>
-                  <p>Weld Servlet - works out of the box, the extensions is automagically added</p>
-                  </li>
-                  <li>
-                  <p>EE - <strong>doesn&#8217;t work without integrator registering the extension</strong></p>
-                  </li>
-                  <li>
-                  <p>Any other custom integration - <strong>doesn&#8217;t work without integrator registering the extension</strong></p>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>There is of course a reason for it - complex structured deployments (such as EAR or WAR) and the fact that Weld alone cannot know the deployment well enough to make sure this extension wouldn&#8217;t be registered multiple times.
-                  On top of that, you might also want to avoid registering this extension if there are no BCE found inside the deployment which can also be dependent on how the given platform performs such discovery.
-                  Therefore, Weld leaves it up to the integrator (WildFly, GF, Liberty,&#8230;&#8203;) to identify where and when to register this extension for each deployment.</p>
-                  </div>
-                  </div>
-                  <div class="sect2">
-                  <h3 id="_registering_liteextensiontranslator">Registering <code>LiteExtensionTranslator</code></h3>
-                  <div class="paragraph">
-                  <p>Registering the <code>LiteExtensionTranslator</code> can be as easy as adding a <code>META-INF</code> entry with it into some archive in the deployment.
-                  An example of this would be <code>arquillian-container-weld</code>, a test container for Weld applications.
-                  As you can see from <a href="https://github.com/arquillian/arquillian-container-weld/pull/114/files">this pull request</a>, it basically adds a <code>META-INF</code> entry which is sufficient to support new extension model.
-                  Since it a test tool, the extension is always registered without any attempt to optimize it.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>The above solution is nice and clean, but won&#8217;t cut it for any EE integrators.
-                  Instead, you will want to register this extension very similarly to how you currently register <a href="https://github.com/weld/core/blob/5.0.0.Beta1/probe/core/src/main/java/org/jboss/weld/probe/ProbeExtension.java"><code>ProbeExtension</code></a> - add it programmatically as part of the CDI deployment.
-                  As mentioned above, this extension should to be registered at most once per deployment, so I&#8217;d recommend welding (pun intended) this directly into your <code>org.jboss.weld.bootstrap.spi.CDI11Deployment</code> implementation.
-                  Because WildFly does not yet have a public branch with this, I can at least point to how <a href="https://github.com/wildfly/wildfly/blob/main/weld/subsystem/src/main/java/org/jboss/as/weld/deployment/processors/DevelopmentModeProcessor.java#L138-L139">it registers <code>ProbeExtension</code></a>.
-                  With a little bit of digging, it boils down to <a href="https://github.com/wildfly/wildfly/blob/main/weld/subsystem/src/main/java/org/jboss/as/weld/deployment/WeldDeployment.java#L97">creating <code>CDI11Deployment</code> impl</a> with list of extensions already containing this one.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Which brings us to the second point - I&#8217;d recommend integrators to optimize this process and only register/include <code>LiteExtensionTranslator</code> when there is at least one BCE present in any given deployment.
-                  The reason being that this extension has to monitor a very wide range of events including <code>ProcessAnnotatedType&lt;?&gt;</code> for all types in order to properly implement BCE.
-                  Many integrators can perform BCE detection in their own ways (such as Jandex in WildFly) but for those that want a generic solution, take a look at <code>org.jboss.weld.lite.extension.translator.BuildCompatibleExtensionLoader</code> which is a utility class alowing to perform a standard service discovery process with given <code>ClassLoader</code> and returns the set of discovered BCE classes.
-                  You can then instantiate <code>LiteExtensionTranslator</code> via a constructor that takes this set as an input; or skip registering it if you haven&#8217;t found any BCE at all.</p>
-                  </div>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_tck_structural_changes_and_lang_model_tcks">TCK structural changes and lang model TCKs</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>Few paragraphs above I mentioned new language model used by Build Compatible Extensions.
-                  Obviously, this needed some testing and so CDI TCK has a separate module for it; see <a href="https://github.com/eclipse-ee4j/cdi-tck/tree/4.0.0-RC2/lang-model"><code>lang-model</code> module and its README</a>.
-                  Weld tests and passes these TCKs via <a href="https://github.com/weld/core/tree/5.0.0.Beta1/lang-model-tck"><code>lang-model-tck</code> module</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Next change was a separation of tests between pure CDI tests and tests requiring other Jakarta EE technologies such as JSF, EL and other.
-                  Many of these are candidates for move into their respective specifications but are for now still hosted in CDI TCK.
-                  All of these tests now reside under a <a href="https://github.com/eclipse-ee4j/cdi-tck/tree/4.0.0-RC2/web">separate module</a> with GAV <code>jakarta.enterprise:cdi-tck-web-impl</code>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Lastly, due to the split between CDI Lite and Full and the ability to have CDI implementations only for Lite, all TCKs had to be reviewed and a new test category was added - <a href="https://github.com/eclipse-ee4j/cdi-tck/blob/4.0.0-RC2/impl/src/main/java/org/jboss/cdi/tck/TestGroups.java#L37"><code>cdi-full</code></a>.
-                  It is easy to guess that this category was assigned to tests that are supposed to only execute in CDI Full implementations; i.e. tests containing features that aren&#8217;t present in CDI Lite.
-                  Weld, as noted before, is a CDI Full implementation and as such passes all TCKs.
-                  The current setup used for TCK execution can be read from <a href="https://github.com/weld/core/blob/5.0.0.Beta1/jboss-tck-runner/pom.xml">this POM file</a>.</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_more_in_depth_overview_of_resolved_issues_in_weld_5">More in-depth overview of resolved issues in Weld 5</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>Finally, for those who would like to inspect a more detailed list of changes, here are links to release notes of all version 5 releases up to and including Beta1:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p><a href="https://issues.redhat.com/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12358586">Weld 5.0.0.Alpha1 Release Notes</a></p>
-                  </li>
-                  <li>
-                  <p><a href="https://issues.redhat.com/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12378774">Weld 5.0.0.Alpha2 Release Notes</a></p>
-                  </li>
-                  <li>
-                  <p><a href="https://issues.redhat.com/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12378495">Weld 5.0.0.Beta1 Release Notes</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.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=12378495" target="_blank" rel="noopener">Release notes</a> &#93;</p>
-                  </div>
-                  </div>
-                  </div>
-                </div>
-                <hr>
-              </div>
               <div class="pagination-links"><a href="/news/tags/release/" class="previous-link">Previous</a> <a href="/news/tags/release/" class="page-link">1</a> <span class="current-page">2</span> <a href="/news/tags/release/page/3.html" class="page-link">3</a> <span class="skip">...</span><a href="/news/tags/release/page/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 ef0f9e89..1bb5a47a 100644
--- a/news/tags/release/page/3.html
+++ b/news/tags/release/page/3.html
@@ -141,6 +141,315 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2022/01/24/weld-500Beta1/">Weld 5.0.0.Beta1</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2022-1-24
+                  &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>Some of you might have noticed that Weld already had some version 5 releases, namely two Alphas.
+                  Those were a work-in-progress implementations so I didn&#8217;t post any actual release notes as the specification was still undergoing changes.
+                  CDI 4 is now in very much ready-to-fly state as its first CR release has recently landed in Maven Central.
+                  Therefore, here we are with a proper release of Weld API <code>5.0.Beta5</code> and Weld Core <code>5.0.0.Beta1</code> which implements all the bits and pieces of CDI 4.0 plus brings a few more changes and deprecation removals.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>This post will try to cover Weld-side of things meaning anything that changed and is Weld specific or influences integrators in any way.
+                  If you want to learn what&#8217;s new in CDI 4.0, I suggest taking a look at <a href="https://eclipse-ee4j.github.io/cdi/2021/10/25/way-to-cdi4.html">this detailed article</a> I wrote some time ago.
+                  It provides a good overview of all major changes, all of which are implemented in this Weld release.
+                  In case you want to check out the list of JIRA issues for Weld releases, the last chapter will provide links for both Alpha releases as well as this Beta release.
+                  Last but not least, you can also reach out to us via <a href="https://gitter.im/weld/user">Gitter channel</a> or <a href="https://lists.jboss.org/admin/lists/weld-dev.lists.jboss.org/"><code>weld-dev@lists.jboss.org</code> mailing list</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Without further ado, let&#8217;s dive into it!</p>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_target_jdk_version_for_weld_5_and_for_cdi_4_is_now_11">Target JDK version for Weld 5 (and for CDI 4) is now 11</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>Therefore, JDK 11 is now the minimal version required to run Weld.
+                  This is basically a requirement for all Jakarta EE 10 specifications.
+                  On the other hand, Weld 5 is also tested against and supports JDK 17 as well.</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_weld_5_is_no_longer_a_multi_release_mr_jars">Weld 5 is no longer a multi-release (MR) JARs</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>As you might know, Weld 3 and 4 are running some different class defining strategies for JDK 8 or 11+ resulting in an MR JAR solution.
+                  Since JDK 11 is the basis, this is no longer needed and similar workarounds were removed from code.</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_deprecations_and_removals">Deprecations and removals</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>Here is a list of all changes of this nature within Weld APIs:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Multiple methods from <code>org.jboss.weld.serialization.spi.ProxyServices</code> were removed.</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>If you are an integrator, you probably implemented this interface at some point in time; these methods weren&#8217;t used by Weld anyway, so they are now gone for good.</p>
+                  </li>
+                  <li>
+                  <p>Here is a <a href="https://issues.redhat.com/browse/WELD-2702">link to the issue removing it</a>.</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Any integrators basing their implementations of Jandex likely implemented <code>ClassFileInfo</code>; its <code>isTopLevelClass()</code> has been removed.</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Note that this method was redundant and can be replaced by <code>getClassNestingType()</code>.</p>
+                  </li>
+                  <li>
+                  <p>This was removed as part of the above mentioned issue.</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p><code>WeldInstance.Handler</code> class is now deprecated and so are multiple methods returning this type from <code>WeldInstance</code></p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>The reasons for this removal is that the very same feature was accepted into CDI specification so you can now use CDI API interfaces to achieve the same.</p>
+                  </li>
+                  <li>
+                  <p>For more information, take a look at <a href="https://github.com/eclipse-ee4j/cdi/blob/master/api/src/main/java/jakarta/enterprise/inject/Instance.java#L266-L315"><code>Instance.Handle</code> class from CDI API</a>.</p>
+                  </li>
+                  <li>
+                  <p>And again, a <a href="https://issues.redhat.com/browse/WELD-2685">link to the relevant issue</a>.</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>CDI has had a similar cleanup and some long deprecated API methods were removed; glance at <a href="https://github.com/eclipse-ee4j/cdi/issues/472">this GitHub issue</a> if you want to learn more about that.</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_empty_beans_xml_interpretation">Empty `beans.xml interpretation</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>There is one breaking change in CDI 4.0 that should be mentioned here - change of default interpretation of empty <code>beans.xml</code> descriptor.
+                  Up until CDI 3.0, leaving this file empty meant discovery mode <code>all</code> whereas starting with CDI 4 it now defaults to <code>annotated</code> discovery mode.
+                  As per specification, in <code>all</code> discovery mode, all classes in bean archive are scanned and if fitting, turned into beans.
+                  However, <code>annotated</code> discovery mode only scans classes with <em>bean defining annotations</em>.
+                  Therefore, this change can be breaking for lots of applications using empty <code>beans.xml</code> and relying on CDI to discover classes without annotations.
+                  In order to ease the transition to this new default, CDI 4 specification says the following:</p>
+                  </div>
+                  <div class="quoteblock">
+                  <blockquote>
+                  <div class="paragraph">
+                  <p>For compatibility with CDI versions prior to 4.0, CDI Full products must contain an option that causes an archive with empty beans.xml to be considered an explicit bean archive.</p>
+                  </div>
+                  </blockquote>
+                  </div>
+                  <div class="paragraph">
+                  <p>This option is vendor-dependent and integrators needs to define how to achieve it in their frameworks/platforms.
+                  That being said, Weld has been updated to allow for this.
+                  If you are using Weld tooling to parse <code>beans.xml</code>, chances are, you&#8217;re doing one of these:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Directly invoking parser via <a href="https://github.com/weld/core/blob/5.0.0.Beta1/impl/src/main/java/org/jboss/weld/xml/BeansXmlStreamParser.java"><code>org.jboss.weld.xml.BeansXmlStreamParser</code></a>.</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p><code>BeansXmlStreamParser</code> now has new constructor methods which allow passing <code>BeanDiscoveryMode</code> parameter telling Weld how to interpret empty <code>beans.xml</code>.</p>
+                  </li>
+                  <li>
+                  <p>All former constructors were retained and default to <code>BeanDiscoveryMode.ANNOTATED</code>.</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Indirectly invoking it via an implementation of <code>org.jboss.weld.bootstrap.api.Bootstrap</code> and its <code>parse</code> methods.</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>New variantions of the <code>parse</code> methods were added and accept <code>BeanDiscoveryMode</code> parameter telling Weld how to interpret empty <code>beans.xml</code>.</p>
+                  </li>
+                  <li>
+                  <p>All former variantion of <code>parse</code> methods were retained and default to <code>BeanDiscoveryMode.ANNOTATED</code>.</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>This should give integrators enough leeway to implement the backward compatibility switch.</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_weld_versus_cdi_lite_versus_cdi_full">Weld versus CDI Lite versus CDI Full</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>By far the biggest change in CDI 4.0 is the introduction of CDI Lite.
+                  At this point I should reiterate that I highly recommend looking <a href="https://eclipse-ee4j.github.io/cdi/2021/10/25/way-to-cdi4.html">this article</a> if you don&#8217;t know what CDI Lite is.
+                  In short, CDI Lite is a feature subset of CDI Full that broadens the amount of environments in which CDI can execute; more presicely, it enables CDI in build time oriented frameworks such as Micronaut or Quarkus.
+                  What does that means for Weld users? Nothing much, Weld is and will be a runtime oriented implementation and you can keep using CDI as you did up until now.
+                  More precisely, Weld is so called CDI Full implementation meaning it provides each and every CDI feature and while there were some deprecations and removals, the rest stays the same.</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_build_compatible_extensions">Build Compatible Extensions</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>One of the notable additions to CDI Lite  (and therefore into CDI Full as well) were Build Compatible Extensions (BCE).
+                  These are akin to Portable Extensions but tuned in a way so that they can be used in build time oriented environments as well.
+                  Along with it comes a different language model because <code>AnnotatedType</code> and friends are reflection-heavy and not a good fit for that API.
+                  If you want to learns more, <a href="https://eclipse-ee4j.github.io/cdi/2021/12/03/you-know-build-compatible-extensions.html">here is an excellent article</a> by Ladislav Thon that covers how they work.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>From Weld perspective, you can use BCE as much as you like although they are also executed at runtime, just as Portable Extensions are.
+                  It is still recommended to use Portable Extensions if possible because BCE are (in Weld) implemented via Portable Extensions.
+                  That being said, if you have some portability demands between Lite and Full, you should be able to use BCE as much as you like.</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_integrators_how_to_make_weld_understand_build_compatible_extensions">Integrators - how to make Weld understand Build Compatible Extensions?</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>This part focuses mainly on integrators and describes how Weld implements Build Compatible Extensions and what needs to be done by integrators in order to fully support CDI Lite.</p>
+                  </div>
+                  <div class="sect2">
+                  <h3 id="_weld_lite_extension_translator_module"><code>weld-lite-extension-translator</code> module</h3>
+                  <div class="paragraph">
+                  <p>Weld 5 has a new module that enables Build Compatible Extensions (BCE) and the new language model that goes along with it - <a href="https://github.com/weld/core/tree/5.0.0.Beta1/weld-lite-extension-translator"><code>weld-lite-extension-translator</code></a>.
+                  GAV of this new artifact is <code>org.jboss.weld:weld-lite-extension-translator:5.0.0.Beta1</code>.
+                  As I mentioned in previous point, BCE are executed via a Portable extension.
+                  More precisely, the key class is <a href="https://github.com/weld/core/blob/5.0.0.Beta1/weld-lite-extension-translator/src/main/java/org/jboss/weld/lite/extension/translator/LiteExtensionTranslator.java"><code>WeldLiteExtensionTranslator</code></a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Just like any Portable extension, it needs an entry in <code>META-INF</code> or an instance of this extensions has to be added programmaticaly during Weld bootstrap.
+                  This is where it gets tricky; <strong>it doesn&#8217;t work out of the box in all environments</strong>!</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Weld SE - works out of the box, the extension is automagically added</p>
+                  </li>
+                  <li>
+                  <p>Weld Servlet - works out of the box, the extensions is automagically added</p>
+                  </li>
+                  <li>
+                  <p>EE - <strong>doesn&#8217;t work without integrator registering the extension</strong></p>
+                  </li>
+                  <li>
+                  <p>Any other custom integration - <strong>doesn&#8217;t work without integrator registering the extension</strong></p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>There is of course a reason for it - complex structured deployments (such as EAR or WAR) and the fact that Weld alone cannot know the deployment well enough to make sure this extension wouldn&#8217;t be registered multiple times.
+                  On top of that, you might also want to avoid registering this extension if there are no BCE found inside the deployment which can also be dependent on how the given platform performs such discovery.
+                  Therefore, Weld leaves it up to the integrator (WildFly, GF, Liberty,&#8230;&#8203;) to identify where and when to register this extension for each deployment.</p>
+                  </div>
+                  </div>
+                  <div class="sect2">
+                  <h3 id="_registering_liteextensiontranslator">Registering <code>LiteExtensionTranslator</code></h3>
+                  <div class="paragraph">
+                  <p>Registering the <code>LiteExtensionTranslator</code> can be as easy as adding a <code>META-INF</code> entry with it into some archive in the deployment.
+                  An example of this would be <code>arquillian-container-weld</code>, a test container for Weld applications.
+                  As you can see from <a href="https://github.com/arquillian/arquillian-container-weld/pull/114/files">this pull request</a>, it basically adds a <code>META-INF</code> entry which is sufficient to support new extension model.
+                  Since it a test tool, the extension is always registered without any attempt to optimize it.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>The above solution is nice and clean, but won&#8217;t cut it for any EE integrators.
+                  Instead, you will want to register this extension very similarly to how you currently register <a href="https://github.com/weld/core/blob/5.0.0.Beta1/probe/core/src/main/java/org/jboss/weld/probe/ProbeExtension.java"><code>ProbeExtension</code></a> - add it programmatically as part of the CDI deployment.
+                  As mentioned above, this extension should to be registered at most once per deployment, so I&#8217;d recommend welding (pun intended) this directly into your <code>org.jboss.weld.bootstrap.spi.CDI11Deployment</code> implementation.
+                  Because WildFly does not yet have a public branch with this, I can at least point to how <a href="https://github.com/wildfly/wildfly/blob/main/weld/subsystem/src/main/java/org/jboss/as/weld/deployment/processors/DevelopmentModeProcessor.java#L138-L139">it registers <code>ProbeExtension</code></a>.
+                  With a little bit of digging, it boils down to <a href="https://github.com/wildfly/wildfly/blob/main/weld/subsystem/src/main/java/org/jboss/as/weld/deployment/WeldDeployment.java#L97">creating <code>CDI11Deployment</code> impl</a> with list of extensions already containing this one.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Which brings us to the second point - I&#8217;d recommend integrators to optimize this process and only register/include <code>LiteExtensionTranslator</code> when there is at least one BCE present in any given deployment.
+                  The reason being that this extension has to monitor a very wide range of events including <code>ProcessAnnotatedType&lt;?&gt;</code> for all types in order to properly implement BCE.
+                  Many integrators can perform BCE detection in their own ways (such as Jandex in WildFly) but for those that want a generic solution, take a look at <code>org.jboss.weld.lite.extension.translator.BuildCompatibleExtensionLoader</code> which is a utility class alowing to perform a standard service discovery process with given <code>ClassLoader</code> and returns the set of discovered BCE classes.
+                  You can then instantiate <code>LiteExtensionTranslator</code> via a constructor that takes this set as an input; or skip registering it if you haven&#8217;t found any BCE at all.</p>
+                  </div>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_tck_structural_changes_and_lang_model_tcks">TCK structural changes and lang model TCKs</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>Few paragraphs above I mentioned new language model used by Build Compatible Extensions.
+                  Obviously, this needed some testing and so CDI TCK has a separate module for it; see <a href="https://github.com/eclipse-ee4j/cdi-tck/tree/4.0.0-RC2/lang-model"><code>lang-model</code> module and its README</a>.
+                  Weld tests and passes these TCKs via <a href="https://github.com/weld/core/tree/5.0.0.Beta1/lang-model-tck"><code>lang-model-tck</code> module</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Next change was a separation of tests between pure CDI tests and tests requiring other Jakarta EE technologies such as JSF, EL and other.
+                  Many of these are candidates for move into their respective specifications but are for now still hosted in CDI TCK.
+                  All of these tests now reside under a <a href="https://github.com/eclipse-ee4j/cdi-tck/tree/4.0.0-RC2/web">separate module</a> with GAV <code>jakarta.enterprise:cdi-tck-web-impl</code>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Lastly, due to the split between CDI Lite and Full and the ability to have CDI implementations only for Lite, all TCKs had to be reviewed and a new test category was added - <a href="https://github.com/eclipse-ee4j/cdi-tck/blob/4.0.0-RC2/impl/src/main/java/org/jboss/cdi/tck/TestGroups.java#L37"><code>cdi-full</code></a>.
+                  It is easy to guess that this category was assigned to tests that are supposed to only execute in CDI Full implementations; i.e. tests containing features that aren&#8217;t present in CDI Lite.
+                  Weld, as noted before, is a CDI Full implementation and as such passes all TCKs.
+                  The current setup used for TCK execution can be read from <a href="https://github.com/weld/core/blob/5.0.0.Beta1/jboss-tck-runner/pom.xml">this POM file</a>.</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_more_in_depth_overview_of_resolved_issues_in_weld_5">More in-depth overview of resolved issues in Weld 5</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>Finally, for those who would like to inspect a more detailed list of changes, here are links to release notes of all version 5 releases up to and including Beta1:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p><a href="https://issues.redhat.com/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12358586">Weld 5.0.0.Alpha1 Release Notes</a></p>
+                  </li>
+                  <li>
+                  <p><a href="https://issues.redhat.com/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12378774">Weld 5.0.0.Alpha2 Release Notes</a></p>
+                  </li>
+                  <li>
+                  <p><a href="https://issues.redhat.com/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12378495">Weld 5.0.0.Beta1 Release Notes</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.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=12378495" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </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>
@@ -1009,97 +1318,6 @@ <h2 id="_development_plans">Development Plans</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2020/03/28/weld-314Final/">Weld 3.1.4.Final</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2020-3-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>New Weld version is here, say hello to Weld 3.1.4.Final.
-                  There are only few issues included in this release, so let&#8217;s take a look at them.</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><code>ObserverMethodConfigurator</code> initialized by reading an <code>AnnotatedType</code> previously didn&#8217;t set the method as async when it should (<a href="https://issues.jboss.org/browse/WELD-2609" target="_blank" rel="noopener">WELD-2609</a>)</p>
-                  </li>
-                  <li>
-                  <p>Fixed observability of <code>@Destroyed</code> events for Conversation context when there are multiple WARs deployed (<a href="https://issues.jboss.org/browse/WELD-2610" target="_blank" rel="noopener">WELD-2610</a>)</p>
-                  </li>
-                  <li>
-                  <p>After a failed attempt to restore a conversation, Weld could omit firing <code>@Initialized</code> event; this is now working properly (<a href="https://issues.jboss.org/browse/WELD-2611" target="_blank" rel="noopener">WELD-2611</a>)</p>
-                  </li>
-                  <li>
-                  <p>Cleanup of stored conversations required unnecessarily many locks simultaneously which could lead to deadlock on some servers (<a href="https://issues.jboss.org/browse/WELD-2612" target="_blank" rel="noopener">WELD-2612</a>)</p>
-                  </li>
-                  <li>
-                  <p>Removed <code>Unsafe</code> usage as means of cracking open <code>ClassLoader</code> for proxy definition (<a href="https://issues.jboss.org/browse/WELD-2613" target="_blank" rel="noopener">WELD-2613</a>)</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>This only helped to hide <code>IllegalAccess</code> warning on JDK 11 (which will now show again)</p>
-                  </li>
-                  <li>
-                  <p>Starting with JDK 12 and newer, <code>Unsafe</code> doesn&#8217;t work at all making this solution obsolete</p>
-                  </li>
-                  <li>
-                  <p>We&#8217;ve created (<a href="https://issues.jboss.org/browse/WELD-2619" target="_blank" rel="noopener">WELD-2619</a>) in order to search for better solution that would work across all JDK versions</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Using <code>HttpSessionContext.destroy()</code> could sometimes not destroy the instance if it wasn&#8217;t used in current request (<a href="https://issues.jboss.org/browse/WELD-2615" target="_blank" rel="noopener">WELD-2615</a>)</p>
-                  </li>
-                  <li>
-                  <p>Fix OSGi versions for EE dependencies (<a href="https://issues.jboss.org/browse/WELD-2616" target="_blank" rel="noopener">WELD-2616</a>)</p>
-                  </li>
-                  <li>
-                  <p>Properly close stream after reading <code>weld.properties</code> (<a href="https://issues.jboss.org/browse/WELD-2606" target="_blank" rel="noopener">WELD-2606</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.4.Final/wildfly-19.0.0.Final-weld-3.1.4.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly 19.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.1.4.Final/en-US/html/" target="_blank" rel="noopener">Documentation</a> &#93;
-                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12343306" 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 af5215d6..8c98e460 100644
--- a/news/tags/release/page/4.html
+++ b/news/tags/release/page/4.html
@@ -141,6 +141,97 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2020/03/28/weld-314Final/">Weld 3.1.4.Final</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2020-3-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>New Weld version is here, say hello to Weld 3.1.4.Final.
+                  There are only few issues included in this release, so let&#8217;s take a look at them.</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><code>ObserverMethodConfigurator</code> initialized by reading an <code>AnnotatedType</code> previously didn&#8217;t set the method as async when it should (<a href="https://issues.jboss.org/browse/WELD-2609" target="_blank" rel="noopener">WELD-2609</a>)</p>
+                  </li>
+                  <li>
+                  <p>Fixed observability of <code>@Destroyed</code> events for Conversation context when there are multiple WARs deployed (<a href="https://issues.jboss.org/browse/WELD-2610" target="_blank" rel="noopener">WELD-2610</a>)</p>
+                  </li>
+                  <li>
+                  <p>After a failed attempt to restore a conversation, Weld could omit firing <code>@Initialized</code> event; this is now working properly (<a href="https://issues.jboss.org/browse/WELD-2611" target="_blank" rel="noopener">WELD-2611</a>)</p>
+                  </li>
+                  <li>
+                  <p>Cleanup of stored conversations required unnecessarily many locks simultaneously which could lead to deadlock on some servers (<a href="https://issues.jboss.org/browse/WELD-2612" target="_blank" rel="noopener">WELD-2612</a>)</p>
+                  </li>
+                  <li>
+                  <p>Removed <code>Unsafe</code> usage as means of cracking open <code>ClassLoader</code> for proxy definition (<a href="https://issues.jboss.org/browse/WELD-2613" target="_blank" rel="noopener">WELD-2613</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>This only helped to hide <code>IllegalAccess</code> warning on JDK 11 (which will now show again)</p>
+                  </li>
+                  <li>
+                  <p>Starting with JDK 12 and newer, <code>Unsafe</code> doesn&#8217;t work at all making this solution obsolete</p>
+                  </li>
+                  <li>
+                  <p>We&#8217;ve created (<a href="https://issues.jboss.org/browse/WELD-2619" target="_blank" rel="noopener">WELD-2619</a>) in order to search for better solution that would work across all JDK versions</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Using <code>HttpSessionContext.destroy()</code> could sometimes not destroy the instance if it wasn&#8217;t used in current request (<a href="https://issues.jboss.org/browse/WELD-2615" target="_blank" rel="noopener">WELD-2615</a>)</p>
+                  </li>
+                  <li>
+                  <p>Fix OSGi versions for EE dependencies (<a href="https://issues.jboss.org/browse/WELD-2616" target="_blank" rel="noopener">WELD-2616</a>)</p>
+                  </li>
+                  <li>
+                  <p>Properly close stream after reading <code>weld.properties</code> (<a href="https://issues.jboss.org/browse/WELD-2606" target="_blank" rel="noopener">WELD-2606</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.4.Final/wildfly-19.0.0.Final-weld-3.1.4.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly 19.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.1.4.Final/en-US/html/" target="_blank" rel="noopener">Documentation</a> &#93;
+                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12343306" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2019/11/28/weld-313Final/">Weld 3.1.3.Final</a>
@@ -1408,136 +1499,6 @@ <h2 id="_wildfly_patch">WildFly Patch</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2017/12/18/weld-246Final/">Weld 2.4.6.Final</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2017-12-18
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/release">release</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Matej Novotny
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>Time has come for another round of Weld 2.4 bugfix release.
-                  But that&#8217;s not all - this time there is also new API to go along with this release - Weld API 2.4.SP2.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Among other things you can now obtain interceptor binding from <code>javax.interceptor.InvocationContext</code>, use enriched version of <code>javax.enterprise.event.Event</code> or select <code>javax.enterprise.inject.Instance</code> based on <code>java.lang.reflect.Type</code>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Notable fixes and improvements:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Weld Core:</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Improved subclass generation mechanism for generic interceptors (<a href="https://issues.jboss.org/browse/WELD-2414" target="_blank" rel="noopener">WELD-2414</a>)</p>
-                  </li>
-                  <li>
-                  <p>Corrected proxy creation for signed classes (<a href="https://issues.jboss.org/browse/WELD-2425" target="_blank" rel="noopener">WELD-2425</a>)</p>
-                  </li>
-                  <li>
-                  <p>Correct <code>InjectionPoint</code> bean behaviour when used within <code>AfterBeanDiscovery</code> observer (<a href="https://issues.jboss.org/browse/WELD-2429" target="_blank" rel="noopener">WELD-2429</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Weld SE</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>There are now multiple convenient error-proof methods to quickly configure SE container (<a href="https://issues.jboss.org/browse/WELD-2426" target="_blank" rel="noopener">WELD-2426</a>)</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p><code>Weld.enableDevMode()</code>, <code>Weld.scanClasspathEntries()</code>, &#8230;&#8203;</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Weld API/SPI</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p><code>WeldInstance</code> has several improvements</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>It now allows you to <code>select()</code> beans based on <code>java.lang.reflect.Type</code> (<a href="https://issues.jboss.org/browse/WELD-2427" target="_blank" rel="noopener">WELD-2427</a>)</p>
-                  </li>
-                  <li>
-                  <p><code>WeldInstance.Handler</code> had become lazy which means you can now iterate/filter/sort <code>WeldInstance</code> without actually instantiating beans (<a href="https://issues.jboss.org/browse/WELD-2258" target="_blank" rel="noopener">WELD-2258</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>There is new interface in the API - <code>WeldEvent</code> - which can be used in place of well known <code>Event</code> but allows you narrow down event type by using <code>select()</code> with <code>java.lang.reflect.Type</code> (<a href="https://issues.jboss.org/browse/WELD-2427" target="_blank" rel="noopener">WELD-2427</a>)</p>
-                  </li>
-                  <li>
-                  <p>API now contains <code>WeldInvocationContext</code>, an enriched version of <code>javax.interceptor.InvocationContext</code> which allows to obtain interceptor binding (<a href="https://issues.jboss.org/browse/WELD-2433" target="_blank" rel="noopener">WELD-2433</a>)</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>There is also a <code>String</code> key used to obtain interceptors binding directly from <code>InvocationContext</code> (<a href="https://issues.jboss.org/browse/WELD-2436" target="_blank" rel="noopener">WELD-2436</a>)</p>
-                  </li>
-                  <li>
-                  <p>In order to learn more, please refer to (<a href="http://docs.jboss.org/weld/reference/latest/en-US/html_single/#_enhanced_version_of_literal_javax_interceptor_invocationcontext_literal" target="_blank" rel="noopener">our documentation</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Other</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Probe - fixed NPE which might occur when bean had <code>@Priority</code> but no other annotation (<a href="https://issues.jboss.org/browse/WELD-2432" target="_blank" rel="noopener">WELD-2432</a>)</p>
-                  </li>
-                  <li>
-                  <p>All the API changes should now be documented within Weld docs</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_wildfly_patch">WildFly Patch</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>As usual, a <a href="http://download.jboss.org/weld/2.4.6.Final/wildfly-11.0.0.Final-weld-2.4.6.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly 11.0.0.Final</a> is available.
-                  If you’re not familiar with patching WildFly, check the <a href="/documentation/#12">FAQ</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>&#91; <a href="/download/">Download</a> &#93;
-                  &#91; <a href="http://docs.jboss.org/weld/reference/2.4.6.Final/en-US/html/" target="_blank" rel="noopener">Documentation</a> &#93;
-                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?version=12334958&amp;styleName=Html&amp;projectId=12310891" target="_blank" rel="noopener">Release notes</a> &#93;</p>
-                  </div>
-                  </div>
-                  </div>
-                </div>
-                <hr>
-              </div>
               <div class="pagination-links"><a href="/news/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 405dcb82..28efbcbe 100644
--- a/news/tags/release/page/5.html
+++ b/news/tags/release/page/5.html
@@ -141,6 +141,136 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2017/12/18/weld-246Final/">Weld 2.4.6.Final</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2017-12-18
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/release">release</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Matej Novotny
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>Time has come for another round of Weld 2.4 bugfix release.
+                  But that&#8217;s not all - this time there is also new API to go along with this release - Weld API 2.4.SP2.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Among other things you can now obtain interceptor binding from <code>javax.interceptor.InvocationContext</code>, use enriched version of <code>javax.enterprise.event.Event</code> or select <code>javax.enterprise.inject.Instance</code> based on <code>java.lang.reflect.Type</code>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Notable fixes and improvements:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Weld Core:</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Improved subclass generation mechanism for generic interceptors (<a href="https://issues.jboss.org/browse/WELD-2414" target="_blank" rel="noopener">WELD-2414</a>)</p>
+                  </li>
+                  <li>
+                  <p>Corrected proxy creation for signed classes (<a href="https://issues.jboss.org/browse/WELD-2425" target="_blank" rel="noopener">WELD-2425</a>)</p>
+                  </li>
+                  <li>
+                  <p>Correct <code>InjectionPoint</code> bean behaviour when used within <code>AfterBeanDiscovery</code> observer (<a href="https://issues.jboss.org/browse/WELD-2429" target="_blank" rel="noopener">WELD-2429</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Weld SE</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>There are now multiple convenient error-proof methods to quickly configure SE container (<a href="https://issues.jboss.org/browse/WELD-2426" target="_blank" rel="noopener">WELD-2426</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p><code>Weld.enableDevMode()</code>, <code>Weld.scanClasspathEntries()</code>, &#8230;&#8203;</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Weld API/SPI</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p><code>WeldInstance</code> has several improvements</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>It now allows you to <code>select()</code> beans based on <code>java.lang.reflect.Type</code> (<a href="https://issues.jboss.org/browse/WELD-2427" target="_blank" rel="noopener">WELD-2427</a>)</p>
+                  </li>
+                  <li>
+                  <p><code>WeldInstance.Handler</code> had become lazy which means you can now iterate/filter/sort <code>WeldInstance</code> without actually instantiating beans (<a href="https://issues.jboss.org/browse/WELD-2258" target="_blank" rel="noopener">WELD-2258</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>There is new interface in the API - <code>WeldEvent</code> - which can be used in place of well known <code>Event</code> but allows you narrow down event type by using <code>select()</code> with <code>java.lang.reflect.Type</code> (<a href="https://issues.jboss.org/browse/WELD-2427" target="_blank" rel="noopener">WELD-2427</a>)</p>
+                  </li>
+                  <li>
+                  <p>API now contains <code>WeldInvocationContext</code>, an enriched version of <code>javax.interceptor.InvocationContext</code> which allows to obtain interceptor binding (<a href="https://issues.jboss.org/browse/WELD-2433" target="_blank" rel="noopener">WELD-2433</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>There is also a <code>String</code> key used to obtain interceptors binding directly from <code>InvocationContext</code> (<a href="https://issues.jboss.org/browse/WELD-2436" target="_blank" rel="noopener">WELD-2436</a>)</p>
+                  </li>
+                  <li>
+                  <p>In order to learn more, please refer to (<a href="http://docs.jboss.org/weld/reference/latest/en-US/html_single/#_enhanced_version_of_literal_javax_interceptor_invocationcontext_literal" target="_blank" rel="noopener">our documentation</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Other</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Probe - fixed NPE which might occur when bean had <code>@Priority</code> but no other annotation (<a href="https://issues.jboss.org/browse/WELD-2432" target="_blank" rel="noopener">WELD-2432</a>)</p>
+                  </li>
+                  <li>
+                  <p>All the API changes should now be documented within Weld docs</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_wildfly_patch">WildFly Patch</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>As usual, a <a href="http://download.jboss.org/weld/2.4.6.Final/wildfly-11.0.0.Final-weld-2.4.6.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly 11.0.0.Final</a> is available.
+                  If you’re not familiar with patching WildFly, check the <a href="/documentation/#12">FAQ</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="/download/">Download</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/2.4.6.Final/en-US/html/" target="_blank" rel="noopener">Documentation</a> &#93;
+                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?version=12334958&amp;styleName=Html&amp;projectId=12310891" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2017/11/23/weld-302Final/">Weld 3.0.2.Final</a>
@@ -1112,93 +1242,6 @@ <h2 id="_wildfly_patch">WildFly Patch</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2016/12/19/weld-300Beta1/">Weld 3.0.0.Beta1</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2016-12-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 class="paragraph">
-                  <p>I am very pleased to announce the first <strong>Beta</strong> version of Weld <strong>3.0.0</strong> (CDI 2.0).
-                  See also <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12331387" target="_blank" rel="noopener">the release details</a>.
-                  Thanks to everyone involved in this release!</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>This is an important milestone.
-                  CDI 2.0 is now considered "feature complete" and so the next Weld 3 versions should be mostly dedicated to cleanup and optimization.
-                  The next version will be Weld <strong>3.0.0.CR1</strong> (ETA in mid January).
-                  Finally, we would like to release Weld <strong>3.0.0.Final</strong> in early February.</p>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_new_and_noteworthy">New and noteworthy</h2>
-                  <div class="sectionbody">
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p><code>javax.enterprise.inject.spi.InterceptionFactory</code> implementation (<a href="https://issues.jboss.org/browse/WELD-2257" target="_blank" rel="noopener">WELD-2257</a>)</p>
-                  </li>
-                  <li>
-                  <p><code>ProcessSyntheticObserverMethod</code> container lifecycle event (<a href="https://issues.jboss.org/browse/WELD-2279" target="_blank" rel="noopener">WELD-2279</a>)</p>
-                  </li>
-                  <li>
-                  <p><code>BeforeDestroyed</code> event fired before a context is actually destroyed (<a href="https://issues.jboss.org/browse/WELD-2269" target="_blank" rel="noopener">WELD-2269</a>)</p>
-                  </li>
-                  <li>
-                  <p>"trimmed" bean archives (<a href="https://issues.jboss.org/browse/WELD-2268" target="_blank" rel="noopener">WELD-2268</a>)</p>
-                  </li>
-                  <li>
-                  <p>context control - <code>ActivateRequestContext</code> interceptor binding (<a href="https://issues.jboss.org/browse/WELD-2267" target="_blank" rel="noopener">WELD-2267</a>) and <code>RequestContextController</code> built-in bean (<a href="https://issues.jboss.org/browse/WELD-2266" target="_blank" rel="noopener">WELD-2266</a>)</p>
-                  </li>
-                  <li>
-                  <p><code>ProcessSyntheticBean</code> container lifecycle event (<a href="https://issues.jboss.org/browse/WELD-2265" target="_blank" rel="noopener">WELD-2265</a>)</p>
-                  </li>
-                  <li>
-                  <p>few proposals did not make it into CDI 2.0 and so we enhanced the Weld API:</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p><code>org.jboss.weld.inject.WeldInstance</code> (already part of Weld 2.4 API)</p>
-                  </li>
-                  <li>
-                  <p><code>org.jboss.weld.interceptor.WeldInvocationContext</code> allows to obtain a set of interceptor bindings for a lifecycle callback, business method, timeout method, or constructor (see also <a href="https://issues.jboss.org/browse/CDI-468" target="_blank" rel="noopener">CDI-468</a>)</p>
-                  </li>
-                  <li>
-                  <p><code>org.jboss.weld.bootstrap.event.WeldAfterBeanDiscovery</code> allows to obtain an <code>InterceptorConfigurator</code> to configure a new <code>Interceptor</code> bean</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  </ul>
-                  </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.Beta1/wildfly-10.1.0.Final-weld-3.0.0.Beta1-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="/download/">Download</a> &#93;
-                  &#91; <a href="http://docs.jboss.org/weld/reference/3.0.0.Beta1/en-US/html/" target="_blank" rel="noopener">Documentation</a> &#93;
-                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12331387" 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 b8da3646..941dedaa 100644
--- a/news/tags/release/page/6.html
+++ b/news/tags/release/page/6.html
@@ -141,6 +141,93 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2016/12/19/weld-300Beta1/">Weld 3.0.0.Beta1</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2016-12-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 class="paragraph">
+                  <p>I am very pleased to announce the first <strong>Beta</strong> version of Weld <strong>3.0.0</strong> (CDI 2.0).
+                  See also <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12331387" target="_blank" rel="noopener">the release details</a>.
+                  Thanks to everyone involved in this release!</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>This is an important milestone.
+                  CDI 2.0 is now considered "feature complete" and so the next Weld 3 versions should be mostly dedicated to cleanup and optimization.
+                  The next version will be Weld <strong>3.0.0.CR1</strong> (ETA in mid January).
+                  Finally, we would like to release Weld <strong>3.0.0.Final</strong> in early February.</p>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_new_and_noteworthy">New and noteworthy</h2>
+                  <div class="sectionbody">
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p><code>javax.enterprise.inject.spi.InterceptionFactory</code> implementation (<a href="https://issues.jboss.org/browse/WELD-2257" target="_blank" rel="noopener">WELD-2257</a>)</p>
+                  </li>
+                  <li>
+                  <p><code>ProcessSyntheticObserverMethod</code> container lifecycle event (<a href="https://issues.jboss.org/browse/WELD-2279" target="_blank" rel="noopener">WELD-2279</a>)</p>
+                  </li>
+                  <li>
+                  <p><code>BeforeDestroyed</code> event fired before a context is actually destroyed (<a href="https://issues.jboss.org/browse/WELD-2269" target="_blank" rel="noopener">WELD-2269</a>)</p>
+                  </li>
+                  <li>
+                  <p>"trimmed" bean archives (<a href="https://issues.jboss.org/browse/WELD-2268" target="_blank" rel="noopener">WELD-2268</a>)</p>
+                  </li>
+                  <li>
+                  <p>context control - <code>ActivateRequestContext</code> interceptor binding (<a href="https://issues.jboss.org/browse/WELD-2267" target="_blank" rel="noopener">WELD-2267</a>) and <code>RequestContextController</code> built-in bean (<a href="https://issues.jboss.org/browse/WELD-2266" target="_blank" rel="noopener">WELD-2266</a>)</p>
+                  </li>
+                  <li>
+                  <p><code>ProcessSyntheticBean</code> container lifecycle event (<a href="https://issues.jboss.org/browse/WELD-2265" target="_blank" rel="noopener">WELD-2265</a>)</p>
+                  </li>
+                  <li>
+                  <p>few proposals did not make it into CDI 2.0 and so we enhanced the Weld API:</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p><code>org.jboss.weld.inject.WeldInstance</code> (already part of Weld 2.4 API)</p>
+                  </li>
+                  <li>
+                  <p><code>org.jboss.weld.interceptor.WeldInvocationContext</code> allows to obtain a set of interceptor bindings for a lifecycle callback, business method, timeout method, or constructor (see also <a href="https://issues.jboss.org/browse/CDI-468" target="_blank" rel="noopener">CDI-468</a>)</p>
+                  </li>
+                  <li>
+                  <p><code>org.jboss.weld.bootstrap.event.WeldAfterBeanDiscovery</code> allows to obtain an <code>InterceptorConfigurator</code> to configure a new <code>Interceptor</code> bean</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  </ul>
+                  </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.Beta1/wildfly-10.1.0.Final-weld-3.0.0.Beta1-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="/download/">Download</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/3.0.0.Beta1/en-US/html/" target="_blank" rel="noopener">Documentation</a> &#93;
+                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12331387" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2016/11/18/weld-241Final/">Weld 2.4.1.Final</a>
@@ -1064,48 +1151,6 @@ <h2 id="_notable_bug_fixes_and_enhancements">Notable bug-fixes and enhancements<
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2015/12/04/weld-300Alpha14/">Weld 3.0.0.Alpha14</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2015-12-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.Alpha14 the penultimate Weld version for this year has been released into the wild.
-                  It reflects some of the most recent changes in the CDI 2.0 specification, mostly related to asynchronous events.
-                  Moreover, this release also contains quite a lot of enhancements and bugfixes. See also <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12327856">the release details</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.Alpha14/wildfly-10.0.0.CR4-weld-3.0.0.Alpha14-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.CR4</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=12327856">Release notes</a> &#93;
-                  &#91; <a href="http://download.jboss.org/weld/3.0.0.Alpha14/weld-3.0.0.Alpha14.zip">Distribution</a> &#93;
-                  &#91; <a href="http://download.jboss.org/weld/3.0.0.Alpha14/wildfly-10.0.0.CR4-weld-3.0.0.Alpha14-patch.zip">Patch for Wildfly 10 CR4</a>
-                  &#93;</p>
-                  </div>
-                  </div>
-                  </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 d094e401..b69cac6b 100644
--- a/news/tags/release/page/7.html
+++ b/news/tags/release/page/7.html
@@ -141,6 +141,48 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2015/12/04/weld-300Alpha14/">Weld 3.0.0.Alpha14</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2015-12-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.Alpha14 the penultimate Weld version for this year has been released into the wild.
+                  It reflects some of the most recent changes in the CDI 2.0 specification, mostly related to asynchronous events.
+                  Moreover, this release also contains quite a lot of enhancements and bugfixes. See also <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12327856">the release details</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.Alpha14/wildfly-10.0.0.CR4-weld-3.0.0.Alpha14-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.CR4</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=12327856">Release notes</a> &#93;
+                  &#91; <a href="http://download.jboss.org/weld/3.0.0.Alpha14/weld-3.0.0.Alpha14.zip">Distribution</a> &#93;
+                  &#91; <a href="http://download.jboss.org/weld/3.0.0.Alpha14/wildfly-10.0.0.CR4-weld-3.0.0.Alpha14-patch.zip">Patch for Wildfly 10 CR4</a>
+                  &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2015/10/27/weld-231Final/">Weld 2.3.1.Final arrives...</a>
diff --git a/sitemap.xml b/sitemap.xml
index 6386dbc0..2248942c 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -606,6 +606,12 @@
     <priority>1</priority>
     <changefreq>weekly</changefreq>
   </url>
+  <url>
+    <loc>https://weld.cdi-spec.org/news/2024/12/16/weld-600Final/</loc>
+    <lastmod>2024-12-16</lastmod>
+    <priority>1</priority>
+    <changefreq>weekly</changefreq>
+  </url>
   <url>
     <loc>https://weld.cdi-spec.org/news/</loc>
     <lastmod>2024-12-16</lastmod>