From 162c1afc0fed41f60b232d6c21e73e91dee2c31d Mon Sep 17 00:00:00 2001
From: Matej Novotny <manovotn@redhat.com>
Date: Tue, 27 Aug 2024 14:29:21 +0000
Subject: [PATCH] Published master to GitHub pages.

---
 dist/index.html                          |  23 ++
 download/index.html                      |  48 +--
 index.html                               |  30 +-
 news.atom                                | 253 +++++++++------
 news/2024/08/27/weld-513Final/index.html | 268 ++++++++++++++++
 news/index.html                          | 113 +++++--
 news/page/10.html                        | 192 ++++++++---
 news/page/11.html                        | 242 +++-----------
 news/page/12.html                        | 251 ++++++++++++---
 news/page/13.html                        | 134 +++-----
 news/page/14.html                        | 129 +++++---
 news/page/15.html                        |  84 ++---
 news/page/16.html                        | 326 +++----------------
 news/page/17.html                        | 332 ++++++++++++++++---
 news/page/18.html                        |  70 ++--
 news/page/19.html                        |  27 ++
 news/page/2.html                         |  71 ++---
 news/page/3.html                         | 108 +++----
 news/page/4.html                         | 171 +++++-----
 news/page/5.html                         | 229 ++++++--------
 news/page/6.html                         | 372 ++++++++--------------
 news/page/7.html                         | 387 ++++++++++++++---------
 news/page/8.html                         | 240 ++++++++------
 news/page/9.html                         | 244 ++++++--------
 news/tags/release/index.html             | 114 ++++---
 news/tags/release/page/2.html            | 135 +++-----
 news/tags/release/page/3.html            | 341 ++++++--------------
 news/tags/release/page/4.html            | 360 ++++++++++++++-------
 news/tags/release/page/5.html            | 235 +++++++-------
 news/tags/release/page/6.html            | 271 +++++++---------
 news/tags/release/page/7.html            | 154 +++++++++
 sitemap.xml                              |  20 +-
 32 files changed, 3238 insertions(+), 2736 deletions(-)
 create mode 100644 news/2024/08/27/weld-513Final/index.html

diff --git a/dist/index.html b/dist/index.html
index 43987736..dd2eb5a2 100644
--- a/dist/index.html
+++ b/dist/index.html
@@ -157,6 +157,29 @@ <h1>Download - binary distribution archive</h1>
                     Download
                   </th>
                 </tr>
+                <tr>
+                  <td class="version">
+                    5.1.3.Final
+                  </td>
+                  <td>
+                    Final
+                  </td>
+                  <td>
+                  </td>
+                  <td>
+                    27.08.2024
+                  </td>
+                  <td>
+                    <a href="https://issues.redhat.com/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12414627">
+                      Changelog
+                    </a>
+                  </td>
+                  <td>
+                    <a href="http://download.jboss.org/weld/5.1.3.Final">
+                      Download
+                    </a>
+                  </td>
+                </tr>
                 <tr>
                   <td class="version">
                     6.0.0.Beta4
diff --git a/download/index.html b/download/index.html
index a8f4f187..2056c52b 100644
--- a/download/index.html
+++ b/download/index.html
@@ -207,6 +207,30 @@ <h2>Binary distribution</h2>
                     Download
                   </th>
                 </tr>
+                <tr>
+                  <td class="version">
+                    5.1.3.Final
+                  </td>
+                  <td>
+                    Final
+                  </td>
+                  <td>
+                    4.0
+                  </td>
+                  <td>
+                    27.08.2024
+                  </td>
+                  <td>
+                    <a href="https://issues.redhat.com/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12414627">
+                      Changelog
+                    </a>
+                  </td>
+                  <td>
+                    <a href="https://download.jboss.org/weld/5.1.3.Final">
+                      Download
+                    </a>
+                  </td>
+                </tr>
                 <tr>
                   <td class="version">
                     6.0.0.Beta4
@@ -429,30 +453,6 @@ <h2>Binary distribution</h2>
                     </a>
                   </td>
                 </tr>
-                <tr>
-                  <td class="version">
-                    5.0.0.SP2
-                  </td>
-                  <td>
-                    Final
-                  </td>
-                  <td>
-                    4.0
-                  </td>
-                  <td>
-                    08.06.2022
-                  </td>
-                  <td>
-                    <a href="https://issues.redhat.com/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12390013">
-                      Changelog
-                    </a>
-                  </td>
-                  <td>
-                    <a href="https://download.jboss.org/weld/5.0.0.SP2">
-                      Download
-                    </a>
-                  </td>
-                </tr>
               </table>
               <p></p>
               <a href="/dist">
diff --git a/index.html b/index.html
index 22ad10d5..ee6f0603 100644
--- a/index.html
+++ b/index.html
@@ -549,10 +549,10 @@ <h2>
                     <ul class="newsColumn">
                       <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>
@@ -560,16 +560,16 @@ <h3>
                           </span>
                         </div>
                         <p>
-                          Weld 6.0.0.Beta4 is now available
+                          Squashing bugs with Weld 5.1.3.Final!
                         </p>
                         <hr>
                       </li>
                       <li>
                         <h3>
-                          <a href="/news/2024/02/26/weld-600Beta1/">Weld 6.0.0.Beta1</a>
+                          <a href="/news/2024/07/03/weld-600Beta4/">Weld 6.0.0.Beta4</a>
                         </h3>
                         <div class="news-date news-boxed">
-                          2024-2-26
+                          2024-7-3
                           &nbsp;
                           <span class="tags">
                             <i class="fa fa-tags"></i>
@@ -577,16 +577,16 @@ <h3>
                           </span>
                         </div>
                         <p>
-                          Weld 6.0.0.Beta1 is now available
+                          Weld 6.0.0.Beta4 is now available
                         </p>
                         <hr>
                       </li>
                       <li>
                         <h3>
-                          <a href="/news/2023/10/26/weld-600Alpha1/">Weld 6.0.0.Alpha1</a>
+                          <a href="/news/2024/02/26/weld-600Beta1/">Weld 6.0.0.Beta1</a>
                         </h3>
                         <div class="news-date news-boxed">
-                          2023-10-26
+                          2024-2-26
                           &nbsp;
                           <span class="tags">
                             <i class="fa fa-tags"></i>
@@ -594,16 +594,16 @@ <h3>
                           </span>
                         </div>
                         <p>
-                          Weld 6.0.0.Alpha1 is now available
+                          Weld 6.0.0.Beta1 is now available
                         </p>
                         <hr>
                       </li>
                       <li>
                         <h3>
-                          <a href="/news/2023/10/05/weld-512Final/">Weld 5.1.2.Final</a>
+                          <a href="/news/2023/10/26/weld-600Alpha1/">Weld 6.0.0.Alpha1</a>
                         </h3>
                         <div class="news-date news-boxed">
-                          2023-10-5
+                          2023-10-26
                           &nbsp;
                           <span class="tags">
                             <i class="fa fa-tags"></i>
@@ -611,16 +611,16 @@ <h3>
                           </span>
                         </div>
                         <p>
-                          Weld 5.1.2.Final is now available
+                          Weld 6.0.0.Alpha1 is now available
                         </p>
                         <hr>
                       </li>
                       <li>
                         <h3>
-                          <a href="/news/2023/08/09/weld-511SP2/">Weld 5.1.1.SP2</a>
+                          <a href="/news/2023/10/05/weld-512Final/">Weld 5.1.2.Final</a>
                         </h3>
                         <div class="news-date news-boxed">
-                          2023-8-9
+                          2023-10-5
                           &nbsp;
                           <span class="tags">
                             <i class="fa fa-tags"></i>
@@ -628,7 +628,7 @@ <h3>
                           </span>
                         </div>
                         <p>
-                          Weld 5.1.1.SP2 available
+                          Weld 5.1.2.Final is now available
                         </p>
                         <hr>
                       </li>
diff --git a/news.atom b/news.atom
index a8b79a95..85a14e33 100644
--- a/news.atom
+++ b/news.atom
@@ -2,13 +2,114 @@
 <feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
   <id>https://weld.cdi-spec.org/</id>
   <title>Weld</title>
-  <updated>2024-07-03T12:41:45+00:00</updated>
+  <updated>2024-08-27T14:27:45+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/08/27/weld-513Final/</id>
+    <title>Weld 5.1.3.Final</title>
+    <updated>2024-08-27T14:27:45+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>
+      <name>Matej Novotny</name>
+    </author>
+    <category term="release"></category>
+    <summary>
+      A new version of Weld 5.1 has landed in Maven Central.
+      
+      
+      This is a bug squashing round which backports several notable fixes and changes from Weld 6 into Weld 5:
+      
+      
+      
+      
+      Change BeanManager resolution process for BuildCompatibleExtension not belonging to any bean archive (WELD-2794)
+      
+      
+      LazySessionBeanStore no longer swallows exceptions happening when attempting to initiate HTTP session (WELD-2762)
+      
+      
+      Correct how we determine proxy package for beans with unassignable types in their bean type set (WELD-2763)
+      
+      
+      
+      This was only problematic in environments using WeldDefaultProxyServices to define their proxies (such as Weld SE)
+      
+      
+      
+      
+      
+      Correct CommonLogger to mention correct GAV for Jandex (WELD-2770)
+      
+      
+      Added the ability to register Build Compatible Extension in...
+    </summary>
+    <content type="html">
+      &lt;div class=&quot;paragraph&quot;&gt;
+      &lt;p&gt;A new version of Weld 5.1 has landed in Maven Central.&lt;/p&gt;
+      &lt;/div&gt;
+      &lt;div class=&quot;paragraph&quot;&gt;
+      &lt;p&gt;This is a bug squashing round which backports several notable fixes and changes from Weld 6 into Weld 5:&lt;/p&gt;
+      &lt;/div&gt;
+      &lt;div class=&quot;ulist&quot;&gt;
+      &lt;ul&gt;
+      &lt;li&gt;
+      &lt;p&gt;Change &lt;code&gt;BeanManager&lt;/code&gt; resolution process for &lt;code&gt;BuildCompatibleExtension&lt;/code&gt; not belonging to any bean archive (&lt;a href=&quot;https://issues.redhat.com/browse/WELD-2794&quot;&gt;WELD-2794&lt;/a&gt;)&lt;/p&gt;
+      &lt;/li&gt;
+      &lt;li&gt;
+      &lt;p&gt;&lt;code&gt;LazySessionBeanStore&lt;/code&gt; no longer swallows exceptions happening when attempting to initiate HTTP session (&lt;a href=&quot;https://issues.redhat.com/browse/WELD-2762&quot;&gt;WELD-2762&lt;/a&gt;)&lt;/p&gt;
+      &lt;/li&gt;
+      &lt;li&gt;
+      &lt;p&gt;Correct how we determine proxy package for beans with unassignable types in their bean type set (&lt;a href=&quot;https://issues.redhat.com/browse/WELD-2763&quot;&gt;WELD-2763&lt;/a&gt;)&lt;/p&gt;
+      &lt;div class=&quot;ulist&quot;&gt;
+      &lt;ul&gt;
+      &lt;li&gt;
+      &lt;p&gt;This was only problematic in environments using WeldDefaultProxyServices to define their proxies (such as Weld SE)&lt;/p&gt;
+      &lt;/li&gt;
+      &lt;/ul&gt;
+      &lt;/div&gt;
+      &lt;/li&gt;
+      &lt;li&gt;
+      &lt;p&gt;Correct &lt;code&gt;CommonLogger&lt;/code&gt; to mention correct GAV for Jandex (&lt;a href=&quot;https://issues.redhat.com/browse/WELD-2770&quot;&gt;WELD-2770&lt;/a&gt;)&lt;/p&gt;
+      &lt;/li&gt;
+      &lt;li&gt;
+      &lt;p&gt;Added the ability to register Build Compatible Extension in Weld SE without discovery (&lt;a href=&quot;https://issues.redhat.com/browse/WELD-2772&quot;&gt;WELD-2772&lt;/a&gt;)&lt;/p&gt;
+      &lt;/li&gt;
+      &lt;li&gt;
+      &lt;p&gt;Correct inheritance of producer fields if there is an extension present (&lt;a href=&quot;https://issues.redhat.com/browse/WELD-2773&quot;&gt;WELD-2773&lt;/a&gt;)&lt;/p&gt;
+      &lt;/li&gt;
+      &lt;li&gt;
+      &lt;p&gt;Make sure &lt;code&gt;@Default&lt;/code&gt; qualifier is added to events fired via &lt;code&gt;BeanManager#getEvent()&lt;/code&gt; where appropriate (&lt;a href=&quot;https://issues.redhat.com/browse/WELD-2775&quot;&gt;WELD-2775&lt;/a&gt;)&lt;/p&gt;
+      &lt;/li&gt;
+      &lt;li&gt;
+      &lt;p&gt;Observer method confiurator now correctly allows to override &lt;code&gt;Reception&lt;/code&gt; settings without changing its &lt;code&gt;notify()&lt;/code&gt; method (&lt;a href=&quot;https://issues.redhat.com/browse/WELD-2786&quot;&gt;WELD-2786&lt;/a&gt;)&lt;/p&gt;
+      &lt;/li&gt;
+      &lt;li&gt;
+      &lt;p&gt;Clean up legacy Jetty integration parts (&lt;a href=&quot;https://issues.redhat.com/browse/WELD-2787&quot;&gt;WELD-2787&lt;/a&gt;)&lt;/p&gt;
+      &lt;/li&gt;
+      &lt;li&gt;
+      &lt;p&gt;Use &lt;code&gt;Lock&lt;/code&gt; instead of &lt;code&gt;synchronized&lt;/code&gt; within &lt;code&gt;ContextualInstanceStrategy&lt;/code&gt; to be more virtual thread-friendly (&lt;a href=&quot;https://issues.redhat.com/browse/WELD-2788&quot;&gt;WELD-2788&lt;/a&gt;)&lt;/p&gt;
+      &lt;/li&gt;
+      &lt;li&gt;
+      &lt;p&gt;Skip superclass declarations of final methods when creating proxies (&lt;a href=&quot;https://issues.redhat.com/browse/WELD-2785&quot;&gt;WELD-2785&lt;/a&gt;)&lt;/p&gt;
+      &lt;/li&gt;
+      &lt;li&gt;
+      &lt;p&gt;Ensure OSGi bundle has access to all dependencies needed for built-in beans (&lt;a href=&quot;https://issues.redhat.com/browse/WELD-2796&quot;&gt;WELD-2796&lt;/a&gt;)&lt;/p&gt;
+      &lt;/li&gt;
+      &lt;/ul&gt;
+      &lt;/div&gt;
+      &lt;div class=&quot;paragraph&quot;&gt;
+      &lt;p&gt;[ &lt;a href=&quot;https://weld.cdi-spec.org/download/&quot;&gt;Download&lt;/a&gt; ]
+      [ &lt;a href=&quot;http://docs.jboss.org/weld/reference/5.1.3.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=12414627&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/07/03/weld-600Beta4/</id>
     <title>Weld 6.0.0.Beta4</title>
-    <updated>2024-07-03T12:41:45+00:00</updated>
+    <updated>2024-08-27T14:08:13+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>
@@ -125,7 +226,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2024/02/26/weld-600Beta1/</id>
     <title>Weld 6.0.0.Beta1</title>
-    <updated>2024-03-20T12:52:43+00:00</updated>
+    <updated>2024-08-27T14:08:13+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>
@@ -246,7 +347,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2023/10/26/weld-600Alpha1/</id>
     <title>Weld 6.0.0.Alpha1</title>
-    <updated>2024-03-20T12:52:43+00:00</updated>
+    <updated>2024-08-27T14:08:13+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>
@@ -383,7 +484,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2023/10/05/weld-512Final/</id>
     <title>Weld 5.1.2.Final</title>
-    <updated>2024-03-20T12:52:43+00:00</updated>
+    <updated>2024-08-27T14:08:13+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>
@@ -471,7 +572,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2023/08/09/weld-511SP2/</id>
     <title>Weld 5.1.1.SP2</title>
-    <updated>2024-03-20T12:52:43+00:00</updated>
+    <updated>2024-08-27T14:08:13+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>
@@ -514,7 +615,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2023/07/11/weld-511SP1/</id>
     <title>Weld 5.1.1.SP1</title>
-    <updated>2024-03-20T12:52:43+00:00</updated>
+    <updated>2024-08-27T14:08:13+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>
@@ -578,7 +679,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2023/06/12/weld-511Final/</id>
     <title>Weld 5.1.1.Final</title>
-    <updated>2024-03-20T12:52:43+00:00</updated>
+    <updated>2024-08-27T14:08:13+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>
@@ -667,7 +768,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2022/10/03/weld-510Final/</id>
     <title>Weld 5.1.0.Final</title>
-    <updated>2024-03-20T12:52:43+00:00</updated>
+    <updated>2024-08-27T14:08:13+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>
@@ -759,7 +860,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2022/06/24/weld-501Final/</id>
     <title>Weld 5.0.1.Final</title>
-    <updated>2024-03-20T12:52:43+00:00</updated>
+    <updated>2024-08-27T14:08:13+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>
@@ -834,7 +935,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2022/06/08/weld-500SP2/</id>
     <title>Weld 5.0.0.SP2</title>
-    <updated>2024-03-20T12:52:43+00:00</updated>
+    <updated>2024-08-27T14:08:13+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>
@@ -879,7 +980,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2022/05/04/weld-500SP1/</id>
     <title>Weld 5.0.0.SP1</title>
-    <updated>2024-03-20T12:52:43+00:00</updated>
+    <updated>2024-08-27T14:08:13+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>
@@ -924,7 +1025,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2022/04/29/weld-500Final/</id>
     <title>Weld 5.0.0.Final</title>
-    <updated>2024-03-20T12:52:43+00:00</updated>
+    <updated>2024-08-27T14:08:13+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>
@@ -1007,7 +1108,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2022/03/23/weld-500CR2/</id>
     <title>Weld 5.0.0.CR2</title>
-    <updated>2024-03-20T12:52:43+00:00</updated>
+    <updated>2024-08-27T14:08:13+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>
@@ -1047,7 +1148,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2022/02/23/weld-500CR1/</id>
     <title>Weld 5.0.0.CR1</title>
-    <updated>2024-03-20T12:52:43+00:00</updated>
+    <updated>2024-08-27T14:08:13+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>
@@ -1116,7 +1217,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-03-20T12:52:43+00:00</updated>
+    <updated>2024-08-27T14:08:13+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>
@@ -1213,7 +1314,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2022/01/24/weld-500Beta1/</id>
     <title>Weld 5.0.0.Beta1</title>
-    <updated>2024-03-20T12:52:43+00:00</updated>
+    <updated>2024-08-27T14:08:13+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>
@@ -1524,7 +1625,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-03-20T12:52:43+00:00</updated>
+    <updated>2024-08-27T14:08:13+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>
@@ -1605,7 +1706,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-03-20T12:52:43+00:00</updated>
+    <updated>2024-08-27T14:08:13+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>
@@ -1685,7 +1786,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2021/03/22/weld-401Final/</id>
     <title>Weld 4.0.1.Final</title>
-    <updated>2024-03-20T12:52:43+00:00</updated>
+    <updated>2024-08-27T14:08:13+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>
@@ -1804,7 +1905,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2021/03/18/weld-317Final/</id>
     <title>Weld 3.1.7.Final</title>
-    <updated>2024-03-20T12:52:43+00:00</updated>
+    <updated>2024-08-27T14:08:13+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>
@@ -1918,7 +2019,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2021/01/13/weld-316Final/</id>
     <title>Weld 3.1.6.Final</title>
-    <updated>2024-03-20T12:52:43+00:00</updated>
+    <updated>2024-08-27T14:08:13+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>
@@ -2076,7 +2177,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2020/12/16/weld-400Final/</id>
     <title>Weld 4.0.0.Final</title>
-    <updated>2024-03-20T12:52:43+00:00</updated>
+    <updated>2024-08-27T14:08:13+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>
@@ -2154,7 +2255,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2020/09/18/weld-400Beta1/</id>
     <title>Weld 4.0.0.Beta1</title>
-    <updated>2024-03-20T12:52:43+00:00</updated>
+    <updated>2024-08-27T14:08:13+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>
@@ -2271,7 +2372,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2020/08/12/weld-315Final/</id>
     <title>Weld 3.1.5.Final</title>
-    <updated>2024-03-20T12:52:43+00:00</updated>
+    <updated>2024-08-27T14:08:13+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>
@@ -2409,7 +2510,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-03-20T12:52:43+00:00</updated>
+    <updated>2024-08-27T14:08:13+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>
@@ -2548,7 +2649,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2020/03/28/weld-314Final/</id>
     <title>Weld 3.1.4.Final</title>
-    <updated>2024-03-20T12:52:43+00:00</updated>
+    <updated>2024-08-27T14:08:13+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>
@@ -2660,7 +2761,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2019/11/28/weld-313Final/</id>
     <title>Weld 3.1.3.Final</title>
-    <updated>2024-03-20T12:52:43+00:00</updated>
+    <updated>2024-08-27T14:08:13+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>
@@ -2794,7 +2895,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2019/08/06/weld-312Final/</id>
     <title>Weld 3.1.2.Final</title>
-    <updated>2024-03-20T12:52:43+00:00</updated>
+    <updated>2024-08-27T14:08:13+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>
@@ -2948,7 +3049,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2019/05/07/weld-311Final/</id>
     <title>Weld 3.1.1.Final</title>
-    <updated>2024-03-20T12:52:43+00:00</updated>
+    <updated>2024-08-27T14:08:13+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>
@@ -3081,7 +3182,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2019/02/06/weld-310Final/</id>
     <title>Weld 3.1.0.Final</title>
-    <updated>2024-03-20T12:52:43+00:00</updated>
+    <updated>2024-08-27T14:08:13+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>
@@ -3333,7 +3434,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2018/09/26/weld-248Final/</id>
     <title>Weld 2.4.8.Final</title>
-    <updated>2024-03-20T12:52:43+00:00</updated>
+    <updated>2024-08-27T14:08:13+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>
@@ -3470,7 +3571,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2018/07/26/weld-305Final/</id>
     <title>Weld 3.0.5.Final</title>
-    <updated>2024-03-20T12:52:43+00:00</updated>
+    <updated>2024-08-27T14:08:13+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>
@@ -3634,7 +3735,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2018/07/10/weld-team-changes/</id>
     <title>Weld team changes</title>
-    <updated>2024-03-20T12:52:43+00:00</updated>
+    <updated>2024-08-27T14:08:13+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>
@@ -3683,7 +3784,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2018/04/26/weld-304Final/</id>
     <title>Weld 3.0.4.Final</title>
-    <updated>2024-03-20T12:52:43+00:00</updated>
+    <updated>2024-08-27T14:08:13+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>
@@ -3882,7 +3983,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2018/03/20/weld-247Final/</id>
     <title>Weld 2.4.7.Final</title>
-    <updated>2024-03-20T12:52:43+00:00</updated>
+    <updated>2024-08-27T14:08:13+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>
@@ -4065,7 +4166,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2018/02/09/weld-303Final/</id>
     <title>Weld 3.0.3.Final</title>
-    <updated>2024-03-20T12:52:43+00:00</updated>
+    <updated>2024-08-27T14:08:13+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>
@@ -4200,7 +4301,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2017/12/19/weld-meets-junit5/</id>
     <title>Weld meets JUnit 5</title>
-    <updated>2024-03-20T12:52:43+00:00</updated>
+    <updated>2024-08-27T14:08:13+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>
@@ -4377,7 +4478,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2017/12/18/weld-246Final/</id>
     <title>Weld 2.4.6.Final</title>
-    <updated>2024-03-20T12:52:43+00:00</updated>
+    <updated>2024-08-27T14:08:13+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>
@@ -4556,7 +4657,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2017/11/23/weld-302Final/</id>
     <title>Weld 3.0.2.Final</title>
-    <updated>2024-03-20T12:52:43+00:00</updated>
+    <updated>2024-08-27T14:08:13+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>
@@ -4731,7 +4832,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2017/09/11/weld-245Final/</id>
     <title>Weld 2.4.5.Final</title>
-    <updated>2024-03-20T12:52:43+00:00</updated>
+    <updated>2024-08-27T14:08:13+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>
@@ -4848,7 +4949,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2017/08/25/weld-301Final/</id>
     <title>Weld 3.0.1.Final</title>
-    <updated>2024-03-20T12:52:43+00:00</updated>
+    <updated>2024-08-27T14:08:13+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>
@@ -4999,7 +5100,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2017/08/07/weld-vertx-next/</id>
     <title>Weld Vert.x Next?</title>
-    <updated>2024-03-20T12:52:43+00:00</updated>
+    <updated>2024-08-27T14:08:13+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>
@@ -5258,7 +5359,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2017/06/14/weld-244Final/</id>
     <title>Weld 2.4.4.Final</title>
-    <updated>2024-03-20T12:52:43+00:00</updated>
+    <updated>2024-08-27T14:08:13+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>
@@ -5410,7 +5511,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-03-20T12:52:43+00:00</updated>
+    <updated>2024-08-27T14:08:13+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>
@@ -5728,7 +5829,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-03-20T12:52:43+00:00</updated>
+    <updated>2024-08-27T14:08:13+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>
@@ -5906,7 +6007,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2017/04/07/weld-243Final/</id>
     <title>Weld 2.4.3.Final</title>
-    <updated>2024-03-20T12:52:43+00:00</updated>
+    <updated>2024-08-27T14:08:13+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>
@@ -6034,7 +6135,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2017/03/03/weld-300CR2/</id>
     <title>Weld 3.0.0.CR2</title>
-    <updated>2024-03-20T12:52:43+00:00</updated>
+    <updated>2024-08-27T14:08:13+00:00</updated>
     <published>2017-03-03T00:00:00+00:00</published>
     <link href="https://weld.cdi-spec.org/news/2017/03/03/weld-300CR2/" rel="alternate" type="text/html" />
     <author>
@@ -6170,7 +6271,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2017/02/02/weld-242Final/</id>
     <title>Weld 2.4.2.Final</title>
-    <updated>2024-03-20T12:52:43+00:00</updated>
+    <updated>2024-08-27T14:08:13+00:00</updated>
     <published>2017-02-02T00:00:00+00:00</published>
     <link href="https://weld.cdi-spec.org/news/2017/02/02/weld-242Final/" rel="alternate" type="text/html" />
     <author>
@@ -6288,7 +6389,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2017/02/01/tip4-testing/</id>
     <title>Weld Tip 4 - Testing CDI/Weld apps</title>
-    <updated>2024-03-20T12:52:43+00:00</updated>
+    <updated>2024-08-27T14:08:13+00:00</updated>
     <published>2017-02-01T00:00:00+00:00</published>
     <link href="https://weld.cdi-spec.org/news/2017/02/01/tip4-testing/" rel="alternate" type="text/html" />
     <author>
@@ -6548,56 +6649,4 @@
       &lt;/div&gt;
     </content>
   </entry>
-  <entry>
-    <id>https://weld.cdi-spec.org/news/2017/01/23/weld-300CR1/</id>
-    <title>Weld 3.0.0.CR1</title>
-    <updated>2024-03-20T12:52:43+00:00</updated>
-    <published>2017-01-23T00:00:00+00:00</published>
-    <link href="https://weld.cdi-spec.org/news/2017/01/23/weld-300CR1/" rel="alternate" type="text/html" />
-    <author>
-      <name>Martin Kouba</name>
-    </author>
-    <category term="release"></category>
-    <summary>
-      I am very pleased to announce the release of Weld 3.0.0.CR1 (aligned with CDI 2.0-PFD).
-      See also the release details.
-      Thanks to everyone involved in this release!
-      This version of Weld will be part of the JSR 365 Approval Ballot (watch CDI spec website for news).
-      The Beta1 version of Weld 3 turned out to be sufficiently stable and so the first release candidate is mostly dedicated to cleanup and minor optimizations.
-      We would like to release Weld 3.0.0.Final (stable version of CDI 2.0) in early February.
-      
-      
-      WildFly Patch
-      
-      
-      As usual, a patch for WildFly is available.
-      This time the target platform is WildFly 10.1.0.Final.
-      If you’re not familiar...
-    </summary>
-    <content type="html">
-      &lt;div class=&quot;paragraph&quot;&gt;
-      &lt;p&gt;I am very pleased to announce the release of Weld &lt;strong&gt;3.0.0.CR1&lt;/strong&gt; (aligned with &lt;strong&gt;CDI 2.0-PFD&lt;/strong&gt;).
-      See also &lt;a href=&quot;https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;amp;version=12331714&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;the release details&lt;/a&gt;.
-      Thanks to everyone involved in this release!
-      This version of Weld will be part of the JSR 365 Approval Ballot (watch &lt;a href=&quot;http://cdi-spec.org/&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;CDI spec website&lt;/a&gt; for news).
-      The Beta1 version of Weld 3 turned out to be sufficiently stable and so the first release candidate is mostly dedicated to cleanup and minor optimizations.
-      We would like to release Weld &lt;strong&gt;3.0.0.Final&lt;/strong&gt; (stable version of CDI 2.0) in early February.&lt;/p&gt;
-      &lt;/div&gt;
-      &lt;div class=&quot;sect1&quot;&gt;
-      &lt;h2 id=&quot;_wildfly_patch&quot;&gt;WildFly Patch&lt;/h2&gt;
-      &lt;div class=&quot;sectionbody&quot;&gt;
-      &lt;div class=&quot;paragraph&quot;&gt;
-      &lt;p&gt;As usual, a &lt;a href=&quot;http://download.jboss.org/weld/3.0.0.CR1/wildfly-10.1.0.Final-weld-3.0.0.CR1-patch.zip&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;patch for WildFly&lt;/a&gt; is available.
-      This time the target platform is &lt;strong&gt;WildFly 10.1.0.Final&lt;/strong&gt;.
-      If you’re not familiar with patching WildFly, check the &lt;a href=&quot;https://weld.cdi-spec.org/documentation/#12&quot;&gt;FAQ&lt;/a&gt;.&lt;/p&gt;
-      &lt;/div&gt;
-      &lt;div class=&quot;paragraph&quot;&gt;
-      &lt;p&gt;[ &lt;a href=&quot;https://weld.cdi-spec.org/download/&quot;&gt;Download&lt;/a&gt; ]
-      [ &lt;a href=&quot;http://docs.jboss.org/weld/reference/3.0.0.CR1/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=12331714&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/08/27/weld-513Final/index.html b/news/2024/08/27/weld-513Final/index.html
new file mode 100644
index 00000000..c9f81f80
--- /dev/null
+++ b/news/2024/08/27/weld-513Final/index.html
@@ -0,0 +1,268 @@
+<!DOCTYPE html>
+<html>
+  <head>
+    <meta charset="utf-8">
+    <title>
+      Weld: Weld 5.1.3.Final
+    </title>
+    <meta content="width=device-width, initial-scale=1.0" name="viewport">
+    <meta content="Squashing bugs with Weld 5.1.3.Final!" name="description">
+    <link href="/images/weld_icon_32x.ico" rel="shortcut icon" type="image/x-icon">
+    <link href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.5/css/bootstrap.min.css" rel="stylesheet" type="text/css">
+    <link href="https://maxcdn.bootstrapcdn.com/font-awesome/4.4.0/css/font-awesome.min.css" rel="stylesheet" type="text/css">
+    <link href="//static.jboss.org/css/tabzilla.css" media="screen" rel="stylesheet" type="text/css">
+    <link href="https://weld.cdi-spec.org/stylesheets/styles.css" rel="stylesheet" type="text/css">
+    <script src="//static.jboss.org/theme/js/libs/jquery/jquery-1.9.1.min.js" type="text/javascript"></script>
+    <script src="//static.jboss.org/js/_jbossorg-tabzilla.js" type="text/javascript"></script>
+    <!--[if lt IE 9]>
+      <script src="//html5shim.googlecode.com/svn/trunk/html5.js" type="text/javascript"></script>
+    <![endif]-->
+    <link href="https://weld.cdi-spec.org/news.atom" rel="alternate" type="application/atom+xml">
+    <link href="//cdn.jsdelivr.net/highlight.js/8.9.1/styles/hybrid.min.css" rel="stylesheet">
+    <script src="//cdn.jsdelivr.net/highlight.js/8.9.1/highlight.min.js" type="text/javascript"></script>
+    <script>
+      hljs.initHighlightingOnLoad();
+    </script>
+  </head>
+  <body>
+    <div class="container-fluid">
+      <div class="row">
+        <div class="col-md-2 col-sm-3">
+          <div class="sidebar-nav">
+            <div class="navbar navbar-default" role="navigation">
+              <div class="navbar-header">
+                <button ="button" class="navbar-toggle" data-target=".sidebar-navbar-collapse" data-toggle="collapse">
+                  <span class="sr-only">
+                    Toggle navigation
+                  </span>
+                  <span class="icon-bar"></span>
+                  <span class="icon-bar"></span>
+                  <span class="icon-bar"></span>
+                  <span class="icon-bar"></span>
+                </button>
+                <a ="#" class="visible-xs navbar-brand">
+                  <img alt="Weld Logo" src="/images/weld_logo_100x.png">
+                </a>
+              </div>
+              <div class="collapse navbar-collapse sidebar-navbar-collapse">
+                <ul class="nav navbar-nav">
+                  <li>
+                    <a href="/">
+                      <i class="fa fa-home"></i>
+                      &nbsp;Home
+                    </a>
+                  </li>
+                  <li>
+                    <a href="/download">
+                      <i class="fa fa-download"></i>
+                      &nbsp;Download
+                    </a>
+                  </li>
+                  <li>
+                    <a href="/news">
+                      <i class="fa fa-newspaper-o"></i>
+                      &nbsp;News
+                    </a>
+                  </li>
+                  <li>
+                    <a href="https://issues.jboss.org/projects/WELD?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page" target="_blank">
+                      <i class="fa fa-road"></i>
+                      &nbsp;Road Map
+                    </a>
+                  </li>
+                  <li>
+                    <a href="/documentation">
+                      <i class="fa fa-book"></i>
+                      &nbsp;Docs &amp; FAQ
+                    </a>
+                  </li>
+                  <li>
+                    <a href="/news/tags/tips">
+                      <i class="fa fa-lightbulb-o"></i>
+                      &nbsp;Tips and Tricks
+                    </a>
+                  </li>
+                  <li>
+                    <a href="/community">
+                      <i class="fa fa-group"></i>
+                      &nbsp;Community
+                    </a>
+                  </li>
+                  <li>
+                    <a href="http://github.com/weld" target="_blank">
+                      <i class="fa fa-github-alt"></i>
+                      &nbsp;Source Code
+                    </a>
+                  </li>
+                  <li>
+                    <a href="https://issues.jboss.org/browse/WELD#selectedTab=com.atlassian.jira.plugin.system.project%3Asummary-panel" target="_blank">
+                      <i class="fa fa-tasks"></i>
+                      &nbsp;Bug Tracker
+                    </a>
+                  </li>
+                  <li>
+                    <a href="https://twitter.com/jbossweld" target="_blank">
+                      <i class="fa fa-twitter"></i>
+                      &nbsp;Follow @jbossweld
+                    </a>
+                  </li>
+                </ul>
+              </div>
+            </div>
+          </div>
+        </div>
+        <div class="col-md-10 col-sm-9">
+          <div class="row hidden-xs">
+            <div class="dropup">
+              <div id="ajbossproject">
+                A JBoss Project
+              </div>
+              <a class="tabnav-closed" href="#" id="tab">Red Hat</a>
+              <script>
+                window.addEventListener('load', function() {renderTabzilla("Weld", "weld", false )}, false);
+              </script>
+            </div>
+          </div>
+          <div class="row">
+            <div class="col-md-4">
+              <a href="/">
+                <img alt="Weld Logo" class="hidden-xs weld-home-logo" src="/images/weld_logo_450x.png">
+              </a>
+            </div>
+            <div class="col-md-8">
+              <img alt="CDI tagcloud" class="hidden-xs hidden-sm cdi-background" src="/images/CDIbackground.png">
+            </div>
+          </div>
+          <div class="row content-wrapper">
+            <div class="col-md-12">
+              <div class="post">
+                <h1>
+                  Weld 5.1.3.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-8-27
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/release">release</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Matej Novotny
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>A new version of Weld 5.1 has landed in Maven Central.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>This is a bug squashing round which backports several notable fixes and changes from Weld 6 into Weld 5:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Change <code>BeanManager</code> resolution process for <code>BuildCompatibleExtension</code> not belonging to any bean archive (<a href="https://issues.redhat.com/browse/WELD-2794">WELD-2794</a>)</p>
+                  </li>
+                  <li>
+                  <p><code>LazySessionBeanStore</code> no longer swallows exceptions happening when attempting to initiate HTTP session (<a href="https://issues.redhat.com/browse/WELD-2762">WELD-2762</a>)</p>
+                  </li>
+                  <li>
+                  <p>Correct how we determine proxy package for beans with unassignable types in their bean type set (<a href="https://issues.redhat.com/browse/WELD-2763">WELD-2763</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>This was only problematic in environments using WeldDefaultProxyServices to define their proxies (such as Weld SE)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </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>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>Correct inheritance of producer fields if there is an extension present (<a href="https://issues.redhat.com/browse/WELD-2773">WELD-2773</a>)</p>
+                  </li>
+                  <li>
+                  <p>Make sure <code>@Default</code> qualifier is added to events fired via <code>BeanManager#getEvent()</code> where appropriate (<a href="https://issues.redhat.com/browse/WELD-2775">WELD-2775</a>)</p>
+                  </li>
+                  <li>
+                  <p>Observer method confiurator now correctly allows 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>Clean up legacy Jetty integration parts (<a href="https://issues.redhat.com/browse/WELD-2787">WELD-2787</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>Ensure OSGi bundle has access to all dependencies needed for built-in beans (<a href="https://issues.redhat.com/browse/WELD-2796">WELD-2796</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="/download/">Download</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/5.1.3.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=12414627" 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/08/27/weld-513Final/";
+                            var disqus_developer = null;
+                            var disqus_identifier = "a0aebc3f453f09c1563dc71ee03e817b9834d2f3";
+                            (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 8285487a..8281970b 100644
--- a/news/index.html
+++ b/news/index.html
@@ -141,6 +141,84 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2024/08/27/weld-513Final/">Weld 5.1.3.Final</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2024-8-27
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/release">release</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Matej Novotny
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>A new version of Weld 5.1 has landed in Maven Central.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>This is a bug squashing round which backports several notable fixes and changes from Weld 6 into Weld 5:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Change <code>BeanManager</code> resolution process for <code>BuildCompatibleExtension</code> not belonging to any bean archive (<a href="https://issues.redhat.com/browse/WELD-2794">WELD-2794</a>)</p>
+                  </li>
+                  <li>
+                  <p><code>LazySessionBeanStore</code> no longer swallows exceptions happening when attempting to initiate HTTP session (<a href="https://issues.redhat.com/browse/WELD-2762">WELD-2762</a>)</p>
+                  </li>
+                  <li>
+                  <p>Correct how we determine proxy package for beans with unassignable types in their bean type set (<a href="https://issues.redhat.com/browse/WELD-2763">WELD-2763</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>This was only problematic in environments using WeldDefaultProxyServices to define their proxies (such as Weld SE)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </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>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>Correct inheritance of producer fields if there is an extension present (<a href="https://issues.redhat.com/browse/WELD-2773">WELD-2773</a>)</p>
+                  </li>
+                  <li>
+                  <p>Make sure <code>@Default</code> qualifier is added to events fired via <code>BeanManager#getEvent()</code> where appropriate (<a href="https://issues.redhat.com/browse/WELD-2775">WELD-2775</a>)</p>
+                  </li>
+                  <li>
+                  <p>Observer method confiurator now correctly allows 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>Clean up legacy Jetty integration parts (<a href="https://issues.redhat.com/browse/WELD-2787">WELD-2787</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>Ensure OSGi bundle has access to all dependencies needed for built-in beans (<a href="https://issues.redhat.com/browse/WELD-2796">WELD-2796</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="/download/">Download</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/5.1.3.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=12414627" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2024/07/03/weld-600Beta4/">Weld 6.0.0.Beta4</a>
@@ -524,41 +602,6 @@ <h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2023/08/09/weld-511SP2/">Weld 5.1.1.SP2</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2023-8-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>Another bug-smashing release has landed in Maven Central and this time it&#8217;s Weld 5.1.1.SP2.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>This is a very small but important change which addresses possible memory leak scenario (<a href="https://issues.redhat.com/browse/WELD-2750">WELD-2750</a>).
-                  There are multiple conditions for this leak to occur and while most applications are unlikely to be affected, it is still recommended to upgrade to this latest version.</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.SP2/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=12410416" target="_blank" rel="noopener">Release notes</a> &#93;</p>
-                  </div>
-                </div>
-                <hr>
-              </div>
               <div class="pagination-links"><span class="current-page">1</span> <a href="/news/page/2.html" class="page-link">2</a> <span class="skip">...</span><a href="/news/page/18.html" class="page-link">18</a> <a href="/news/page/19.html" class="page-link">19</a> <a href="/news/page/2.html" class="next-link">Next</a> </div>
               <hr>
               <div>
diff --git a/news/page/10.html b/news/page/10.html
index c1132577..dc28b8f8 100644
--- a/news/page/10.html
+++ b/news/page/10.html
@@ -141,6 +141,155 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2017/05/15/weld-300Final/">Weld 3.0.0.Final - the first implementation of CDI 2.0!</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2017-5-15
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/release">release</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Martin Kouba
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>I am very pleased to announce the release of Weld <strong>3.0.0.Final</strong> - the first implementation of <strong>CDI 2.0</strong>!
+                  I would like to thank not only to everyone involved in this particular release but also to the Weld community as a whole and also to all active CDI EG members who invested a lot of energy into the specification process!</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>[ source, java ]</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre>/**&#x000A;     * TODO: Continue to deliver bugfixes and improvements&#x000A;     */&#x000A;    public class WeldTeam extends OpenSourceCommunity {&#x000A;    &#x000A;      @Inject&#x000A;      @AwesomeNews&#x000A;      Event&lt;String&gt; event;&#x000A;    &#x000A;      public void release() {&#x000A;        // Fire asynchronously so that we don't need to wait for observer notification before we start celebrating!&#x000A;        event.fireAsync("CDI 1.2 is dead, long live CDI 2.0!");&#x000A;        celebrate();&#x000A;      }&#x000A;    &#x000A;    }</pre>
+                  </div>
+                  </div>
+                  <div class="admonitionblock note">
+                  <table>
+                  <tr>
+                  <td class="icon">
+                  <div class="title">Note</div>
+                  </td>
+                  <td class="content">
+                  Weld 3 is an IMPORTANT MILESTONE.
+                  Therefore, we&#8217;re preparing a special blogpost summarizing all the important stuff that was added.
+                  Expect the <strong>Tour around Weld 3</strong> blogpost within a few days.
+                  </td>
+                  </tr>
+                  </table>
+                  </div>
+                  <div class="paragraph">
+                  <p>Let&#8217;s sum up the notable changes since <strong>3.0.0.CR2</strong>:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Weld defines two non-portable <strong>notification options</strong> to configure the notification of asynchronous observer methods (see also <a href="http://docs.jboss.org/weld/reference/3.0.0.Final/en-US/html/events.html#_notification_options" target="_blank" rel="noopener">Notification options</a> for more info):</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p><code>weld.async.notification.mode</code> - the notification mode, possible values are: <code>SERIAL</code> (default) and <code>PARALLEL</code></p>
+                  </li>
+                  <li>
+                  <p><code>weld.async.notification.timeout</code> - the notification timeout (in milliseconds) after which the returned completion stage must be completed.</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>If the time expires the stage is completed exceptionally with a <code>CompletionException</code> holding the <code>java.util.concurrent.TimeoutException</code> as its cause</p>
+                  </li>
+                  <li>
+                  <p>The expiration does not abort the notification of the observers</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Session replication - 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>
+                  <li>
+                  <p>Fire <code>@Initialied(RequestScoped.class)</code>/<code>@Destroyed(RequestScoped.class)</code> events for a <code>@PostConstruct</code> callback if the request context was activated for the specific callback</p>
+                  </li>
+                  <li>
+                  <p>Weld SE</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>It&#8217;s possible to easily register a <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> 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>Weld Servlet</p>
+                  <div class="ulist">
+                  <ul>
+                  <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>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Added option to disable Jandex in Weld SE and Weld Servlet (<a href="https://issues.jboss.org/browse/WELD-2374" target="_blank" rel="noopener">WELD-2374</a>)</p>
+                  </li>
+                  <li>
+                  <p>Development tools</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>If a deployment validation fails and the development mode is enabled a simple <strong>validation HTML report</strong> (which contains a lot of useful information) is generated</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Users are encouraged to always attach this report when asking a question on the mailing list or any other communication channel</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Updated documentation and migration notes for integrators</p>
+                  </li>
+                  <li>
+                  <p>Examples cleanup (dropped GAE support, etc.)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_wildfly_patch">WildFly Patch</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>As usual, a <a href="http://wildfly.org/" target="_blank" rel="noopener">patch for WildFly</a> is available.
+                  This time the target platforms are <a href="http://download.jboss.org/weld/3.0.0.Final/wildfly-10.1.0.Final-weld-3.0.0.Final-patch.zip" target="_blank" rel="noopener">WildFly 10.1.0.Final</a> and <a href="http://download.jboss.org/weld/3.0.0.Final/wildfly-11.0.0.Alpha1-weld-3.0.0.Final-patch.zip" target="_blank" rel="noopener">WildFly 11.0.0.Alpha1</a>.
+                  If you’re not familiar with patching WildFly, check the <a href="/documentation/#12">FAQ</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="/download/">Download</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/3.0.0.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=12333608" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2017/04/07/weld-243Final/">Weld 2.4.3.Final</a>
@@ -644,49 +793,6 @@ <h2 id="_arquillian_weld_embedded_container">Arquillian Weld Embedded container<
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2017/01/23/weld-300CR1/">Weld 3.0.0.CR1</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2017-1-23
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/release">release</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Martin Kouba
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>I am very pleased to announce the release of Weld <strong>3.0.0.CR1</strong> (aligned with <strong>CDI 2.0-PFD</strong>).
-                  See also <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12331714" target="_blank" rel="noopener">the release details</a>.
-                  Thanks to everyone involved in this release!
-                  This version of Weld will be part of the JSR 365 Approval Ballot (watch <a href="http://cdi-spec.org/" target="_blank" rel="noopener">CDI spec website</a> for news).
-                  The Beta1 version of Weld 3 turned out to be sufficiently stable and so the first release candidate is mostly dedicated to cleanup and minor optimizations.
-                  We would like to release Weld <strong>3.0.0.Final</strong> (stable version of CDI 2.0) in early February.</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.CR1/wildfly-10.1.0.Final-weld-3.0.0.CR1-patch.zip" target="_blank" rel="noopener">patch for WildFly</a> is available.
-                  This time the target platform is <strong>WildFly 10.1.0.Final</strong>.
-                  If you’re not familiar with patching WildFly, check the <a href="/documentation/#12">FAQ</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>&#91; <a href="/download/">Download</a> &#93;
-                  &#91; <a href="http://docs.jboss.org/weld/reference/3.0.0.CR1/en-US/html/" target="_blank" rel="noopener">Documentation</a> &#93;
-                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12331714" target="_blank" rel="noopener">Release notes</a> &#93;</p>
-                  </div>
-                  </div>
-                  </div>
-                </div>
-                <hr>
-              </div>
               <div class="pagination-links"><a href="/news/page/9.html" class="previous-link">Previous</a> <a href="/news/" class="page-link">1</a> <a href="/news/page/2.html" class="page-link">2</a> <span class="skip">...</span><a href="/news/page/9.html" class="page-link">9</a> <span class="current-page">10</span> <a href="/news/page/11.html" class="page-link">11</a> <span class="skip">...</span><a href="/news/page/18.html" class="page-link">18</a> <a href="/news/page/19.html" class="page-link">19</a> <a href="/news/page/11.html" class="next-link">Next</a> </div>
               <hr>
               <div>
diff --git a/news/page/11.html b/news/page/11.html
index 30e4ed25..30e9e227 100644
--- a/news/page/11.html
+++ b/news/page/11.html
@@ -141,6 +141,49 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2017/01/23/weld-300CR1/">Weld 3.0.0.CR1</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2017-1-23
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/release">release</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Martin Kouba
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>I am very pleased to announce the release of Weld <strong>3.0.0.CR1</strong> (aligned with <strong>CDI 2.0-PFD</strong>).
+                  See also <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12331714" target="_blank" rel="noopener">the release details</a>.
+                  Thanks to everyone involved in this release!
+                  This version of Weld will be part of the JSR 365 Approval Ballot (watch <a href="http://cdi-spec.org/" target="_blank" rel="noopener">CDI spec website</a> for news).
+                  The Beta1 version of Weld 3 turned out to be sufficiently stable and so the first release candidate is mostly dedicated to cleanup and minor optimizations.
+                  We would like to release Weld <strong>3.0.0.Final</strong> (stable version of CDI 2.0) in early February.</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.CR1/wildfly-10.1.0.Final-weld-3.0.0.CR1-patch.zip" target="_blank" rel="noopener">patch for WildFly</a> is available.
+                  This time the target platform is <strong>WildFly 10.1.0.Final</strong>.
+                  If you’re not familiar with patching WildFly, check the <a href="/documentation/#12">FAQ</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="/download/">Download</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/3.0.0.CR1/en-US/html/" target="_blank" rel="noopener">Documentation</a> &#93;
+                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12331714" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2016/12/19/weld-300Beta1/">Weld 3.0.0.Beta1</a>
@@ -833,205 +876,6 @@ <h2 id="probe-offline">Does it work offline?</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2016/10/01/tip1-logging/">Weld Tip 1 - Logging</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2016-10-1
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/tips">tips</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Martin Kouba
-                </div>
-                <p></p>
-                <div class="content">
-                  <div id="toc" class="toc">
-                  <div id="toctitle" class="title">Contents</div>
-                  <ul class="sectlevel1">
-                  <li><a href="#_motivation">Motivation</a></li>
-                  <li><a href="#under_the_hood">Under the hood</a></li>
-                  <li><a href="#filter">Set the log level and use categories to filter messages</a></li>
-                  <li><a href="#bootstrap">Monitoring bootstrap</a>
-                  <ul class="sectlevel2">
-                  <li><a href="#_registered_beans">Registered beans</a></li>
-                  <li><a href="#_actions_performed_by_extensions">Actions performed by extensions</a></li>
-                  </ul>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>This is the first article from a series of short articles covering some useful Weld features.
-                  In this article we talk about logging.
-                  The topics for the next articles include: <strong>DEVELOPMENT MODE</strong>, <strong>PERFORMANCE</strong>, <strong>NON-EE ENVIRONMENTS</strong> and <strong>TESTING</strong>.</p>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_motivation">Motivation</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>Logging is usually no fancy stuff.
-                  But very often it&#8217;s <em>the best thing to start with if problems arise</em>.
-                  Moreover, it&#8217;s the easiest form of debugging.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>In this article you will find:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p><a href="#under_the_hood">Under the hood</a> - how to control and configure the output</p>
-                  </li>
-                  <li>
-                  <p><a href="#filter">Set the log level and use categories to filter messages</a> - how to keep logs small and to the point</p>
-                  </li>
-                  <li>
-                  <p><a href="#bootstrap">Monitoring bootstrap</a> - registered beans, actions performed by extensions</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="under_the_hood">Under the hood</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>Weld is using <a href="https://developer.jboss.org/wiki/JBossLoggingTooling">JBoss Logging</a>.
-                  This is an abstraction layer wchich does not "write" any log messages at all.
-                  Instead, it effectively constructs a log message and then delegates to a back-end logging framework.
-                  The supported frameworks include <a href="https://developer.jboss.org/wiki/StandaloneJBossLogManager">jboss-logmanager</a>, <a href="http://logging.apache.org/log4j/2.x/">Log4j</a>, <a href="http://www.slf4j.org/">SLF4J</a> and JDK logging.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>So which logging framework is actually used to write the Weld messages?
-                  Well, it depends on the environment.
-                  In a <strong>Java EE container</strong> (e.g. WildFly) the logging configuration is under the direction of the container.
-                  You should follow the container-specific guides to change the configuration (see for example <a href="https://docs.jboss.org/author/display/WFLY10/Logging+Configuration">WildFly - Logging Configuration</a> and <a href="/documentation/#7">How do I enable debug logging for Weld in a specific container?</a>).</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>A web application deployed to a <strong>servlet container</strong> usually bundles a logging framework and possibly some configuration file.
-                  In this case, the configuration is in hands of the application developer.
-                  If no logging framework is bundled follow the container-specific guides to change the configuration (e.g. <a href="http://tomcat.apache.org/tomcat-8.0-doc/logging.html">Logging in Tomcat</a>).</p>
-                  </div>
-                  <div class="admonitionblock tip">
-                  <table>
-                  <tr>
-                  <td class="icon">
-                  <div class="title">Tip</div>
-                  </td>
-                  <td class="content">
-                  A system property <code>org.jboss.logging.provider</code> can be used to specify the logging framework directly. If not set, the JBoss Logging will attempt to find the "best match" on the classpath. See also <a href="https://github.com/jboss-logging/jboss-logging/blob/master/src/main/java/org/jboss/logging/LoggerProviders.java" target="_blank" rel="noopener">LoggerProviders</a>.
-                  </td>
-                  </tr>
-                  </table>
-                  </div>
-                  <div class="paragraph">
-                  <p>In <strong>Java SE</strong> the situation is very similar to servlet containers except the class loading is usually even less complicated (see also <a href="/documentation/#10"> How do I enable debug logging for Weld SE?</a>).</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="filter">Set the log level and use categories to filter messages</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>The default log level is usually <code>INFO</code>.
-                  Weld does not log that much information with this level.
-                  You will have to set the log level to <code>DEBUG</code> (or even <code>TRACE</code>) to see what&#8217;s going on in your application.
-                  If you set the level globally (for all frameworks and libraries), the log files will be bloated and it will be very hard to get some relevant info from there.
-                  If you set the level for Weld only (i.e. for <code>org.jboss.weld</code>), it should be better.
-                  Moreover, it&#8217;s possible to use categories to filter messages from a particular "domain".
-                  Weld log messages are grouped into several categories:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p><code>org.jboss.weld.Bootstrap</code></p>
-                  </li>
-                  <li>
-                  <p><code>org.jboss.weld.Validator</code></p>
-                  </li>
-                  <li>
-                  <p><code>org.jboss.weld.Bean</code></p>
-                  </li>
-                  <li>
-                  <p><code>org.jboss.weld.Context</code></p>
-                  </li>
-                  <li>
-                  <p><code>org.jboss.weld.El</code></p>
-                  </li>
-                  <li>
-                  <p>and others (see also <a href="https://github.com/weld/core/blob/master/impl/src/main/java/org/jboss/weld/logging/Category.java" target="_blank" rel="noopener">org.jboss.weld.logging.Category</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>So for example, if you&#8217;re only interested in log messages related to <strong>EL resolution</strong> set the log level for the <code>org.jboss.weld.El</code> category to <code>TRACE</code> (or level with corresponding priority).
-                  Another useful example is the check of <a href="http://docs.jboss.org/weld/reference/latest/en-US/html/configure.html#_weld_configuration" target="_blank" rel="noopener">Weld configuration</a>.
-                  Simply set the log level to <code>DEBUG</code> and filter the <code>org.jboss.weld.Configuration</code> category:</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre>DEBUG [Configuration] WELD-001907: Reading properties file: test.war/WEB-INF/classes/weld.properties&#x000A;    DEBUG [Configuration] WELD-001903: Configuration key RESOLUTION_CACHE_SIZE already set to 1 000 in a source with higher priority, value 500 from system properties is ignored&#x000A;    DEBUG [Configuration] WELD-001904: Unsupported configuration key found and ignored: com.foo.bar&#x000A;    DEBUG [Configuration] WELD-001902: Configuration initialized: {CONCURRENT_DEPLOYMENT=false, RESOLUTION_CACHE_SIZE=1000, RELAXED_CONSTRUCTION=true}</pre>
-                  </div>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="bootstrap">Monitoring bootstrap</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>CDI is designed to fail fast.
-                  An extensive validation is performed during application initialization in order to avoid malicious errors at runtime.
-                  Container usually also logs a lot of interesting info during bootstrap.
-                  Let&#8217;s try to set the log level to <strong>DEBUG</strong> for the <code>org.jboss.weld.Bootstrap</code> category and see what we get.</p>
-                  </div>
-                  <div class="sect2">
-                  <h3 id="_registered_beans">Registered beans</h3>
-                  <div class="paragraph">
-                  <p>As simple as it looks - Weld logs <em>all the beans</em> found in the application, e.g.:</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre>DEBUG [Bootstrap] WELD-000106: Bean: Managed Bean [class org.jboss.cdi.tck.tests.lookup.dependency.resolution.broken.unsatisfied.Vanilla] with qualifiers [@Any @Default]&#x000A;    DEBUG [Bootstrap] WELD-000106: Bean: Producer Method [String[]] with qualifiers [@BatchProperty @Any] declared as [[UnbackedAnnotatedMethod] @Produces @BatchProperty public org.jberet.creation.BatchBeanProducer.getStringArray(InjectionPoint)]</pre>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect2">
-                  <h3 id="_actions_performed_by_extensions">Actions performed by extensions</h3>
-                  <div class="paragraph">
-                  <p>There is no doubt that portable extensions are really powerful.
-                  They can change almost anything.
-                  That&#8217;s great for framework/libraries developers.
-                  On the other hand, this may cause problems when looking for a bug.
-                  There is an application class provided by a developer but what does the CDI container actually see?
-                  Well, it depends&#8230;&#8203; because portable extensions are allowed to redefine this.
-                  And that&#8217;s why Weld logs all the <em>"modification"</em> operations performed by extensions, such as <code>ProcessAnnotatedType.veto()</code>:</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre>DEBUG [Bootstrap] WELD-000148: ProcessAnnotatedType.veto() called by com.foo.MyExtension@50fed5b1 for [BackedAnnotatedType] public class com.foo.Foo</pre>
-                  </div>
-                  </div>
-                  <div class="admonitionblock tip">
-                  <table>
-                  <tr>
-                  <td class="icon">
-                  <div class="title">Tip</div>
-                  </td>
-                  <td class="content">
-                  If your application deploys successfully, you can use <a href="http://docs.jboss.org/weld/reference/latest/en-US/html/devmode.html#devtools">Development Tools</a> to inspect the runtime info (will be covered in one of the follow-up articles).
-                  </td>
-                  </tr>
-                  </table>
-                  </div>
-                  </div>
-                  </div>
-                  </div>
-                </div>
-                <hr>
-              </div>
               <div class="pagination-links"><a href="/news/page/10.html" class="previous-link">Previous</a> <a href="/news/" class="page-link">1</a> <a href="/news/page/2.html" class="page-link">2</a> <span class="skip">...</span><a href="/news/page/10.html" class="page-link">10</a> <span class="current-page">11</span> <a href="/news/page/12.html" class="page-link">12</a> <span class="skip">...</span><a href="/news/page/18.html" class="page-link">18</a> <a href="/news/page/19.html" class="page-link">19</a> <a href="/news/page/12.html" class="next-link">Next</a> </div>
               <hr>
               <div>
diff --git a/news/page/12.html b/news/page/12.html
index 87271a92..278c3caa 100644
--- a/news/page/12.html
+++ b/news/page/12.html
@@ -141,6 +141,205 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2016/10/01/tip1-logging/">Weld Tip 1 - Logging</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2016-10-1
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/tips">tips</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Martin Kouba
+                </div>
+                <p></p>
+                <div class="content">
+                  <div id="toc" class="toc">
+                  <div id="toctitle" class="title">Contents</div>
+                  <ul class="sectlevel1">
+                  <li><a href="#_motivation">Motivation</a></li>
+                  <li><a href="#under_the_hood">Under the hood</a></li>
+                  <li><a href="#filter">Set the log level and use categories to filter messages</a></li>
+                  <li><a href="#bootstrap">Monitoring bootstrap</a>
+                  <ul class="sectlevel2">
+                  <li><a href="#_registered_beans">Registered beans</a></li>
+                  <li><a href="#_actions_performed_by_extensions">Actions performed by extensions</a></li>
+                  </ul>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>This is the first article from a series of short articles covering some useful Weld features.
+                  In this article we talk about logging.
+                  The topics for the next articles include: <strong>DEVELOPMENT MODE</strong>, <strong>PERFORMANCE</strong>, <strong>NON-EE ENVIRONMENTS</strong> and <strong>TESTING</strong>.</p>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_motivation">Motivation</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>Logging is usually no fancy stuff.
+                  But very often it&#8217;s <em>the best thing to start with if problems arise</em>.
+                  Moreover, it&#8217;s the easiest form of debugging.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>In this article you will find:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p><a href="#under_the_hood">Under the hood</a> - how to control and configure the output</p>
+                  </li>
+                  <li>
+                  <p><a href="#filter">Set the log level and use categories to filter messages</a> - how to keep logs small and to the point</p>
+                  </li>
+                  <li>
+                  <p><a href="#bootstrap">Monitoring bootstrap</a> - registered beans, actions performed by extensions</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="under_the_hood">Under the hood</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>Weld is using <a href="https://developer.jboss.org/wiki/JBossLoggingTooling">JBoss Logging</a>.
+                  This is an abstraction layer wchich does not "write" any log messages at all.
+                  Instead, it effectively constructs a log message and then delegates to a back-end logging framework.
+                  The supported frameworks include <a href="https://developer.jboss.org/wiki/StandaloneJBossLogManager">jboss-logmanager</a>, <a href="http://logging.apache.org/log4j/2.x/">Log4j</a>, <a href="http://www.slf4j.org/">SLF4J</a> and JDK logging.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>So which logging framework is actually used to write the Weld messages?
+                  Well, it depends on the environment.
+                  In a <strong>Java EE container</strong> (e.g. WildFly) the logging configuration is under the direction of the container.
+                  You should follow the container-specific guides to change the configuration (see for example <a href="https://docs.jboss.org/author/display/WFLY10/Logging+Configuration">WildFly - Logging Configuration</a> and <a href="/documentation/#7">How do I enable debug logging for Weld in a specific container?</a>).</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>A web application deployed to a <strong>servlet container</strong> usually bundles a logging framework and possibly some configuration file.
+                  In this case, the configuration is in hands of the application developer.
+                  If no logging framework is bundled follow the container-specific guides to change the configuration (e.g. <a href="http://tomcat.apache.org/tomcat-8.0-doc/logging.html">Logging in Tomcat</a>).</p>
+                  </div>
+                  <div class="admonitionblock tip">
+                  <table>
+                  <tr>
+                  <td class="icon">
+                  <div class="title">Tip</div>
+                  </td>
+                  <td class="content">
+                  A system property <code>org.jboss.logging.provider</code> can be used to specify the logging framework directly. If not set, the JBoss Logging will attempt to find the "best match" on the classpath. See also <a href="https://github.com/jboss-logging/jboss-logging/blob/master/src/main/java/org/jboss/logging/LoggerProviders.java" target="_blank" rel="noopener">LoggerProviders</a>.
+                  </td>
+                  </tr>
+                  </table>
+                  </div>
+                  <div class="paragraph">
+                  <p>In <strong>Java SE</strong> the situation is very similar to servlet containers except the class loading is usually even less complicated (see also <a href="/documentation/#10"> How do I enable debug logging for Weld SE?</a>).</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="filter">Set the log level and use categories to filter messages</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>The default log level is usually <code>INFO</code>.
+                  Weld does not log that much information with this level.
+                  You will have to set the log level to <code>DEBUG</code> (or even <code>TRACE</code>) to see what&#8217;s going on in your application.
+                  If you set the level globally (for all frameworks and libraries), the log files will be bloated and it will be very hard to get some relevant info from there.
+                  If you set the level for Weld only (i.e. for <code>org.jboss.weld</code>), it should be better.
+                  Moreover, it&#8217;s possible to use categories to filter messages from a particular "domain".
+                  Weld log messages are grouped into several categories:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p><code>org.jboss.weld.Bootstrap</code></p>
+                  </li>
+                  <li>
+                  <p><code>org.jboss.weld.Validator</code></p>
+                  </li>
+                  <li>
+                  <p><code>org.jboss.weld.Bean</code></p>
+                  </li>
+                  <li>
+                  <p><code>org.jboss.weld.Context</code></p>
+                  </li>
+                  <li>
+                  <p><code>org.jboss.weld.El</code></p>
+                  </li>
+                  <li>
+                  <p>and others (see also <a href="https://github.com/weld/core/blob/master/impl/src/main/java/org/jboss/weld/logging/Category.java" target="_blank" rel="noopener">org.jboss.weld.logging.Category</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>So for example, if you&#8217;re only interested in log messages related to <strong>EL resolution</strong> set the log level for the <code>org.jboss.weld.El</code> category to <code>TRACE</code> (or level with corresponding priority).
+                  Another useful example is the check of <a href="http://docs.jboss.org/weld/reference/latest/en-US/html/configure.html#_weld_configuration" target="_blank" rel="noopener">Weld configuration</a>.
+                  Simply set the log level to <code>DEBUG</code> and filter the <code>org.jboss.weld.Configuration</code> category:</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre>DEBUG [Configuration] WELD-001907: Reading properties file: test.war/WEB-INF/classes/weld.properties&#x000A;    DEBUG [Configuration] WELD-001903: Configuration key RESOLUTION_CACHE_SIZE already set to 1 000 in a source with higher priority, value 500 from system properties is ignored&#x000A;    DEBUG [Configuration] WELD-001904: Unsupported configuration key found and ignored: com.foo.bar&#x000A;    DEBUG [Configuration] WELD-001902: Configuration initialized: {CONCURRENT_DEPLOYMENT=false, RESOLUTION_CACHE_SIZE=1000, RELAXED_CONSTRUCTION=true}</pre>
+                  </div>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="bootstrap">Monitoring bootstrap</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>CDI is designed to fail fast.
+                  An extensive validation is performed during application initialization in order to avoid malicious errors at runtime.
+                  Container usually also logs a lot of interesting info during bootstrap.
+                  Let&#8217;s try to set the log level to <strong>DEBUG</strong> for the <code>org.jboss.weld.Bootstrap</code> category and see what we get.</p>
+                  </div>
+                  <div class="sect2">
+                  <h3 id="_registered_beans">Registered beans</h3>
+                  <div class="paragraph">
+                  <p>As simple as it looks - Weld logs <em>all the beans</em> found in the application, e.g.:</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre>DEBUG [Bootstrap] WELD-000106: Bean: Managed Bean [class org.jboss.cdi.tck.tests.lookup.dependency.resolution.broken.unsatisfied.Vanilla] with qualifiers [@Any @Default]&#x000A;    DEBUG [Bootstrap] WELD-000106: Bean: Producer Method [String[]] with qualifiers [@BatchProperty @Any] declared as [[UnbackedAnnotatedMethod] @Produces @BatchProperty public org.jberet.creation.BatchBeanProducer.getStringArray(InjectionPoint)]</pre>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect2">
+                  <h3 id="_actions_performed_by_extensions">Actions performed by extensions</h3>
+                  <div class="paragraph">
+                  <p>There is no doubt that portable extensions are really powerful.
+                  They can change almost anything.
+                  That&#8217;s great for framework/libraries developers.
+                  On the other hand, this may cause problems when looking for a bug.
+                  There is an application class provided by a developer but what does the CDI container actually see?
+                  Well, it depends&#8230;&#8203; because portable extensions are allowed to redefine this.
+                  And that&#8217;s why Weld logs all the <em>"modification"</em> operations performed by extensions, such as <code>ProcessAnnotatedType.veto()</code>:</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre>DEBUG [Bootstrap] WELD-000148: ProcessAnnotatedType.veto() called by com.foo.MyExtension@50fed5b1 for [BackedAnnotatedType] public class com.foo.Foo</pre>
+                  </div>
+                  </div>
+                  <div class="admonitionblock tip">
+                  <table>
+                  <tr>
+                  <td class="icon">
+                  <div class="title">Tip</div>
+                  </td>
+                  <td class="content">
+                  If your application deploys successfully, you can use <a href="http://docs.jboss.org/weld/reference/latest/en-US/html/devmode.html#devtools">Development Tools</a> to inspect the runtime info (will be covered in one of the follow-up articles).
+                  </td>
+                  </tr>
+                  </table>
+                  </div>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2016/09/13/weld-240Final/">Weld 2.4.0.Final</a>
@@ -560,58 +759,6 @@ <h2 id="_wildfly_patch">WildFly Patch</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2016/06/21/update-on-weld-vertx/">Update on weld-vertx</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2016-6-21
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/vertx">vertx</a>
-                    ,
-                    <a href="/news/tags/integration">integration</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Martin Kouba
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>This is a follow-up on the article <a href="/news/2016/04/11/weld-meets-vertx/" target="_blank" rel="noopener">Weld meets Vert.x</a>.
-                  Weld team has just released the first alpha version of <a href="https://github.com/weld/weld-vertx" target="_blank" rel="noopener">weld-vertx</a> (artifacts are available in <a href="http://search.maven.org/#search%7Cga%7C1%7Cweld-vertx" target="_blank" rel="noopener">Maven Central</a>).
-                  Since the last time we talked about <code>weld-vertx</code> two new features were added.
-                  First, it&#8217;s possible to inject the relevant <code>io.vertx.core.Vertx</code> and <code>io.vertx.core.Context</code> instances direcly into beans.
-                  Also there is a new module called <code>weld-vertx-web</code> which extends functionality of <code>weld-vertx-core</code> and <code>io.vertx:vertx-web</code> and allows to register <code>Route</code> handlers discovered during container initialization.
-                  In other words, it&#8217;s possible to configure a <code>Route</code> in a declarative way:</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">import javax.inject.Inject;&#x000A;    &#x000A;    import org.jboss.weld.vertx.web.WebRoute;&#x000A;    &#x000A;    import io.vertx.core.Handler;&#x000A;    import io.vertx.ext.web.RoutingContext;&#x000A;    &#x000A;    // This annotation is used to configure a Route&#x000A;    @WebRoute("/hello")&#x000A;    public class HelloHandler implements Handler&lt;RoutingContext&gt; {&#x000A;    &#x000A;        @Inject&#x000A;        SayHelloService service;&#x000A;    &#x000A;        @Override&#x000A;        public void handle(RoutingContext ctx) {&#x000A;            ctx.response().setStatusCode(200).end(service.hello());&#x000A;        }&#x000A;    &#x000A;    }</code></pre>
-                  </div>
-                  </div>
-                  <div class="paragraph">
-                  <p>The registered handler instances are NOT real bean instances, i.e. they&#8217;re not managed by the CDI container (similarly as <a href="http://docs.jboss.org/cdi/spec/1.2/cdi-spec.html#javaee_components">Java EE components</a>).
-                  However, the <strong>dependency injection</strong> is supported.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>The central point of integration is the <code>org.jboss.weld.vertx.web.WeldWebVerticle</code>.
-                  This Verticle extends <code>org.jboss.weld.vertx.WeldVerticle</code> and provides the <code>WeldWebVerticle.registerRoutes(Router)</code> method:</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java"> class MyApp {&#x000A;    &#x000A;         public static void main(String[] args) {&#x000A;             final Vertx vertx = Vertx.vertx();&#x000A;             final WeldWebVerticle weldVerticle = new WeldWebVerticle();&#x000A;    &#x000A;             vertx.deployVerticle(weldVerticle, result -&gt; {&#x000A;    &#x000A;                 if (result.succeeded()) {&#x000A;                     // Configure the router after Weld bootstrap finished&#x000A;                     Router router = Router.router(vertx);&#x000A;                     router.route().handler(BodyHandler.create());&#x000A;                     weldVerticle.registerRoutes(router);&#x000A;                     vertx.createHttpServer().requestHandler(router::accept).listen(8080);&#x000A;                 }&#x000A;             });&#x000A;         }&#x000A;     }</code></pre>
-                  </div>
-                  </div>
-                  <div class="paragraph">
-                  <p>Give it a try and let us know if you have any idea how to extend the functionality of <code>weld-vertx</code>.
-                  Any feedback is appreciated!</p>
-                  </div>
-                </div>
-                <hr>
-              </div>
               <div class="pagination-links"><a href="/news/page/11.html" class="previous-link">Previous</a> <a href="/news/" class="page-link">1</a> <a href="/news/page/2.html" class="page-link">2</a> <span class="skip">...</span><a href="/news/page/11.html" class="page-link">11</a> <span class="current-page">12</span> <a href="/news/page/13.html" class="page-link">13</a> <span class="skip">...</span><a href="/news/page/18.html" class="page-link">18</a> <a href="/news/page/19.html" class="page-link">19</a> <a href="/news/page/13.html" class="next-link">Next</a> </div>
               <hr>
               <div>
diff --git a/news/page/13.html b/news/page/13.html
index 1be86104..e8af1364 100644
--- a/news/page/13.html
+++ b/news/page/13.html
@@ -141,6 +141,58 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2016/06/21/update-on-weld-vertx/">Update on weld-vertx</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2016-6-21
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/vertx">vertx</a>
+                    ,
+                    <a href="/news/tags/integration">integration</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Martin Kouba
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>This is a follow-up on the article <a href="/news/2016/04/11/weld-meets-vertx/" target="_blank" rel="noopener">Weld meets Vert.x</a>.
+                  Weld team has just released the first alpha version of <a href="https://github.com/weld/weld-vertx" target="_blank" rel="noopener">weld-vertx</a> (artifacts are available in <a href="http://search.maven.org/#search%7Cga%7C1%7Cweld-vertx" target="_blank" rel="noopener">Maven Central</a>).
+                  Since the last time we talked about <code>weld-vertx</code> two new features were added.
+                  First, it&#8217;s possible to inject the relevant <code>io.vertx.core.Vertx</code> and <code>io.vertx.core.Context</code> instances direcly into beans.
+                  Also there is a new module called <code>weld-vertx-web</code> which extends functionality of <code>weld-vertx-core</code> and <code>io.vertx:vertx-web</code> and allows to register <code>Route</code> handlers discovered during container initialization.
+                  In other words, it&#8217;s possible to configure a <code>Route</code> in a declarative way:</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">import javax.inject.Inject;&#x000A;    &#x000A;    import org.jboss.weld.vertx.web.WebRoute;&#x000A;    &#x000A;    import io.vertx.core.Handler;&#x000A;    import io.vertx.ext.web.RoutingContext;&#x000A;    &#x000A;    // This annotation is used to configure a Route&#x000A;    @WebRoute("/hello")&#x000A;    public class HelloHandler implements Handler&lt;RoutingContext&gt; {&#x000A;    &#x000A;        @Inject&#x000A;        SayHelloService service;&#x000A;    &#x000A;        @Override&#x000A;        public void handle(RoutingContext ctx) {&#x000A;            ctx.response().setStatusCode(200).end(service.hello());&#x000A;        }&#x000A;    &#x000A;    }</code></pre>
+                  </div>
+                  </div>
+                  <div class="paragraph">
+                  <p>The registered handler instances are NOT real bean instances, i.e. they&#8217;re not managed by the CDI container (similarly as <a href="http://docs.jboss.org/cdi/spec/1.2/cdi-spec.html#javaee_components">Java EE components</a>).
+                  However, the <strong>dependency injection</strong> is supported.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>The central point of integration is the <code>org.jboss.weld.vertx.web.WeldWebVerticle</code>.
+                  This Verticle extends <code>org.jboss.weld.vertx.WeldVerticle</code> and provides the <code>WeldWebVerticle.registerRoutes(Router)</code> method:</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java"> class MyApp {&#x000A;    &#x000A;         public static void main(String[] args) {&#x000A;             final Vertx vertx = Vertx.vertx();&#x000A;             final WeldWebVerticle weldVerticle = new WeldWebVerticle();&#x000A;    &#x000A;             vertx.deployVerticle(weldVerticle, result -&gt; {&#x000A;    &#x000A;                 if (result.succeeded()) {&#x000A;                     // Configure the router after Weld bootstrap finished&#x000A;                     Router router = Router.router(vertx);&#x000A;                     router.route().handler(BodyHandler.create());&#x000A;                     weldVerticle.registerRoutes(router);&#x000A;                     vertx.createHttpServer().requestHandler(router::accept).listen(8080);&#x000A;                 }&#x000A;             });&#x000A;         }&#x000A;     }</code></pre>
+                  </div>
+                  </div>
+                  <div class="paragraph">
+                  <p>Give it a try and let us know if you have any idea how to extend the functionality of <code>weld-vertx</code>.
+                  Any feedback is appreciated!</p>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2016/05/18/enhanced-instance/">Programmatic lookup improvements</a>
@@ -585,88 +637,6 @@ <h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2016/02/12/weld-233Final/">Weld 2.3.3.Final</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2016-2-12
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/release">release</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Martin Kouba
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>Weld 2.3.3.Final the next bug-fix version of the stable 2.3 branch has been released!
-                  See also <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12328954" target="_blank" rel="noopener">the release details</a>.
-                  Thanks to everyone involved in this release!
-                  Notable improvements:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>allow to proxy classes with non-static non-private final methods</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>this is a non-portable way to get around the <a href="http://docs.jboss.org/cdi/spec/1.2/cdi-spec.html#unproxyable" target="_blank" rel="noopener">CDI spec restrictions</a>, see also <a href="http://docs.jboss.org/weld/reference/2.3.3.Final/en-US/html/configure.html#_proxying_classes_with_final_methods" target="_blank" rel="noopener">Proxying classes with final methods</a> and <a href="https://issues.jboss.org/browse/CDI-527" target="_blank" rel="noopener">CDI-527</a></p>
-                  </li>
-                  <li>
-                  <p><strong>use with caution!</strong></p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>other enhancements and bug-fixes around proxies:</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>better support for DeltaSpike partial beans (<a href="https://issues.jboss.org/browse/WELD-2084" target="_blank" rel="noopener">WELD-2084</a>)</p>
-                  </li>
-                  <li>
-                  <p>better support for Camel CDI (<a href="https://issues.jboss.org/browse/WELD-2089" target="_blank" rel="noopener">WELD-2089</a>)</p>
-                  </li>
-                  <li>
-                  <p>better support for proxies with non public classes (<a href="https://issues.jboss.org/browse/WELD-2091" target="_blank" rel="noopener">WELD-2091</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Weld Probe has a slightly redesigned menu and a new Dashboard view with some basic stats</p>
-                  </li>
-                  <li>
-                  <p>the decorator validation was improved (<a href="https://issues.jboss.org/browse/WELD-2085" target="_blank" rel="noopener">WELD-2085</a>, <a href="https://issues.jboss.org/browse/WELD-1811" target="_blank" rel="noopener">WELD-1811</a>, <a href="https://issues.jboss.org/browse/WELD-2039" target="_blank" rel="noopener">WELD-2039</a>)</p>
-                  </li>
-                  <li>
-                  <p>minor SPI cleanup was performed  (<a href="https://issues.jboss.org/browse/WELD-2077" target="_blank" rel="noopener">WELD-2077</a>, <a href="https://issues.jboss.org/browse/WELD-2079" target="_blank" rel="noopener">WELD-2079</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_wildfly_patch">WildFly Patch</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>As usual, a <a href="http://download.jboss.org/weld/2.3.3.Final/wildfly-10.0.0.Final-weld-2.3.3.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly</a> is available. This time the target platform is <strong>WildFly 10.0.0.Final</strong>.  If you’re not familiar with patching WildFly, check <a href="http://blog.eisele.net/2015/02/playing-with-weld-probe-see-all-of-your.html" target="_blank" rel="noopener">Markus&#8217;s tutorial</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>&#91; <a href="http://docs.jboss.org/cdi/api/1.2/" target="_blank" rel="noopener">CDI 1.2 API</a> &#93;
-                  &#91; <a href="/download/">Download</a> &#93;
-                  &#91; <a href="http://docs.jboss.org/weld/reference/2.3.3.Final/en-US/html/" target="_blank" rel="noopener">Documentation</a> &#93;
-                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12328954" target="_blank" rel="noopener">Release notes</a> &#93;</p>
-                  </div>
-                  </div>
-                  </div>
-                </div>
-                <hr>
-              </div>
               <div class="pagination-links"><a href="/news/page/12.html" class="previous-link">Previous</a> <a href="/news/" class="page-link">1</a> <a href="/news/page/2.html" class="page-link">2</a> <span class="skip">...</span><a href="/news/page/12.html" class="page-link">12</a> <span class="current-page">13</span> <a href="/news/page/14.html" class="page-link">14</a> <span class="skip">...</span><a href="/news/page/18.html" class="page-link">18</a> <a href="/news/page/19.html" class="page-link">19</a> <a href="/news/page/14.html" class="next-link">Next</a> </div>
               <hr>
               <div>
diff --git a/news/page/14.html b/news/page/14.html
index 9af8c242..63b278b4 100644
--- a/news/page/14.html
+++ b/news/page/14.html
@@ -141,6 +141,88 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2016/02/12/weld-233Final/">Weld 2.3.3.Final</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2016-2-12
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/release">release</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Martin Kouba
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>Weld 2.3.3.Final the next bug-fix version of the stable 2.3 branch has been released!
+                  See also <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12328954" target="_blank" rel="noopener">the release details</a>.
+                  Thanks to everyone involved in this release!
+                  Notable improvements:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>allow to proxy classes with non-static non-private final methods</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>this is a non-portable way to get around the <a href="http://docs.jboss.org/cdi/spec/1.2/cdi-spec.html#unproxyable" target="_blank" rel="noopener">CDI spec restrictions</a>, see also <a href="http://docs.jboss.org/weld/reference/2.3.3.Final/en-US/html/configure.html#_proxying_classes_with_final_methods" target="_blank" rel="noopener">Proxying classes with final methods</a> and <a href="https://issues.jboss.org/browse/CDI-527" target="_blank" rel="noopener">CDI-527</a></p>
+                  </li>
+                  <li>
+                  <p><strong>use with caution!</strong></p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>other enhancements and bug-fixes around proxies:</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>better support for DeltaSpike partial beans (<a href="https://issues.jboss.org/browse/WELD-2084" target="_blank" rel="noopener">WELD-2084</a>)</p>
+                  </li>
+                  <li>
+                  <p>better support for Camel CDI (<a href="https://issues.jboss.org/browse/WELD-2089" target="_blank" rel="noopener">WELD-2089</a>)</p>
+                  </li>
+                  <li>
+                  <p>better support for proxies with non public classes (<a href="https://issues.jboss.org/browse/WELD-2091" target="_blank" rel="noopener">WELD-2091</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Weld Probe has a slightly redesigned menu and a new Dashboard view with some basic stats</p>
+                  </li>
+                  <li>
+                  <p>the decorator validation was improved (<a href="https://issues.jboss.org/browse/WELD-2085" target="_blank" rel="noopener">WELD-2085</a>, <a href="https://issues.jboss.org/browse/WELD-1811" target="_blank" rel="noopener">WELD-1811</a>, <a href="https://issues.jboss.org/browse/WELD-2039" target="_blank" rel="noopener">WELD-2039</a>)</p>
+                  </li>
+                  <li>
+                  <p>minor SPI cleanup was performed  (<a href="https://issues.jboss.org/browse/WELD-2077" target="_blank" rel="noopener">WELD-2077</a>, <a href="https://issues.jboss.org/browse/WELD-2079" target="_blank" rel="noopener">WELD-2079</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_wildfly_patch">WildFly Patch</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>As usual, a <a href="http://download.jboss.org/weld/2.3.3.Final/wildfly-10.0.0.Final-weld-2.3.3.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly</a> is available. This time the target platform is <strong>WildFly 10.0.0.Final</strong>.  If you’re not familiar with patching WildFly, check <a href="http://blog.eisele.net/2015/02/playing-with-weld-probe-see-all-of-your.html" target="_blank" rel="noopener">Markus&#8217;s tutorial</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="http://docs.jboss.org/cdi/api/1.2/" target="_blank" rel="noopener">CDI 1.2 API</a> &#93;
+                  &#91; <a href="/download/">Download</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/2.3.3.Final/en-US/html/" target="_blank" rel="noopener">Documentation</a> &#93;
+                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12328954" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2016/02/08/weld-se-synth-lifecycle-events/">Weld SE and synthetic container lifecycle event observers</a>
@@ -369,53 +451,6 @@ <h2 id="_wildfly_patch">WildFly Patch</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2015/11/25/arq-container-se-CR1/">Arquillian container SE 1.0.0.CR1 released!</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2015-11-25
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/arquillian">arquillian</a>
-                    ,
-                    <a href="/news/tags/testing">testing</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Tomas Remes
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>We are pleased to announce a new release of Arquillian container SE.
-                  If you are looking for a reliable way to test your application in Java SE then this is the right tool to try out!</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>This managed SE container launches new JVM process for each of your test archives.
-                  This standalone process with isolated classpath is also the main reason why we introduced such tool  (and also the difference e.g to <code>arquillian-weld-se-embedded</code>).</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>You can manage your classpath dependencies by using <a href="https://github.com/shrinkwrap/resolver">ShrinkWrap resolver</a>.
-                  Another option is to provide path to your directory containing your dependencies jars via container property.
-                  You can get ready your dependencies jars by using e.g Maven dependency plugin. Another options which you would expect as debugging, setting system properties or exporting deployment archive are also available.
-                  Test execution is managed by Arquillian JMX protocol.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Finally you can find some basic tests using Arquillian
-                  container SE in <a href="https://github.com/weld/core/tree/2.3/environments/se/tests">Weld SE tests</a> or in <a href="https://github.com/cdi-spec/cdi-tck/tree/master/impl/src/main/java/org/jboss/cdi/tck/tests/se">CDI TCK</a>.
-                  Feedback is more than welcomed and if you have any questions don&#8217;t hesitate to ask!</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="title">Maven Coordinates:</div>
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;dependency&gt;&#x000A;        &lt;groupId&gt;org.jboss.arquillian.container&lt;/groupId&gt;&#x000A;        &lt;artifactId&gt;container-se-managed&lt;/artifactId&gt;&#x000A;        &lt;version&gt;1.0.0.CR1&lt;/version&gt;&#x000A;    &lt;/dependency&gt;</code></pre>
-                  </div>
-                  </div>
-                </div>
-                <hr>
-              </div>
               <div class="pagination-links"><a href="/news/page/13.html" class="previous-link">Previous</a> <a href="/news/" class="page-link">1</a> <a href="/news/page/2.html" class="page-link">2</a> <span class="skip">...</span><a href="/news/page/13.html" class="page-link">13</a> <span class="current-page">14</span> <a href="/news/page/15.html" class="page-link">15</a> <span class="skip">...</span><a href="/news/page/18.html" class="page-link">18</a> <a href="/news/page/19.html" class="page-link">19</a> <a href="/news/page/15.html" class="next-link">Next</a> </div>
               <hr>
               <div>
diff --git a/news/page/15.html b/news/page/15.html
index 7c22aa7f..4735fd2d 100644
--- a/news/page/15.html
+++ b/news/page/15.html
@@ -141,6 +141,53 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2015/11/25/arq-container-se-CR1/">Arquillian container SE 1.0.0.CR1 released!</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2015-11-25
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/arquillian">arquillian</a>
+                    ,
+                    <a href="/news/tags/testing">testing</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Tomas Remes
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>We are pleased to announce a new release of Arquillian container SE.
+                  If you are looking for a reliable way to test your application in Java SE then this is the right tool to try out!</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>This managed SE container launches new JVM process for each of your test archives.
+                  This standalone process with isolated classpath is also the main reason why we introduced such tool  (and also the difference e.g to <code>arquillian-weld-se-embedded</code>).</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>You can manage your classpath dependencies by using <a href="https://github.com/shrinkwrap/resolver">ShrinkWrap resolver</a>.
+                  Another option is to provide path to your directory containing your dependencies jars via container property.
+                  You can get ready your dependencies jars by using e.g Maven dependency plugin. Another options which you would expect as debugging, setting system properties or exporting deployment archive are also available.
+                  Test execution is managed by Arquillian JMX protocol.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Finally you can find some basic tests using Arquillian
+                  container SE in <a href="https://github.com/weld/core/tree/2.3/environments/se/tests">Weld SE tests</a> or in <a href="https://github.com/cdi-spec/cdi-tck/tree/master/impl/src/main/java/org/jboss/cdi/tck/tests/se">CDI TCK</a>.
+                  Feedback is more than welcomed and if you have any questions don&#8217;t hesitate to ask!</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="title">Maven Coordinates:</div>
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;dependency&gt;&#x000A;        &lt;groupId&gt;org.jboss.arquillian.container&lt;/groupId&gt;&#x000A;        &lt;artifactId&gt;container-se-managed&lt;/artifactId&gt;&#x000A;        &lt;version&gt;1.0.0.CR1&lt;/version&gt;&#x000A;    &lt;/dependency&gt;</code></pre>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2015/11/10/weld-probe-jmx/">Weld development mode and JMX support</a>
@@ -471,43 +518,6 @@ <h2 id="_workaround">Workaround</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2015/09/08/weld-team-changes/">Weld team changes</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2015-9-8
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/team">team</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Jozef Hartinger
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>I am pleased to announce a couple of changes coming to the Weld team:</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>First of all, <a href="https://developer.jboss.org/people/mkouba">Martin</a> will be taking over leadership of the project.
-                  Martin has proven himself to be an excellent engineer over all the years and I am happy that I can leave the project in his hands.
-                  His primary task is going to be leading the project towards the Weld 3 milestone.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Secondly, I will be moving to work temporarily on a different project.
-                  I truly enjoyed working on Weld and with the CDI community.
-                  Now after almost 4 years on the project I was given an exciting opportunity which I decided to pursuit.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Last but not least, Matěj Novotný is joining the team as a quality engineer.
-                  He’s going to work on expanding our testsuites and making sure Weld releases do not break anything :-)</p>
-                  </div>
-                </div>
-                <hr>
-              </div>
               <div class="pagination-links"><a href="/news/page/14.html" class="previous-link">Previous</a> <a href="/news/" class="page-link">1</a> <a href="/news/page/2.html" class="page-link">2</a> <span class="skip">...</span><a href="/news/page/14.html" class="page-link">14</a> <span class="current-page">15</span> <a href="/news/page/16.html" class="page-link">16</a> <span class="skip">...</span><a href="/news/page/18.html" class="page-link">18</a> <a href="/news/page/19.html" class="page-link">19</a> <a href="/news/page/16.html" class="next-link">Next</a> </div>
               <hr>
               <div>
diff --git a/news/page/16.html b/news/page/16.html
index a22ee035..1d00f658 100644
--- a/news/page/16.html
+++ b/news/page/16.html
@@ -141,6 +141,43 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2015/09/08/weld-team-changes/">Weld team changes</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2015-9-8
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/team">team</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Jozef Hartinger
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>I am pleased to announce a couple of changes coming to the Weld team:</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>First of all, <a href="https://developer.jboss.org/people/mkouba">Martin</a> will be taking over leadership of the project.
+                  Martin has proven himself to be an excellent engineer over all the years and I am happy that I can leave the project in his hands.
+                  His primary task is going to be leading the project towards the Weld 3 milestone.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Secondly, I will be moving to work temporarily on a different project.
+                  I truly enjoyed working on Weld and with the CDI community.
+                  Now after almost 4 years on the project I was given an exciting opportunity which I decided to pursuit.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Last but not least, Matěj Novotný is joining the team as a quality engineer.
+                  He’s going to work on expanding our testsuites and making sure Weld releases do not break anything :-)</p>
+                  </div>
+                </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>
@@ -756,295 +793,6 @@ <h2 id="_next">Next</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2014/12/10/an-update-on-weld-3/">An update on Weld 3</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2014-12-10
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/cdi2">cdi2</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Jozef Hartinger
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>Today we are releasing the third Alpha release of Weld 3. These Alpha releases serve
-                  as prototypes of changes currently being discussed by the CDI expert group for
-                  the upcoming CDI 2.0.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>The Alpha releases are not suitable for production use as the new API and functionality
-                  are still subject to change. We are releasing them to allow the community to test-drive
-                  the changes early in the development cycle. We want to shorten the feedback loop and
-                  identify possible glitches as soon as possible.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Let’s just quickly review what has been available since Alpha1:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>declarative ordering of observer methods using <code>@Priority</code></p>
-                  </li>
-                  <li>
-                  <p>ability for an extension to veto and modify an observer method</p>
-                  </li>
-                  <li>
-                  <p>support for Java 8 repeatable annotations as qualifiers and interceptor bindings</p>
-                  </li>
-                  <li>
-                  <p>enhanced <code>AnnotatedType</code> API</p>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>For more details and examples of these features see my
-                  <a href="http://weld.cdi-spec.org/news/2014/10/02/weld-300Alpha1/">previous blog post</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>On top of this, we’re now adding the <strong>following new features and enhancements</strong>:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>asynchronous events</p>
-                  </li>
-                  <li>
-                  <p>simplified configuration of Weld-specific properties</p>
-                  </li>
-                  <li>
-                  <p>Guava is no longer used internally</p>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_asynchronous_events">Asynchronous events</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>Since its first version CDI has provided events as a facility for component interaction.
-                  Events enable loose coupling while preserving type safety.
-                  So far, CDI has supported synchronous delivery of events - the calling thread blocks
-                  until invocations of all associated observer methods complete. An alternative to
-                  this are transactional observer methods which are called asynchronously at the end
-                  of a transaction.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>For the upcoming CDI 2.0 specification one of the hot topics is enhancement of the
-                  events facility. The expert group is
-                  <a href="https://docs.google.com/document/d/1pDO7gru6YuEyTDdK3XBozvXZYucT9uC7McZMffSZun4/edit?usp=sharing">considering adding fully asynchronous event dispatching mechanism</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>A working prototype of this is available in Weld 3.0.0.Alpha3. The current proposal
-                  adds a method called <code>fireAsync</code> to the existing <code>Event</code> interface.</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@Inject&#x000A;    private ExperimentalEvent&lt;Configuration&gt; event;&#x000A;    …&#x000A;    event.fireAsync(new Configuration());</code></pre>
-                  </div>
-                  </div>
-                  <div class="paragraph">
-                  <p>The call to <code>event.fireAsync()</code> returns immediately. The event is delivered to
-                  corresponding observers in a dedicated thread pool that can be configured.</p>
-                  </div>
-                  <div class="sect2">
-                  <h3 id="_what_about_thread_safety">What about thread-safety?</h3>
-                  <div class="paragraph">
-                  <p>There are two common usage pattens for events. In the first one an immutable event
-                  object is used. An alternative is to use mutable events. A mutable event allows
-                  observers to participate on the result which is later used by the component that
-                  fired the event. An example of this would be the
-                  <a href="https://docs.oracle.com/javaee/6/api/javax/enterprise/inject/spi/ProcessAnnotatedType.html">ProcessAnnotatedType&lt;T&gt;</a>
-                  event used by CDI extensions. When events are fired synchronously, both
-                  approaches work fine but how does this work when we switch to async?</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Nothing changes actually. No matter if the event object is immutable or not, you
-                  do not have to worry about thread-safety of the event object. The current implementation
-                  comes with the guarantee that event object is safely published which means that
-                  an observer method observes the event in the state in which:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>it was left by an observer executing before the given observer, or</p>
-                  </li>
-                  <li>
-                  <p>the initial state of the event if the given observer is the first one</p>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>Furthermore, the state is consistent throughout the execution of an observer method
-                  which means that we guarantee safe publication and prevent races for you. The only
-                  thing that should be avoided is modifying the state of the event object outside of
-                  an observer method. This behavior matches the
-                  <a href="https://docs.google.com/document/d/1lFtgLm6hY-uECdA1r0Sfimq6vkVYThoUZsevPUaSP0E/edit?usp=sharing">option 4.1.1.1 in the current spec proposal</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Update: new <a href="https://docs.google.com/document/d/1pDO7gru6YuEyTDdK3XBozvXZYucT9uC7McZMffSZun4/edit?usp=sharing">link for a planning document</a></p>
-                  </div>
-                  <div class="paragraph">
-                  <p>In addition, if observer methods are ordered (another new feature proposed for CDI 2.0)
-                  we preserve the ordering (as in such situation the observers are ordered for a reason!)
-                  and invoke observers in the given order.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Last but not least, if an observer is transactional, we again preserve this and
-                  invoke the observer method in the corresponding transaction phase.</p>
-                  </div>
-                  </div>
-                  <div class="sect2">
-                  <h3 id="_how_do_i_know_when_event_delivery_finishes_and_what_about_exceptions">How do I know when event delivery finishes and what about exceptions?</h3>
-                  <div class="paragraph">
-                  <p>In the current prototype we’re reusing the
-                  <a href="https://docs.oracle.com/javase/8/docs/api/java/util/concurrent/CompletionStage.html">CompletionStage</a>
-                  API, introduced in Java 8, which allows actions (callbacks) to be bound to the completion of the
-                  asynchronous delivery process. This is what it looks like:</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">event.fireAsync(new Configuration()).thenAccept(config -&gt; master.compute(config));</code></pre>
-                  </div>
-                  </div>
-                  <div class="paragraph">
-                  <p>This piece of code starts with asynchronously firing a mutable configuration object
-                  allowing loosely-coupled observers to alter the configuration of a computation.
-                  Once all observers finish, computation is initiated based on the resulting configuration.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>If an exception occurs this can be dealt with also, either by falling back to a default value</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">event.fireAsync(new Configuration())&#x000A;        .exceptionally(throwable -&gt; DEFAULT_CONFIGURATION)&#x000A;        .thenAccept((config) -&gt; master.compute(config));</code></pre>
-                  </div>
-                  </div>
-                  <div class="paragraph">
-                  <p>or by executing arbitrary code:</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">event.fireAsync(new Configuration()).whenComplete((config, throwable) -&gt; {&#x000A;        if (throwable != null) {&#x000A;            System.err.println("Oops. Failed because of " + throwable.getMessage());&#x000A;        } else {&#x000A;            master.compute(config);&#x000A;        }&#x000A;    });</code></pre>
-                  </div>
-                  </div>
-                  <div class="paragraph">
-                  <p><code>CompletionStage</code> allows much more. If you are unfamiliar with the API see the
-                  <a href="https://docs.oracle.com/javase/8/docs/api/java/util/concurrent/CompletionStage.html">Javadoc</a>
-                  page for more information.</p>
-                  </div>
-                  </div>
-                  <div class="sect2">
-                  <h3 id="_how_do_i_try_this_myself">How do I try this myself?</h3>
-                  <div class="paragraph">
-                  <p>It’s easy and multiple options are available. First of them is to use Weld in a
-                  <strong>standalone application</strong>.</p>
-                  </div>
-                  <div class="olist arabic">
-                  <ol class="arabic">
-                  <li>
-                  <p>Create a new Java SE application.</p>
-                  </li>
-                  <li>
-                  <p>Add dependency on Weld</p>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">&lt;dependency&gt;&#x000A;        &lt;groupId&gt;org.jboss.weld.se&lt;/groupId&gt;&#x000A;        &lt;artifactId&gt;weld-se-core&lt;/artifactId&gt;&#x000A;        &lt;version&gt;3.0.0.Alpha3&lt;/version&gt;&#x000A;    &lt;/dependency&gt;</code></pre>
-                  </div>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Create an empty <code>beans.xml</code> file, e.g.</p>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-shell hljs" data-lang="shell">mkdir src/main/resources/META-INF&#x000A;    touch src/main/resources/META-INF/beans.xml</code></pre>
-                  </div>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Launch Weld and fire an event asynchronously</p>
-                  <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;        WeldContainer weld = new Weld().initialize();&#x000A;        Event&lt;String&gt; evnt = weld.event().select(String.class);&#x000A;        ExperimentalEvent&lt;String&gt; event = (ExperimentalEvent&lt;String&gt;) evnt;&#x000A;    &#x000A;        event.fireAsync("message");&#x000A;    }</code></pre>
-                  </div>
-                  </div>
-                  </li>
-                  </ol>
-                  </div>
-                  <div class="sect3">
-                  <h4 id="_wildfly">WildFly</h4>
-                  <div class="paragraph">
-                  <p>Alternatively, a patch is available for WildFly that upgrades Weld within an existing WildFly instance. See the
-                  <a href="http://sourceforge.net/projects/jboss/files/Weld/3.0.0.Alpha3">download page</a>
-                  for more details.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Note that these new prototyped APIs are not part of the CDI API yet. Instead, they are currently located
-                  in
-                  <a href="http://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22org.jboss.weld%22%20AND%20a%3A%22weld-api%22">Weld API</a>
-                  in a package named
-                  <a href="http://docs.jboss.org/weld/javadoc/3.0/weld-api/org/jboss/weld/experimental/package-frame.html">org.jboss.weld.experimental</a></p>
-                  </div>
-                  <div class="paragraph">
-                  <p>All these altered APIs have the <code>Experimental</code> prefix (that&#8217;s why we are using <code>ExperimentalEvent</code> in the examples)</p>
-                  </div>
-                  <div class="paragraph">
-                  <p><strong>We would appreciate your feedback!</strong> Feel free to use
-                  <a href="https://community.jboss.org/en/weld?view=discussions">Weld forums</a>
-                  or the
-                  <a href="https://lists.jboss.org/mailman/listinfo/cdi-dev">cdi-dev mailing list</a>
-                  for this purpose.</p>
-                  </div>
-                  </div>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_whats_next">What’s next?</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>We are going to continue releasing early prototypes of features currently proposed for
-                  CDI 2.0. The plan is to release a new Alpha version every 3 weeks. There are several
-                  areas we want to focus on:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>simplifying how extensions register beans and observers</p>
-                  </li>
-                  <li>
-                  <p>monitoring and debugging of CDI applications</p>
-                  </li>
-                  <li>
-                  <p>experimenting with full interception (intercepting even calls within a given component)</p>
-                  </li>
-                  <li>
-                  <p>splitting the codebase into a “light” and “full” version (to support proposed <strong>CDI light</strong> version)</p>
-                  </li>
-                  <li>
-                  <p>bootstrap API for SE environment</p>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>&#91; <a href="http://docs.jboss.org/weld/javadoc/3.0/weld-api/org/jboss/weld/experimental/package-frame.html">Experimental API documentation</a> &#93;
-                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12325836">Release notes</a> &#93;
-                  &#91; <a href="https://sourceforge.net/projects/jboss/files/Weld/3.0.0.Alpha3">Distribution</a> &#93;
-                  &#91; Patch for Wildfly
-                  (<a href="http://sourceforge.net/projects/jboss/files/Weld/3.0.0.Alpha3/wildfly-8.2.0.Final-weld-3.0.0.Alpha3-patch.zip/download">8.2</a>,
-                  <a href="http://sourceforge.net/projects/jboss/files/Weld/3.0.0.Alpha3/wildfly-9.0.0.Alpha1-weld-3.0.0.Alpha3-patch.zip/download">9 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>
               <hr>
               <div>
diff --git a/news/page/17.html b/news/page/17.html
index ca8c8256..0bbba1a6 100644
--- a/news/page/17.html
+++ b/news/page/17.html
@@ -141,6 +141,295 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2014/12/10/an-update-on-weld-3/">An update on Weld 3</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2014-12-10
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/cdi2">cdi2</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Jozef Hartinger
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>Today we are releasing the third Alpha release of Weld 3. These Alpha releases serve
+                  as prototypes of changes currently being discussed by the CDI expert group for
+                  the upcoming CDI 2.0.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>The Alpha releases are not suitable for production use as the new API and functionality
+                  are still subject to change. We are releasing them to allow the community to test-drive
+                  the changes early in the development cycle. We want to shorten the feedback loop and
+                  identify possible glitches as soon as possible.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Let’s just quickly review what has been available since Alpha1:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>declarative ordering of observer methods using <code>@Priority</code></p>
+                  </li>
+                  <li>
+                  <p>ability for an extension to veto and modify an observer method</p>
+                  </li>
+                  <li>
+                  <p>support for Java 8 repeatable annotations as qualifiers and interceptor bindings</p>
+                  </li>
+                  <li>
+                  <p>enhanced <code>AnnotatedType</code> API</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>For more details and examples of these features see my
+                  <a href="http://weld.cdi-spec.org/news/2014/10/02/weld-300Alpha1/">previous blog post</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>On top of this, we’re now adding the <strong>following new features and enhancements</strong>:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>asynchronous events</p>
+                  </li>
+                  <li>
+                  <p>simplified configuration of Weld-specific properties</p>
+                  </li>
+                  <li>
+                  <p>Guava is no longer used internally</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_asynchronous_events">Asynchronous events</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>Since its first version CDI has provided events as a facility for component interaction.
+                  Events enable loose coupling while preserving type safety.
+                  So far, CDI has supported synchronous delivery of events - the calling thread blocks
+                  until invocations of all associated observer methods complete. An alternative to
+                  this are transactional observer methods which are called asynchronously at the end
+                  of a transaction.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>For the upcoming CDI 2.0 specification one of the hot topics is enhancement of the
+                  events facility. The expert group is
+                  <a href="https://docs.google.com/document/d/1pDO7gru6YuEyTDdK3XBozvXZYucT9uC7McZMffSZun4/edit?usp=sharing">considering adding fully asynchronous event dispatching mechanism</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>A working prototype of this is available in Weld 3.0.0.Alpha3. The current proposal
+                  adds a method called <code>fireAsync</code> to the existing <code>Event</code> interface.</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@Inject&#x000A;    private ExperimentalEvent&lt;Configuration&gt; event;&#x000A;    …&#x000A;    event.fireAsync(new Configuration());</code></pre>
+                  </div>
+                  </div>
+                  <div class="paragraph">
+                  <p>The call to <code>event.fireAsync()</code> returns immediately. The event is delivered to
+                  corresponding observers in a dedicated thread pool that can be configured.</p>
+                  </div>
+                  <div class="sect2">
+                  <h3 id="_what_about_thread_safety">What about thread-safety?</h3>
+                  <div class="paragraph">
+                  <p>There are two common usage pattens for events. In the first one an immutable event
+                  object is used. An alternative is to use mutable events. A mutable event allows
+                  observers to participate on the result which is later used by the component that
+                  fired the event. An example of this would be the
+                  <a href="https://docs.oracle.com/javaee/6/api/javax/enterprise/inject/spi/ProcessAnnotatedType.html">ProcessAnnotatedType&lt;T&gt;</a>
+                  event used by CDI extensions. When events are fired synchronously, both
+                  approaches work fine but how does this work when we switch to async?</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Nothing changes actually. No matter if the event object is immutable or not, you
+                  do not have to worry about thread-safety of the event object. The current implementation
+                  comes with the guarantee that event object is safely published which means that
+                  an observer method observes the event in the state in which:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>it was left by an observer executing before the given observer, or</p>
+                  </li>
+                  <li>
+                  <p>the initial state of the event if the given observer is the first one</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>Furthermore, the state is consistent throughout the execution of an observer method
+                  which means that we guarantee safe publication and prevent races for you. The only
+                  thing that should be avoided is modifying the state of the event object outside of
+                  an observer method. This behavior matches the
+                  <a href="https://docs.google.com/document/d/1lFtgLm6hY-uECdA1r0Sfimq6vkVYThoUZsevPUaSP0E/edit?usp=sharing">option 4.1.1.1 in the current spec proposal</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Update: new <a href="https://docs.google.com/document/d/1pDO7gru6YuEyTDdK3XBozvXZYucT9uC7McZMffSZun4/edit?usp=sharing">link for a planning document</a></p>
+                  </div>
+                  <div class="paragraph">
+                  <p>In addition, if observer methods are ordered (another new feature proposed for CDI 2.0)
+                  we preserve the ordering (as in such situation the observers are ordered for a reason!)
+                  and invoke observers in the given order.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Last but not least, if an observer is transactional, we again preserve this and
+                  invoke the observer method in the corresponding transaction phase.</p>
+                  </div>
+                  </div>
+                  <div class="sect2">
+                  <h3 id="_how_do_i_know_when_event_delivery_finishes_and_what_about_exceptions">How do I know when event delivery finishes and what about exceptions?</h3>
+                  <div class="paragraph">
+                  <p>In the current prototype we’re reusing the
+                  <a href="https://docs.oracle.com/javase/8/docs/api/java/util/concurrent/CompletionStage.html">CompletionStage</a>
+                  API, introduced in Java 8, which allows actions (callbacks) to be bound to the completion of the
+                  asynchronous delivery process. This is what it looks like:</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">event.fireAsync(new Configuration()).thenAccept(config -&gt; master.compute(config));</code></pre>
+                  </div>
+                  </div>
+                  <div class="paragraph">
+                  <p>This piece of code starts with asynchronously firing a mutable configuration object
+                  allowing loosely-coupled observers to alter the configuration of a computation.
+                  Once all observers finish, computation is initiated based on the resulting configuration.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>If an exception occurs this can be dealt with also, either by falling back to a default value</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">event.fireAsync(new Configuration())&#x000A;        .exceptionally(throwable -&gt; DEFAULT_CONFIGURATION)&#x000A;        .thenAccept((config) -&gt; master.compute(config));</code></pre>
+                  </div>
+                  </div>
+                  <div class="paragraph">
+                  <p>or by executing arbitrary code:</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">event.fireAsync(new Configuration()).whenComplete((config, throwable) -&gt; {&#x000A;        if (throwable != null) {&#x000A;            System.err.println("Oops. Failed because of " + throwable.getMessage());&#x000A;        } else {&#x000A;            master.compute(config);&#x000A;        }&#x000A;    });</code></pre>
+                  </div>
+                  </div>
+                  <div class="paragraph">
+                  <p><code>CompletionStage</code> allows much more. If you are unfamiliar with the API see the
+                  <a href="https://docs.oracle.com/javase/8/docs/api/java/util/concurrent/CompletionStage.html">Javadoc</a>
+                  page for more information.</p>
+                  </div>
+                  </div>
+                  <div class="sect2">
+                  <h3 id="_how_do_i_try_this_myself">How do I try this myself?</h3>
+                  <div class="paragraph">
+                  <p>It’s easy and multiple options are available. First of them is to use Weld in a
+                  <strong>standalone application</strong>.</p>
+                  </div>
+                  <div class="olist arabic">
+                  <ol class="arabic">
+                  <li>
+                  <p>Create a new Java SE application.</p>
+                  </li>
+                  <li>
+                  <p>Add dependency on Weld</p>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">&lt;dependency&gt;&#x000A;        &lt;groupId&gt;org.jboss.weld.se&lt;/groupId&gt;&#x000A;        &lt;artifactId&gt;weld-se-core&lt;/artifactId&gt;&#x000A;        &lt;version&gt;3.0.0.Alpha3&lt;/version&gt;&#x000A;    &lt;/dependency&gt;</code></pre>
+                  </div>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Create an empty <code>beans.xml</code> file, e.g.</p>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-shell hljs" data-lang="shell">mkdir src/main/resources/META-INF&#x000A;    touch src/main/resources/META-INF/beans.xml</code></pre>
+                  </div>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Launch Weld and fire an event asynchronously</p>
+                  <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;        WeldContainer weld = new Weld().initialize();&#x000A;        Event&lt;String&gt; evnt = weld.event().select(String.class);&#x000A;        ExperimentalEvent&lt;String&gt; event = (ExperimentalEvent&lt;String&gt;) evnt;&#x000A;    &#x000A;        event.fireAsync("message");&#x000A;    }</code></pre>
+                  </div>
+                  </div>
+                  </li>
+                  </ol>
+                  </div>
+                  <div class="sect3">
+                  <h4 id="_wildfly">WildFly</h4>
+                  <div class="paragraph">
+                  <p>Alternatively, a patch is available for WildFly that upgrades Weld within an existing WildFly instance. See the
+                  <a href="http://sourceforge.net/projects/jboss/files/Weld/3.0.0.Alpha3">download page</a>
+                  for more details.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Note that these new prototyped APIs are not part of the CDI API yet. Instead, they are currently located
+                  in
+                  <a href="http://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22org.jboss.weld%22%20AND%20a%3A%22weld-api%22">Weld API</a>
+                  in a package named
+                  <a href="http://docs.jboss.org/weld/javadoc/3.0/weld-api/org/jboss/weld/experimental/package-frame.html">org.jboss.weld.experimental</a></p>
+                  </div>
+                  <div class="paragraph">
+                  <p>All these altered APIs have the <code>Experimental</code> prefix (that&#8217;s why we are using <code>ExperimentalEvent</code> in the examples)</p>
+                  </div>
+                  <div class="paragraph">
+                  <p><strong>We would appreciate your feedback!</strong> Feel free to use
+                  <a href="https://community.jboss.org/en/weld?view=discussions">Weld forums</a>
+                  or the
+                  <a href="https://lists.jboss.org/mailman/listinfo/cdi-dev">cdi-dev mailing list</a>
+                  for this purpose.</p>
+                  </div>
+                  </div>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_whats_next">What’s next?</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>We are going to continue releasing early prototypes of features currently proposed for
+                  CDI 2.0. The plan is to release a new Alpha version every 3 weeks. There are several
+                  areas we want to focus on:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>simplifying how extensions register beans and observers</p>
+                  </li>
+                  <li>
+                  <p>monitoring and debugging of CDI applications</p>
+                  </li>
+                  <li>
+                  <p>experimenting with full interception (intercepting even calls within a given component)</p>
+                  </li>
+                  <li>
+                  <p>splitting the codebase into a “light” and “full” version (to support proposed <strong>CDI light</strong> version)</p>
+                  </li>
+                  <li>
+                  <p>bootstrap API for SE environment</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="http://docs.jboss.org/weld/javadoc/3.0/weld-api/org/jboss/weld/experimental/package-frame.html">Experimental API documentation</a> &#93;
+                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12325836">Release notes</a> &#93;
+                  &#91; <a href="https://sourceforge.net/projects/jboss/files/Weld/3.0.0.Alpha3">Distribution</a> &#93;
+                  &#91; Patch for Wildfly
+                  (<a href="http://sourceforge.net/projects/jboss/files/Weld/3.0.0.Alpha3/wildfly-8.2.0.Final-weld-3.0.0.Alpha3-patch.zip/download">8.2</a>,
+                  <a href="http://sourceforge.net/projects/jboss/files/Weld/3.0.0.Alpha3/wildfly-9.0.0.Alpha1-weld-3.0.0.Alpha3-patch.zip/download">9 Alpha</a>)
+                  &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2014/10/02/weld-300Alpha1/">Weld 3.0.0.Alpha1 released!</a>
@@ -619,49 +908,6 @@ <h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2014/01/14/weld-212-final/">Three new Weld releases</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2014-1-14
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Jozef Hartinger
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>This week we are releasing three new builds of Weld. Firstly, <strong>Weld 2.1.2.Final</strong> was released. This is a bug-fixing release with 11 issues resolved. Most notably:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>The conversation context is now initialized lazily. This resolves the problem with custom character encoding that many of you run into. See the <a href="http://docs.jboss.org/weld/reference/2.1.2.Final/en-US/html/scopescontexts.html#d0e2009">reference documentation</a> for details.</p>
-                  </li>
-                  <li>
-                  <p>Weld now runs fine on JDK8</p>
-                  </li>
-                  <li>
-                  <p>Jetty 9.1 is now supported by weld-servlet</p>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>In addition, <strong>Weld 1.1.17.Final</strong> (CDI 1.0) was released with several bug fixes.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Last but not least, there was a <a href="https://java.net/jira/browse/GLASSFISH-20928">memory leak identified in GlassFish</a> caused partly by GlassFish and partly by Weld. GlassFish still uses Weld 2.0. Although we do not maintain the 2.0 branch any longer and advice everyone to upgrade to Weld 2.1, the memory leak may be a problem for GlassFish users that are not able to upgrade to Weld 2.1 themselves. Therefore, we decided to do one more 2.0 release where this problem is fixed so that GlassFish users stuck on Weld 2.0 have an easy fix. Enjoy <strong>Weld 2.0.5.Final!</strong></p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Now, our focus shifts completely towards Weld 2.2 where performance optimization and lowering memory consumption are the main goals. Expect first Alpha of Weld 2.2 by the end of January.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>If you are interested in Weld make sure you check our <a href="http://weld.cdi-spec.org/community/">community page</a> or the <a href="https://issues.jboss.org/issues/?filter=12320398">list of open issues awaiting contribution</a>.</p>
-                  </div>
-                </div>
-                <hr>
-              </div>
               <div class="pagination-links"><a href="/news/page/16.html" class="previous-link">Previous</a> <a href="/news/" class="page-link">1</a> <a href="/news/page/2.html" class="page-link">2</a> <span class="skip">...</span><a href="/news/page/16.html" class="page-link">16</a> <span class="current-page">17</span> <a href="/news/page/18.html" class="page-link">18</a> <a href="/news/page/19.html" class="page-link">19</a> <a href="/news/page/18.html" class="next-link">Next</a> </div>
               <hr>
               <div>
diff --git a/news/page/18.html b/news/page/18.html
index c27297d0..f4cccff1 100644
--- a/news/page/18.html
+++ b/news/page/18.html
@@ -141,6 +141,49 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2014/01/14/weld-212-final/">Three new Weld releases</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2014-1-14
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Jozef Hartinger
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>This week we are releasing three new builds of Weld. Firstly, <strong>Weld 2.1.2.Final</strong> was released. This is a bug-fixing release with 11 issues resolved. Most notably:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>The conversation context is now initialized lazily. This resolves the problem with custom character encoding that many of you run into. See the <a href="http://docs.jboss.org/weld/reference/2.1.2.Final/en-US/html/scopescontexts.html#d0e2009">reference documentation</a> for details.</p>
+                  </li>
+                  <li>
+                  <p>Weld now runs fine on JDK8</p>
+                  </li>
+                  <li>
+                  <p>Jetty 9.1 is now supported by weld-servlet</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>In addition, <strong>Weld 1.1.17.Final</strong> (CDI 1.0) was released with several bug fixes.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Last but not least, there was a <a href="https://java.net/jira/browse/GLASSFISH-20928">memory leak identified in GlassFish</a> caused partly by GlassFish and partly by Weld. GlassFish still uses Weld 2.0. Although we do not maintain the 2.0 branch any longer and advice everyone to upgrade to Weld 2.1, the memory leak may be a problem for GlassFish users that are not able to upgrade to Weld 2.1 themselves. Therefore, we decided to do one more 2.0 release where this problem is fixed so that GlassFish users stuck on Weld 2.0 have an easy fix. Enjoy <strong>Weld 2.0.5.Final!</strong></p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Now, our focus shifts completely towards Weld 2.2 where performance optimization and lowering memory consumption are the main goals. Expect first Alpha of Weld 2.2 by the end of January.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>If you are interested in Weld make sure you check our <a href="http://weld.cdi-spec.org/community/">community page</a> or the <a href="https://issues.jboss.org/issues/?filter=12320398">list of open issues awaiting contribution</a>.</p>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2013/12/11/weld-211-final/">Weld 2.1.1.Final</a>
@@ -313,33 +356,6 @@ <h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2013/06/06/weld-201-final/">Weld 2.0.1.Final</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2013-6-6
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Jozef Hartinger
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>Weld 2.0.1.Final has been released. This is mainly a bug-fixing release with 20 issues fixed since the previous one. For details, see the <a href="/https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12321507:">release notes</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Our focus is now shifting towards WildFly and its Weld integration in order to provide a CDI 1.1 compliant container. For details about CDI 1.1, see <a href="http://in.relation.to/Bloggers/CDI11Available">Pete&#8217;s blog post</a>. Furthermore, we plan frequent releases of Weld to continue, so expect another release in early July at the latest!</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>&#91; <a href="https://sourceforge.net/projects/jboss/files/Weld/2.0.1.Final">Distribution</a> &#93;
-                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12321507">Release notes</a> &#93;
-                  &#91; <a href="http://docs.jboss.org/weld/reference/2.0.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>
               <hr>
               <div>
diff --git a/news/page/19.html b/news/page/19.html
index 89f2e2ca..0ca6cfb0 100644
--- a/news/page/19.html
+++ b/news/page/19.html
@@ -141,6 +141,33 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2013/06/06/weld-201-final/">Weld 2.0.1.Final</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2013-6-6
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Jozef Hartinger
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>Weld 2.0.1.Final has been released. This is mainly a bug-fixing release with 20 issues fixed since the previous one. For details, see the <a href="/https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12321507:">release notes</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Our focus is now shifting towards WildFly and its Weld integration in order to provide a CDI 1.1 compliant container. For details about CDI 1.1, see <a href="http://in.relation.to/Bloggers/CDI11Available">Pete&#8217;s blog post</a>. Furthermore, we plan frequent releases of Weld to continue, so expect another release in early July at the latest!</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="https://sourceforge.net/projects/jboss/files/Weld/2.0.1.Final">Distribution</a> &#93;
+                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12321507">Release notes</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/2.0.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/04/25/weld-200-final/">Weld 2.0.0.Final released</a>
diff --git a/news/page/2.html b/news/page/2.html
index bdba9b9b..8fd49199 100644
--- a/news/page/2.html
+++ b/news/page/2.html
@@ -141,6 +141,41 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2023/08/09/weld-511SP2/">Weld 5.1.1.SP2</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2023-8-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>Another bug-smashing release has landed in Maven Central and this time it&#8217;s Weld 5.1.1.SP2.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>This is a very small but important change which addresses possible memory leak scenario (<a href="https://issues.redhat.com/browse/WELD-2750">WELD-2750</a>).
+                  There are multiple conditions for this leak to occur and while most applications are unlikely to be affected, it is still recommended to upgrade to this latest version.</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.SP2/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=12410416" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2023/07/11/weld-511SP1/">Weld 5.1.1.SP1</a>
@@ -403,42 +438,6 @@ <h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2022/06/08/weld-500SP2/">Weld 5.0.0.SP2</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2022-6-8
-                  &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>Another quick turnaround as more integrators adopt Weld 5 and help us squash bugs.
-                  Weld 5.0.0.SP2 is headed into Central as we speak.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>The main reason for this service release is <a href="https://issues.redhat.com/browse/WELD-2721">WELD-2721</a> which was a spec violation in how <code>AfterBeanDiscovery</code> methods were treated outside of lifecycle observer method invocations.
-                  Apart from that, there was also a corner case NPE during Weld Servlet and SE cooperation bootstrap (<a href="https://issues.redhat.com/browse/WELD-2720">WELD-2720</a>).</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>As always, if there are more problems with Weld 5, let us know and we&#8217;ll try to help.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>&#91; <a href="/download/">Download</a> &#93;
-                  &#91; <a href="http://docs.jboss.org/weld/reference/5.0.0.SP2/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=12390013" target="_blank" rel="noopener">Release notes</a> &#93;</p>
-                  </div>
-                </div>
-                <hr>
-              </div>
               <div class="pagination-links"><a href="/news/" class="previous-link">Previous</a> <a href="/news/" class="page-link">1</a> <span class="current-page">2</span> <a href="/news/page/3.html" class="page-link">3</a> <span class="skip">...</span><a href="/news/page/18.html" class="page-link">18</a> <a href="/news/page/19.html" class="page-link">19</a> <a href="/news/page/3.html" class="next-link">Next</a> </div>
               <hr>
               <div>
diff --git a/news/page/3.html b/news/page/3.html
index 0f959efb..f880eafc 100644
--- a/news/page/3.html
+++ b/news/page/3.html
@@ -141,6 +141,42 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2022/06/08/weld-500SP2/">Weld 5.0.0.SP2</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2022-6-8
+                  &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>Another quick turnaround as more integrators adopt Weld 5 and help us squash bugs.
+                  Weld 5.0.0.SP2 is headed into Central as we speak.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>The main reason for this service release is <a href="https://issues.redhat.com/browse/WELD-2721">WELD-2721</a> which was a spec violation in how <code>AfterBeanDiscovery</code> methods were treated outside of lifecycle observer method invocations.
+                  Apart from that, there was also a corner case NPE during Weld Servlet and SE cooperation bootstrap (<a href="https://issues.redhat.com/browse/WELD-2720">WELD-2720</a>).</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>As always, if there are more problems with Weld 5, let us know and we&#8217;ll try to help.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="/download/">Download</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/5.0.0.SP2/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=12390013" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2022/05/04/weld-500SP1/">Weld 5.0.0.SP1</a>
@@ -338,78 +374,6 @@ <h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2022/02/16/weld-403Final-319Final/">Weld 4.0.3.Final and 3.1.9.Final</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2022-2-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>Weld 3.1.9.Final for Jakarta EE 8 and Weld 4.0.3.Final for Jakarta EE 9 are now available.</p>
-                  </div>
-                  <div class="admonitionblock note">
-                  <table>
-                  <tr>
-                  <td class="icon">
-                  <div class="title">Note</div>
-                  </td>
-                  <td class="content">
-                  Weld 3.1 and Weld 4.0 now enter a maintenance mode - there will be no further active development on these branches. Instead, the focus will be on Weld 5/EE 10 and beyond.
-                  </td>
-                  </tr>
-                  </table>
-                  </div>
-                  <div class="paragraph">
-                  <p>Here is a brief list of notable changes; all of these are present in both Weld versions:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Gracefully handle non-existing classpath entries in SE (<a href="https://issues.jboss.org/browse/WELD-2605" target="_blank" rel="noopener">WELD-2605</a>)</p>
-                  </li>
-                  <li>
-                  <p>Proxies for classes starting with <code>jakarta.*</code> now have Weld proxy prefix instead (<a href="https://issues.jboss.org/browse/WELD-2684" target="_blank" rel="noopener">WELD-2684</a>)</p>
-                  </li>
-                  <li>
-                  <p><code>WeldInstance.Handle#get()</code> could incorrectly return the same instance even after destroying underlying contextual reference (<a href="https://issues.jboss.org/browse/WELD-2687" target="_blank" rel="noopener">WELD-2687</a>)</p>
-                  </li>
-                  <li>
-                  <p>Fixed <code>BeanConfigurator#produceWith()</code> leaking dependent bean under certain conditions (<a href="https://issues.jboss.org/browse/WELD-2693" target="_blank" rel="noopener">WELD-2693</a>)</p>
-                  </li>
-                  <li>
-                  <p>Correct default package detection inside <code>ProxyFactory</code> (<a href="https://issues.jboss.org/browse/WELD-2704" target="_blank" rel="noopener">WELD-2704</a>)</p>
-                  </li>
-                  <li>
-                  <p>Several minor changes with regard to testing setup and update configurations (<a href="https://issues.jboss.org/browse/WELD-2706" target="_blank" rel="noopener">WELD-2706</a> and <a href="https://issues.jboss.org/browse/WELD-2707" target="_blank" rel="noopener">WELD-2707</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>Last but not least, for those using WildFly, I would recommend taking a look into their <a href="https://www.wildfly.org/news/2022/01/21/WildFly-2022/" target="_blank" rel="noopener">release plan for 2022</a>.
-                  It details which WildFly is the last for EE 8 and EE 9 and what happens going onwards.
-                  Weld is of course going to keep up the pace and we are working on integrating Weld 5 into Wildfly.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>&#91; <a href="/download/">Download</a> &#93;
-                  &#91; <a href="http://docs.jboss.org/weld/reference/4.0.3.Final/en-US/html_single/" target="_blank" rel="noopener">Documentation Weld 4.0.3.Final</a> &#93;
-                  &#91; <a href="http://docs.jboss.org/weld/reference/3.1.9.Final/en-US/html_single/" target="_blank" rel="noopener">Documentation Weld 3.1.9.Final</a> &#93;
-                  &#91; <a href="https://issues.redhat.com/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12359404" target="_blank" rel="noopener">Release notes for Weld 4.0.3.Final</a> &#93;
-                  &#91; <a href="https://issues.redhat.com/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12359403" target="_blank" rel="noopener">Release notes for Weld 3.1.9.Final</a> &#93;</p>
-                  </div>
-                </div>
-                <hr>
-              </div>
               <div class="pagination-links"><a href="/news/page/2.html" class="previous-link">Previous</a> <a href="/news/" class="page-link">1</a> <a href="/news/page/2.html" class="page-link">2</a> <span class="current-page">3</span> <a href="/news/page/4.html" class="page-link">4</a> <span class="skip">...</span><a href="/news/page/18.html" class="page-link">18</a> <a href="/news/page/19.html" class="page-link">19</a> <a href="/news/page/4.html" class="next-link">Next</a> </div>
               <hr>
               <div>
diff --git a/news/page/4.html b/news/page/4.html
index 08759c76..002111a9 100644
--- a/news/page/4.html
+++ b/news/page/4.html
@@ -141,6 +141,78 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2022/02/16/weld-403Final-319Final/">Weld 4.0.3.Final and 3.1.9.Final</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2022-2-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>Weld 3.1.9.Final for Jakarta EE 8 and Weld 4.0.3.Final for Jakarta EE 9 are now available.</p>
+                  </div>
+                  <div class="admonitionblock note">
+                  <table>
+                  <tr>
+                  <td class="icon">
+                  <div class="title">Note</div>
+                  </td>
+                  <td class="content">
+                  Weld 3.1 and Weld 4.0 now enter a maintenance mode - there will be no further active development on these branches. Instead, the focus will be on Weld 5/EE 10 and beyond.
+                  </td>
+                  </tr>
+                  </table>
+                  </div>
+                  <div class="paragraph">
+                  <p>Here is a brief list of notable changes; all of these are present in both Weld versions:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Gracefully handle non-existing classpath entries in SE (<a href="https://issues.jboss.org/browse/WELD-2605" target="_blank" rel="noopener">WELD-2605</a>)</p>
+                  </li>
+                  <li>
+                  <p>Proxies for classes starting with <code>jakarta.*</code> now have Weld proxy prefix instead (<a href="https://issues.jboss.org/browse/WELD-2684" target="_blank" rel="noopener">WELD-2684</a>)</p>
+                  </li>
+                  <li>
+                  <p><code>WeldInstance.Handle#get()</code> could incorrectly return the same instance even after destroying underlying contextual reference (<a href="https://issues.jboss.org/browse/WELD-2687" target="_blank" rel="noopener">WELD-2687</a>)</p>
+                  </li>
+                  <li>
+                  <p>Fixed <code>BeanConfigurator#produceWith()</code> leaking dependent bean under certain conditions (<a href="https://issues.jboss.org/browse/WELD-2693" target="_blank" rel="noopener">WELD-2693</a>)</p>
+                  </li>
+                  <li>
+                  <p>Correct default package detection inside <code>ProxyFactory</code> (<a href="https://issues.jboss.org/browse/WELD-2704" target="_blank" rel="noopener">WELD-2704</a>)</p>
+                  </li>
+                  <li>
+                  <p>Several minor changes with regard to testing setup and update configurations (<a href="https://issues.jboss.org/browse/WELD-2706" target="_blank" rel="noopener">WELD-2706</a> and <a href="https://issues.jboss.org/browse/WELD-2707" target="_blank" rel="noopener">WELD-2707</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>Last but not least, for those using WildFly, I would recommend taking a look into their <a href="https://www.wildfly.org/news/2022/01/21/WildFly-2022/" target="_blank" rel="noopener">release plan for 2022</a>.
+                  It details which WildFly is the last for EE 8 and EE 9 and what happens going onwards.
+                  Weld is of course going to keep up the pace and we are working on integrating Weld 5 into Wildfly.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="/download/">Download</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/4.0.3.Final/en-US/html_single/" target="_blank" rel="noopener">Documentation Weld 4.0.3.Final</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/3.1.9.Final/en-US/html_single/" target="_blank" rel="noopener">Documentation Weld 3.1.9.Final</a> &#93;
+                  &#91; <a href="https://issues.redhat.com/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12359404" target="_blank" rel="noopener">Release notes for Weld 4.0.3.Final</a> &#93;
+                  &#91; <a href="https://issues.redhat.com/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12359403" target="_blank" rel="noopener">Release notes for Weld 3.1.9.Final</a> &#93;</p>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2022/01/24/weld-500Beta1/">Weld 5.0.0.Beta1</a>
@@ -682,105 +754,6 @@ <h2 id="_wildfly_patch">WildFly Patch</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2021/03/18/weld-317Final/">Weld 3.1.7.Final</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2021-3-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>Weld 3.1.7.Final along with API 3.1.SP4 is now up for grabs!</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Along a few bugfixes, the flagship of this release is a rework of Weld&#8217;s default class defining utilities which should eliminate those pesky JDK 11+ warnings about illegal reflective access.
-                  You can find more details on it below or in the <a href="https://issues.redhat.com/browse/WELD-2581">JIRA ticket</a>; in case you encounter any issue with it, please don&#8217;t hesitate to reach out to us.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>So, let&#8217;s take a closer look:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Class Defining in Weld</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Weld Core is now a Multi-Release JAR providing two different implementations for JDK 8 and JDK 11 or newer</p>
-                  </li>
-                  <li>
-                  <p>Integrators are still encouraged to implement <a href="https://github.com/weld/api/blob/3.1.SP4/weld-spi/src/main/java/org/jboss/weld/serialization/spi/ProxyServices.java"><code>ProxyServices</code></a> class from our API</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>All implementations of this interface are now presumed to support class defining (<a href="https://github.com/weld/api/blob/3.1.SP4/weld-spi/src/main/java/org/jboss/weld/serialization/spi/ProxyServices.java#L138-L150"><code>ProxyServices#supportsClassDefining()</code></a> is now deprecated and not used)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>For SE environment or an integrator that doesn&#8217;t implement the aforementioned API, Weld now provides a default implementation of <code>ProxyServices</code> which:</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>On JDK 8 behaves the same as it did until now - it cracks open <code>ClassLoader.defineClass(&#8230;&#8203;)</code> method and uses that</p>
-                  </li>
-                  <li>
-                  <p>On JDK 11+ it uses a combination of <code>MethodHandles.Lookup</code> and a custom <code>ClassLoader</code>; the former is used for vast majority of cases with class loader being a solution for edge cases such as default packages or beans from signed JARs</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Other Weld Core Fixes</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p><code>BeanAttributesConfigurator</code> could incorrectly initialize default qualifiers when <code>@Named</code> was involved (<a href="https://issues.jboss.org/browse/WELD-2659" target="_blank" rel="noopener">WELD-2659</a>)</p>
-                  </li>
-                  <li>
-                  <p>Synthetic alternative beans did not trigger <code>ProcessBean</code> event as they should when enabled (<a href="https://issues.jboss.org/browse/WELD-2658" target="_blank" rel="noopener">WELD-2658</a>)</p>
-                  </li>
-                  <li>
-                  <p>Fixed proxy creation for beans in default package (<a href="https://issues.jboss.org/browse/WELD-2657" target="_blank" rel="noopener">WELD-2657</a>)</p>
-                  </li>
-                  <li>
-                  <p>Fixed a corner case scenario where a hierarchy of classes with bridge methods would not get correctly intercepted (<a href="https://issues.jboss.org/browse/WELD-2656" target="_blank" rel="noopener">WELD-2656</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>There is no WildFly patch at the moment. We are currently exploring how to properly ship a patch that would align with WildFly usage of Galleon; the tracking JIRA can be seen (<a href="https://issues.redhat.com/browse/WELD-2660">here</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.7.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=12353263" 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>
               <hr>
               <div>
diff --git a/news/page/5.html b/news/page/5.html
index bc45bf48..bb8f2019 100644
--- a/news/page/5.html
+++ b/news/page/5.html
@@ -141,6 +141,105 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2021/03/18/weld-317Final/">Weld 3.1.7.Final</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2021-3-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>Weld 3.1.7.Final along with API 3.1.SP4 is now up for grabs!</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Along a few bugfixes, the flagship of this release is a rework of Weld&#8217;s default class defining utilities which should eliminate those pesky JDK 11+ warnings about illegal reflective access.
+                  You can find more details on it below or in the <a href="https://issues.redhat.com/browse/WELD-2581">JIRA ticket</a>; in case you encounter any issue with it, please don&#8217;t hesitate to reach out to us.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>So, let&#8217;s take a closer look:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Class Defining in Weld</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Weld Core is now a Multi-Release JAR providing two different implementations for JDK 8 and JDK 11 or newer</p>
+                  </li>
+                  <li>
+                  <p>Integrators are still encouraged to implement <a href="https://github.com/weld/api/blob/3.1.SP4/weld-spi/src/main/java/org/jboss/weld/serialization/spi/ProxyServices.java"><code>ProxyServices</code></a> class from our API</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>All implementations of this interface are now presumed to support class defining (<a href="https://github.com/weld/api/blob/3.1.SP4/weld-spi/src/main/java/org/jboss/weld/serialization/spi/ProxyServices.java#L138-L150"><code>ProxyServices#supportsClassDefining()</code></a> is now deprecated and not used)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>For SE environment or an integrator that doesn&#8217;t implement the aforementioned API, Weld now provides a default implementation of <code>ProxyServices</code> which:</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>On JDK 8 behaves the same as it did until now - it cracks open <code>ClassLoader.defineClass(&#8230;&#8203;)</code> method and uses that</p>
+                  </li>
+                  <li>
+                  <p>On JDK 11+ it uses a combination of <code>MethodHandles.Lookup</code> and a custom <code>ClassLoader</code>; the former is used for vast majority of cases with class loader being a solution for edge cases such as default packages or beans from signed JARs</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Other Weld Core Fixes</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p><code>BeanAttributesConfigurator</code> could incorrectly initialize default qualifiers when <code>@Named</code> was involved (<a href="https://issues.jboss.org/browse/WELD-2659" target="_blank" rel="noopener">WELD-2659</a>)</p>
+                  </li>
+                  <li>
+                  <p>Synthetic alternative beans did not trigger <code>ProcessBean</code> event as they should when enabled (<a href="https://issues.jboss.org/browse/WELD-2658" target="_blank" rel="noopener">WELD-2658</a>)</p>
+                  </li>
+                  <li>
+                  <p>Fixed proxy creation for beans in default package (<a href="https://issues.jboss.org/browse/WELD-2657" target="_blank" rel="noopener">WELD-2657</a>)</p>
+                  </li>
+                  <li>
+                  <p>Fixed a corner case scenario where a hierarchy of classes with bridge methods would not get correctly intercepted (<a href="https://issues.jboss.org/browse/WELD-2656" target="_blank" rel="noopener">WELD-2656</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>There is no WildFly patch at the moment. We are currently exploring how to properly ship a patch that would align with WildFly usage of Galleon; the tracking JIRA can be seen (<a href="https://issues.redhat.com/browse/WELD-2660">here</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.7.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=12353263" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2021/01/13/weld-316Final/">Weld 3.1.6.Final</a>
@@ -548,136 +647,6 @@ <h2 id="_wildfly_patch">WildFly Patch</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2020/05/13/weld-jakarta-ee-9/">Weld 4 and Jakarta EE 9</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2020-5-13
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/release">release</a>
-                    ,
-                    <a href="/news/tags/jakarta">jakarta</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Matej Novotny
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="sect1">
-                  <h2 id="_weld_meets_jakarta_ee_9">Weld Meets Jakarta EE 9</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>Most of you surely know that Jakarta EE 9 is on the horizon; slowly but steadily it is making its way into Java world.
-                  And we are not far behind, in fact we have just released <strong>Weld 4.0.0.Alpha2</strong> which is an implementation of CDI 3.0!
-                  You heard that right, in Jakarta EE 9, all APIs have bumped their major versions; CDI turned 3.0 and so Weld version implementing that became 4.0.
-                  Hand in hand with it goes Weld API 4.0.Alpha1, also adapted to EE 9.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Some basic information about the release:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>All the bits should be available in Maven Central at this point.</p>
-                  </li>
-                  <li>
-                  <p>There is also <code>.zip</code> distribution as usual, see <a href="/download/">download page</a> for more information.</p>
-                  </li>
-                  <li>
-                  <p>No WildFly patch is provided this time around because WildFly does not yet have an EE 9 branch.</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_working_and_broken_parts">Working and Broken Parts</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>The only, yet considerably huge, change in APIs is (or at least should be) the swap from <code>javax</code> to <code>jakarta</code> packages.
-                  This comes with bunch of problems, for instance there is no EE server that could run on EE 9 with new packages yet.
-                  GlassFish is going to be first and they are working on integrating all the EE 9 reference implementations.
-                  There are some chicken-egg problems such as Weld requiring EE 9 server to execute CDI TCKs, but at the same time there is GlassFish needing Weld 4.0 to start operating with EE 9 in the first place.
-                  For this reason, our first few 4.0 releases are going to be marked as <code>Alpha</code> or <code>Beta</code>, they will not be fully tested and might be missing some parts that previous releases contained.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Here&#8217;s what&#8217;s working:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>All testing that doesn&#8217;t require full EE container</p>
-                  </li>
-                  <li>
-                  <p>Weld core implementation and API works as usual and is fully released</p>
-                  </li>
-                  <li>
-                  <p>Weld examples work only partially, all those needing EE container have nowhere to be deployed</p>
-                  </li>
-                  <li>
-                  <p>Weld SE works fully</p>
-                  </li>
-                  <li>
-                  <p>Weld Probe should work so long as you are in SE</p>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>And here are the missing parts:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>We cannot execute CDI TCKs until there are stable GlassFish build</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>We should be able to renew this pretty soon</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Other in-container tests that we have (running on WildFly) are now disabled</p>
-                  </li>
-                  <li>
-                  <p>Servlet parts of Weld are <strong>completely excluded</strong> from early releases</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>This is because there is currently no servlet working on EE 9, therefore we have nothing to adapt our internals to, yet</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>One big and sadly unanswered question is that of backward compatibility.
-                  In Jakarta itself, there seems to be a consensus of EE 9 not being backward compatible with EE 8.
-                  Weld 4 on its own will not work with applications written for Java EE 8 - basically with anything requiring old <code>javax</code> namespace packages.
-                  However, EE servers will be forced to adapt somehow, so I expect a tooling might eventually emerge that will allow to run legacy applications on newer servers.
-                  But that is yet to be seen and surely no sooner than after EE 9 release when other big servers start to adopt it.</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_development_plans">Development Plans</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>Just to make things clear - we are planning on actively developing both, Weld 3 and Weld 4.
-                  We understand that EE server will need to take their time switching to Jakarta EE 9, all the more due to the aforementioned circumstances around backward compatibility.
-                  Therefore, both our versions will get their share of updates and bug fixes in the future!</p>
-                  </div>
-                  </div>
-                  </div>
-                </div>
-                <hr>
-              </div>
               <div class="pagination-links"><a href="/news/page/4.html" class="previous-link">Previous</a> <a href="/news/" class="page-link">1</a> <a href="/news/page/2.html" class="page-link">2</a> <span class="skip">...</span><a href="/news/page/4.html" class="page-link">4</a> <span class="current-page">5</span> <a href="/news/page/6.html" class="page-link">6</a> <span class="skip">...</span><a href="/news/page/18.html" class="page-link">18</a> <a href="/news/page/19.html" class="page-link">19</a> <a href="/news/page/6.html" class="next-link">Next</a> </div>
               <hr>
               <div>
diff --git a/news/page/6.html b/news/page/6.html
index 64f95bb3..69b9423b 100644
--- a/news/page/6.html
+++ b/news/page/6.html
@@ -141,6 +141,136 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2020/05/13/weld-jakarta-ee-9/">Weld 4 and Jakarta EE 9</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2020-5-13
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/release">release</a>
+                    ,
+                    <a href="/news/tags/jakarta">jakarta</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Matej Novotny
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="sect1">
+                  <h2 id="_weld_meets_jakarta_ee_9">Weld Meets Jakarta EE 9</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>Most of you surely know that Jakarta EE 9 is on the horizon; slowly but steadily it is making its way into Java world.
+                  And we are not far behind, in fact we have just released <strong>Weld 4.0.0.Alpha2</strong> which is an implementation of CDI 3.0!
+                  You heard that right, in Jakarta EE 9, all APIs have bumped their major versions; CDI turned 3.0 and so Weld version implementing that became 4.0.
+                  Hand in hand with it goes Weld API 4.0.Alpha1, also adapted to EE 9.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Some basic information about the release:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>All the bits should be available in Maven Central at this point.</p>
+                  </li>
+                  <li>
+                  <p>There is also <code>.zip</code> distribution as usual, see <a href="/download/">download page</a> for more information.</p>
+                  </li>
+                  <li>
+                  <p>No WildFly patch is provided this time around because WildFly does not yet have an EE 9 branch.</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_working_and_broken_parts">Working and Broken Parts</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>The only, yet considerably huge, change in APIs is (or at least should be) the swap from <code>javax</code> to <code>jakarta</code> packages.
+                  This comes with bunch of problems, for instance there is no EE server that could run on EE 9 with new packages yet.
+                  GlassFish is going to be first and they are working on integrating all the EE 9 reference implementations.
+                  There are some chicken-egg problems such as Weld requiring EE 9 server to execute CDI TCKs, but at the same time there is GlassFish needing Weld 4.0 to start operating with EE 9 in the first place.
+                  For this reason, our first few 4.0 releases are going to be marked as <code>Alpha</code> or <code>Beta</code>, they will not be fully tested and might be missing some parts that previous releases contained.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Here&#8217;s what&#8217;s working:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>All testing that doesn&#8217;t require full EE container</p>
+                  </li>
+                  <li>
+                  <p>Weld core implementation and API works as usual and is fully released</p>
+                  </li>
+                  <li>
+                  <p>Weld examples work only partially, all those needing EE container have nowhere to be deployed</p>
+                  </li>
+                  <li>
+                  <p>Weld SE works fully</p>
+                  </li>
+                  <li>
+                  <p>Weld Probe should work so long as you are in SE</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>And here are the missing parts:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>We cannot execute CDI TCKs until there are stable GlassFish build</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>We should be able to renew this pretty soon</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Other in-container tests that we have (running on WildFly) are now disabled</p>
+                  </li>
+                  <li>
+                  <p>Servlet parts of Weld are <strong>completely excluded</strong> from early releases</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>This is because there is currently no servlet working on EE 9, therefore we have nothing to adapt our internals to, yet</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>One big and sadly unanswered question is that of backward compatibility.
+                  In Jakarta itself, there seems to be a consensus of EE 9 not being backward compatible with EE 8.
+                  Weld 4 on its own will not work with applications written for Java EE 8 - basically with anything requiring old <code>javax</code> namespace packages.
+                  However, EE servers will be forced to adapt somehow, so I expect a tooling might eventually emerge that will allow to run legacy applications on newer servers.
+                  But that is yet to be seen and surely no sooner than after EE 9 release when other big servers start to adopt it.</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_development_plans">Development Plans</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>Just to make things clear - we are planning on actively developing both, Weld 3 and Weld 4.
+                  We understand that EE server will need to take their time switching to Jakarta EE 9, all the more due to the aforementioned circumstances around backward compatibility.
+                  Therefore, both our versions will get their share of updates and bug fixes in the future!</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2020/03/28/weld-314Final/">Weld 3.1.4.Final</a>
@@ -560,248 +690,6 @@ <h2 id="_wildfly_patch">WildFly Patch</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2019/02/06/weld-310Final/">Weld 3.1.0.Final</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2019-2-6
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/release">release</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Matej Novotny
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>Weld 3.1.0.Final and Weld API 3.1.Final are now up for grabs. What&#8217;s in it for you?</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>There are quite a few new things in the mix - <code>InterceptionFactory</code> improvements, new API clases and methods, improvements to class defining for integrators in preparation for JDK 12.
-                  We now also support CDI context propagation between threads; there is a whole new SPI that allows users and/or frameworks to propagate request, session or conversation contexts.
-                  Last but no least, there are bug fixes, so let&#8217;s get right into it!</p>
-                  </div>
-                  <div class="admonitionblock note">
-                  <table>
-                  <tr>
-                  <td class="icon">
-                  <div class="title">Note</div>
-                  </td>
-                  <td class="content">
-                  Integrators (WildFly, Liberty, GlassFish, &#8230;&#8203;) will have to adjust to the changes made in SPI. Those are, most notably, the removal of long deprecated methods (<a href="https://issues.jboss.org/browse/WELD-2558" target="_blank" rel="noopener">WELD-2558</a>) and reworked <code>ProxyServices</code> which now delegate class defining responsibility to the integrator (<a href="https://issues.jboss.org/browse/WELD-2556" target="_blank" rel="noopener">WELD-2556</a>). This is crucial for Weld to operate on newer JDKs (12) and while Weld will work with the old approach for now, we will eventually fully swap to this new SPI.
-                  </td>
-                  </tr>
-                  </table>
-                  </div>
-                  <div class="paragraph">
-                  <p>Fixes and improvements:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Weld API/SPI</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Added API to allow for CDI context propagation between threads (<a href="https://issues.jboss.org/browse/WELD-2497" target="_blank" rel="noopener">WELD-2497</a>)</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>New API class was introduced (<code>WeldAlterableContext</code>), this class offers methods to manipulate context state</p>
-                  </li>
-                  <li>
-                  <p>You can now propagate <code>Request</code>, <code>Session</code> and <code>Conversation</code> contexts between threads as they all implement <code>WeldAlterableContext</code></p>
-                  </li>
-                  <li>
-                  <p>This comes with certain limitations and is mostly designed for frameworks which would do this for you (such as MicroProfile Concurrency) but anyone can use it</p>
-                  </li>
-                  <li>
-                  <p>For more information, please glance at <a href="http://docs.jboss.org/weld/reference/latest/en-US/html_single/#_propagating_built_in_contexts">this part of Weld documentation</a></p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p><code>WeldManager</code>, providing extra methods over what <code>BeanManager</code> offers, is now an injectable bean (<a href="https://issues.jboss.org/browse/WELD-2538" target="_blank" rel="noopener">WELD-2538</a>)</p>
-                  </li>
-                  <li>
-                  <p><code>WeldManager</code> now offers new util methods allowing you to easily grab active contexts</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>This is mainly for the purpose of context propagation as it also allows you to grab all active contexts that support it</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p><code>WeldManager</code> can now be used to check if any given context is active without having to care about exceptions (<a href="https://issues.jboss.org/browse/WELD-2537" target="_blank" rel="noopener">WELD-2537</a>)</p>
-                  </li>
-                  <li>
-                  <p>Added new SPI for class defining, deprecated old approach in <code>ProxyServices</code> (<a href="https://issues.jboss.org/browse/WELD-2556" target="_blank" rel="noopener">WELD-2556</a>)</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Integrators will have to implement this new API to be able to operate on JDK 12+</p>
-                  </li>
-                  <li>
-                  <p>Weld now delegates class defining to integrators in order to avoid having to crack open <code>ClassLoader</code> methods</p>
-                  </li>
-                  <li>
-                  <p>Previously, integrators provided <code>ClassLoader</code> instance which Weld then used to invoke <code>defineClass()</code> methods</p>
-                  </li>
-                  <li>
-                  <p>We now ask integrators to invoke those methods themselves while providing them with all the necessary bits for doing so</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Remove deprecated parts of API/SPI (<a href="https://issues.jboss.org/browse/WELD-2558" target="_blank" rel="noopener">WELD-2558</a>)</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Lots of unused and long deprecated methods were removed, should have no effect on code as those weren&#8217;t used anyway (most of them since Weld 3.0.0)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Weld Core</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Weld will now log a <code>WARNING</code> if you try to register an invalid qualifier (<a href="https://issues.jboss.org/browse/WELD-2522" target="_blank" rel="noopener">WELD-2522</a>)</p>
-                  </li>
-                  <li>
-                  <p>You can now use <code>InterceptionFactory</code> with an interface as a parameter (<a href="https://issues.jboss.org/browse/WELD-2550" target="_blank" rel="noopener">WELD-2550</a>, <a href="https://issues.jboss.org/browse/WELD-2533" target="_blank" rel="noopener">WELD-2533</a>)</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>This means the proxy class will be based off an interface which is by definition always proxyable</p>
-                  </li>
-                  <li>
-                  <p>You can therefore even supply an unproxyable implementation and it will still work</p>
-                  </li>
-                  <li>
-                  <p>Note that this is experimental feature with some limitations to it, see <a href="http://docs.jboss.org/weld/reference/latest/en-US/html_single/#_loosening_the_limitations_of_literal_interceptionfactory_literal">Weld docs</a> for more details</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Correct atomic behaviour in <code>RequestContextController</code> (<a href="https://issues.jboss.org/browse/WELD-2536" target="_blank" rel="noopener">WELD-2536</a>)</p>
-                  </li>
-                  <li>
-                  <p>Fix rare race condition in <code>ConcurrentValidator</code> (<a href="https://issues.jboss.org/browse/WELD-2545" target="_blank" rel="noopener">WELD-2545</a>)</p>
-                  </li>
-                  <li>
-                  <p>Small correction to interceptor resolution when they have no bindings (<a href="https://issues.jboss.org/browse/WELD-2521" target="_blank" rel="noopener">WELD-2521</a>)</p>
-                  </li>
-                  <li>
-                  <p>Enforce consistent behaviour between <code>AnnotatedType</code> and <code>WithAnnotations</code> in regards to default methods (<a href="https://issues.jboss.org/browse/WELD-2551" target="_blank" rel="noopener">WELD-2551</a>)</p>
-                  </li>
-                  <li>
-                  <p>All proxy-specific methods added by Weld now have more complex names to avoid (very rare) method clashes (<a href="https://issues.jboss.org/browse/WELD-2508" target="_blank" rel="noopener">WELD-2508</a>)</p>
-                  </li>
-                  <li>
-                  <p>Lower logging level of <code>InterceptorLogger.unableToDetermineInterceptedBean()</code> from <code>WARN</code> to <code>INFO</code> (<a href="https://issues.jboss.org/browse/WELD-2546" target="_blank" rel="noopener">WELD-2546</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Weld SE</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>You can now extend the set of bean defining annotations in Weld SE (<a href="https://issues.jboss.org/browse/WELD-2523" target="_blank" rel="noopener">WELD-2523</a>)</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>This is handy for when you have discovery on and want custom beans automatically picked up while still avoiding the <code>all</code> discovery mode</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Fix bug in handling JAR dependencies added onto classpath where you could accidentally add more packages than desired (<a href="https://issues.jboss.org/browse/WELD-2535" target="_blank" rel="noopener">WELD-2535</a>)</p>
-                  </li>
-                  <li>
-                  <p>Correct <code>ALLOW_OPTIMIZED_CLEANUP</code> configuration key value (<a href="https://issues.jboss.org/browse/WELD-2547" target="_blank" rel="noopener">WELD-2547</a>)</p>
-                  </li>
-                  <li>
-                  <p>When running with <code>SecurityManager</code> enabled, Weld will now refuse to use <code>ForkJoinPool</code> for startup and will pick different pool instead (<a href="https://issues.jboss.org/browse/WELD-2517" target="_blank" rel="noopener">WELD-2517</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Probe development tool</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Make sure <code>ProbeExtension</code> has priority over any other existing extensions (<a href="https://issues.jboss.org/browse/WELD-2524" target="_blank" rel="noopener">WELD-2524</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Other</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Stabilize testsuite and make sure dependencies are EE 8 based (<a href="https://issues.jboss.org/browse/WELD-2519" target="_blank" rel="noopener">WELD-2519</a>, <a href="https://issues.jboss.org/browse/WELD-2553" target="_blank" rel="noopener">WELD-2553</a>)</p>
-                  </li>
-                  <li>
-                  <p>Documentation has been updated to reflects EE 8 versions of servers (<a href="https://issues.jboss.org/browse/WELD-2529" target="_blank" rel="noopener">WELD-2529</a>)</p>
-                  </li>
-                  <li>
-                  <p>Documented all changes coming to Weld API in 3.1 update (<a href="https://issues.jboss.org/browse/WELD-2540" target="_blank" rel="noopener">WELD-2540</a>)</p>
-                  </li>
-                  <li>
-                  <p>Re-enable SpotBugs code quality checking on JDK 11+ (<a href="https://issues.jboss.org/browse/WELD-2544" target="_blank" rel="noopener">WELD-2544</a>)</p>
-                  </li>
-                  <li>
-                  <p>Upgraded WildFly Arquillian adapter to 2.1.1.Final (<a href="https://issues.jboss.org/browse/WELD-2543" target="_blank" rel="noopener">WELD-2543</a>)</p>
-                  </li>
-                  <li>
-                  <p>Revisit testing on Jetty (<a href="https://issues.jboss.org/browse/WELD-2528" target="_blank" rel="noopener">WELD-2528</a>)</p>
-                  </li>
-                  <li>
-                  <p>We are now regularly testing with JDK 11 and looking into JDK 12 testing</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.0.Final/wildfly-15.0.1.Final-weld-3.1.0.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly 15.0.1.Final</a> is available.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>If you’re not familiar with patching WildFly, check the <a href="/documentation/#12">FAQ</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>&#91; <a href="/download/">Download</a> &#93;
-                  &#91; <a href="http://docs.jboss.org/weld/reference/3.1.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=12339977" target="_blank" rel="noopener">Release notes</a> &#93;</p>
-                  </div>
-                  </div>
-                  </div>
-                </div>
-                <hr>
-              </div>
               <div class="pagination-links"><a href="/news/page/5.html" class="previous-link">Previous</a> <a href="/news/" class="page-link">1</a> <a href="/news/page/2.html" class="page-link">2</a> <span class="skip">...</span><a href="/news/page/5.html" class="page-link">5</a> <span class="current-page">6</span> <a href="/news/page/7.html" class="page-link">7</a> <span class="skip">...</span><a href="/news/page/18.html" class="page-link">18</a> <a href="/news/page/19.html" class="page-link">19</a> <a href="/news/page/7.html" class="next-link">Next</a> </div>
               <hr>
               <div>
diff --git a/news/page/7.html b/news/page/7.html
index d725078b..39f4aab3 100644
--- a/news/page/7.html
+++ b/news/page/7.html
@@ -141,6 +141,248 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2019/02/06/weld-310Final/">Weld 3.1.0.Final</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2019-2-6
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/release">release</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Matej Novotny
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>Weld 3.1.0.Final and Weld API 3.1.Final are now up for grabs. What&#8217;s in it for you?</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>There are quite a few new things in the mix - <code>InterceptionFactory</code> improvements, new API clases and methods, improvements to class defining for integrators in preparation for JDK 12.
+                  We now also support CDI context propagation between threads; there is a whole new SPI that allows users and/or frameworks to propagate request, session or conversation contexts.
+                  Last but no least, there are bug fixes, so let&#8217;s get right into it!</p>
+                  </div>
+                  <div class="admonitionblock note">
+                  <table>
+                  <tr>
+                  <td class="icon">
+                  <div class="title">Note</div>
+                  </td>
+                  <td class="content">
+                  Integrators (WildFly, Liberty, GlassFish, &#8230;&#8203;) will have to adjust to the changes made in SPI. Those are, most notably, the removal of long deprecated methods (<a href="https://issues.jboss.org/browse/WELD-2558" target="_blank" rel="noopener">WELD-2558</a>) and reworked <code>ProxyServices</code> which now delegate class defining responsibility to the integrator (<a href="https://issues.jboss.org/browse/WELD-2556" target="_blank" rel="noopener">WELD-2556</a>). This is crucial for Weld to operate on newer JDKs (12) and while Weld will work with the old approach for now, we will eventually fully swap to this new SPI.
+                  </td>
+                  </tr>
+                  </table>
+                  </div>
+                  <div class="paragraph">
+                  <p>Fixes and improvements:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Weld API/SPI</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Added API to allow for CDI context propagation between threads (<a href="https://issues.jboss.org/browse/WELD-2497" target="_blank" rel="noopener">WELD-2497</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>New API class was introduced (<code>WeldAlterableContext</code>), this class offers methods to manipulate context state</p>
+                  </li>
+                  <li>
+                  <p>You can now propagate <code>Request</code>, <code>Session</code> and <code>Conversation</code> contexts between threads as they all implement <code>WeldAlterableContext</code></p>
+                  </li>
+                  <li>
+                  <p>This comes with certain limitations and is mostly designed for frameworks which would do this for you (such as MicroProfile Concurrency) but anyone can use it</p>
+                  </li>
+                  <li>
+                  <p>For more information, please glance at <a href="http://docs.jboss.org/weld/reference/latest/en-US/html_single/#_propagating_built_in_contexts">this part of Weld documentation</a></p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p><code>WeldManager</code>, providing extra methods over what <code>BeanManager</code> offers, is now an injectable bean (<a href="https://issues.jboss.org/browse/WELD-2538" target="_blank" rel="noopener">WELD-2538</a>)</p>
+                  </li>
+                  <li>
+                  <p><code>WeldManager</code> now offers new util methods allowing you to easily grab active contexts</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>This is mainly for the purpose of context propagation as it also allows you to grab all active contexts that support it</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p><code>WeldManager</code> can now be used to check if any given context is active without having to care about exceptions (<a href="https://issues.jboss.org/browse/WELD-2537" target="_blank" rel="noopener">WELD-2537</a>)</p>
+                  </li>
+                  <li>
+                  <p>Added new SPI for class defining, deprecated old approach in <code>ProxyServices</code> (<a href="https://issues.jboss.org/browse/WELD-2556" target="_blank" rel="noopener">WELD-2556</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Integrators will have to implement this new API to be able to operate on JDK 12+</p>
+                  </li>
+                  <li>
+                  <p>Weld now delegates class defining to integrators in order to avoid having to crack open <code>ClassLoader</code> methods</p>
+                  </li>
+                  <li>
+                  <p>Previously, integrators provided <code>ClassLoader</code> instance which Weld then used to invoke <code>defineClass()</code> methods</p>
+                  </li>
+                  <li>
+                  <p>We now ask integrators to invoke those methods themselves while providing them with all the necessary bits for doing so</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Remove deprecated parts of API/SPI (<a href="https://issues.jboss.org/browse/WELD-2558" target="_blank" rel="noopener">WELD-2558</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Lots of unused and long deprecated methods were removed, should have no effect on code as those weren&#8217;t used anyway (most of them since Weld 3.0.0)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Weld Core</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Weld will now log a <code>WARNING</code> if you try to register an invalid qualifier (<a href="https://issues.jboss.org/browse/WELD-2522" target="_blank" rel="noopener">WELD-2522</a>)</p>
+                  </li>
+                  <li>
+                  <p>You can now use <code>InterceptionFactory</code> with an interface as a parameter (<a href="https://issues.jboss.org/browse/WELD-2550" target="_blank" rel="noopener">WELD-2550</a>, <a href="https://issues.jboss.org/browse/WELD-2533" target="_blank" rel="noopener">WELD-2533</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>This means the proxy class will be based off an interface which is by definition always proxyable</p>
+                  </li>
+                  <li>
+                  <p>You can therefore even supply an unproxyable implementation and it will still work</p>
+                  </li>
+                  <li>
+                  <p>Note that this is experimental feature with some limitations to it, see <a href="http://docs.jboss.org/weld/reference/latest/en-US/html_single/#_loosening_the_limitations_of_literal_interceptionfactory_literal">Weld docs</a> for more details</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Correct atomic behaviour in <code>RequestContextController</code> (<a href="https://issues.jboss.org/browse/WELD-2536" target="_blank" rel="noopener">WELD-2536</a>)</p>
+                  </li>
+                  <li>
+                  <p>Fix rare race condition in <code>ConcurrentValidator</code> (<a href="https://issues.jboss.org/browse/WELD-2545" target="_blank" rel="noopener">WELD-2545</a>)</p>
+                  </li>
+                  <li>
+                  <p>Small correction to interceptor resolution when they have no bindings (<a href="https://issues.jboss.org/browse/WELD-2521" target="_blank" rel="noopener">WELD-2521</a>)</p>
+                  </li>
+                  <li>
+                  <p>Enforce consistent behaviour between <code>AnnotatedType</code> and <code>WithAnnotations</code> in regards to default methods (<a href="https://issues.jboss.org/browse/WELD-2551" target="_blank" rel="noopener">WELD-2551</a>)</p>
+                  </li>
+                  <li>
+                  <p>All proxy-specific methods added by Weld now have more complex names to avoid (very rare) method clashes (<a href="https://issues.jboss.org/browse/WELD-2508" target="_blank" rel="noopener">WELD-2508</a>)</p>
+                  </li>
+                  <li>
+                  <p>Lower logging level of <code>InterceptorLogger.unableToDetermineInterceptedBean()</code> from <code>WARN</code> to <code>INFO</code> (<a href="https://issues.jboss.org/browse/WELD-2546" target="_blank" rel="noopener">WELD-2546</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Weld SE</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>You can now extend the set of bean defining annotations in Weld SE (<a href="https://issues.jboss.org/browse/WELD-2523" target="_blank" rel="noopener">WELD-2523</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>This is handy for when you have discovery on and want custom beans automatically picked up while still avoiding the <code>all</code> discovery mode</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Fix bug in handling JAR dependencies added onto classpath where you could accidentally add more packages than desired (<a href="https://issues.jboss.org/browse/WELD-2535" target="_blank" rel="noopener">WELD-2535</a>)</p>
+                  </li>
+                  <li>
+                  <p>Correct <code>ALLOW_OPTIMIZED_CLEANUP</code> configuration key value (<a href="https://issues.jboss.org/browse/WELD-2547" target="_blank" rel="noopener">WELD-2547</a>)</p>
+                  </li>
+                  <li>
+                  <p>When running with <code>SecurityManager</code> enabled, Weld will now refuse to use <code>ForkJoinPool</code> for startup and will pick different pool instead (<a href="https://issues.jboss.org/browse/WELD-2517" target="_blank" rel="noopener">WELD-2517</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Probe development tool</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Make sure <code>ProbeExtension</code> has priority over any other existing extensions (<a href="https://issues.jboss.org/browse/WELD-2524" target="_blank" rel="noopener">WELD-2524</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Other</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Stabilize testsuite and make sure dependencies are EE 8 based (<a href="https://issues.jboss.org/browse/WELD-2519" target="_blank" rel="noopener">WELD-2519</a>, <a href="https://issues.jboss.org/browse/WELD-2553" target="_blank" rel="noopener">WELD-2553</a>)</p>
+                  </li>
+                  <li>
+                  <p>Documentation has been updated to reflects EE 8 versions of servers (<a href="https://issues.jboss.org/browse/WELD-2529" target="_blank" rel="noopener">WELD-2529</a>)</p>
+                  </li>
+                  <li>
+                  <p>Documented all changes coming to Weld API in 3.1 update (<a href="https://issues.jboss.org/browse/WELD-2540" target="_blank" rel="noopener">WELD-2540</a>)</p>
+                  </li>
+                  <li>
+                  <p>Re-enable SpotBugs code quality checking on JDK 11+ (<a href="https://issues.jboss.org/browse/WELD-2544" target="_blank" rel="noopener">WELD-2544</a>)</p>
+                  </li>
+                  <li>
+                  <p>Upgraded WildFly Arquillian adapter to 2.1.1.Final (<a href="https://issues.jboss.org/browse/WELD-2543" target="_blank" rel="noopener">WELD-2543</a>)</p>
+                  </li>
+                  <li>
+                  <p>Revisit testing on Jetty (<a href="https://issues.jboss.org/browse/WELD-2528" target="_blank" rel="noopener">WELD-2528</a>)</p>
+                  </li>
+                  <li>
+                  <p>We are now regularly testing with JDK 11 and looking into JDK 12 testing</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.0.Final/wildfly-15.0.1.Final-weld-3.1.0.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly 15.0.1.Final</a> is available.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>If you’re not familiar with patching WildFly, check the <a href="/documentation/#12">FAQ</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="/download/">Download</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/3.1.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=12339977" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2018/09/26/weld-248Final/">Weld 2.4.8.Final</a>
@@ -633,151 +875,6 @@ <h2 id="_wildfly_patch">WildFly Patch</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2018/03/20/weld-247Final/">Weld 2.4.7.Final</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2018-3-20
-                  &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.4.7.Final is now available.
-                  It includes multiple important bugfixes, many of them focused around proxy generation and/or invocation.</p>
-                  </div>
-                  <div class="admonitionblock note">
-                  <table>
-                  <tr>
-                  <td class="icon">
-                  <div class="title">Note</div>
-                  </td>
-                  <td class="content">
-                  Weld 2.4 now enters maintenance mode - there will be no further active development on Weld 2. We will be channeling our efforts into Weld 3 instead.
-                  </td>
-                  </tr>
-                  </table>
-                  </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>Proxy-related issues:</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Fixed possible NPE with multiple deployments one of which uses <code>relaxed construction</code> configuration (<a href="https://issues.jboss.org/browse/WELD-2448" target="_blank" rel="noopener">WELD-2448</a>)</p>
-                  </li>
-                  <li>
-                  <p><code>BeanManager.getInjectableReference</code> was using unnecessarily strict checks for proxyability (<a href="https://issues.jboss.org/browse/WELD-2466" target="_blank" rel="noopener">WELD-2466</a>)</p>
-                  </li>
-                  <li>
-                  <p>Proxy serialization is now container agnostic (<a href="https://issues.jboss.org/browse/WELD-2447" target="_blank" rel="noopener">WELD-2447</a>)</p>
-                  </li>
-                  <li>
-                  <p>Fix invocation of private observer method (<a href="https://issues.jboss.org/browse/WELD-2443" target="_blank" rel="noopener">WELD-2443</a>)</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>This only applies to private observer method which is not intercepted but is declared on a bean which has some other intercepted methods</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Correct proxy generation for class hierarchy with abstract class and generics (<a href="https://issues.jboss.org/browse/WELD-2470" target="_blank" rel="noopener">WELD-2470</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Other issues:</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Minor optimization in internal structures of <code>InterceptionModel</code> (<a href="https://issues.jboss.org/browse/WELD-2455" target="_blank" rel="noopener">WELD-2455</a>)</p>
-                  </li>
-                  <li>
-                  <p>Improve exception logging for <code>DeploymentException</code> (<a href="https://issues.jboss.org/browse/WELD-2453" target="_blank" rel="noopener">WELD-2453</a>)</p>
-                  </li>
-                  <li>
-                  <p>Prevent NPE if <code>ProtectionDomain.getPermissions()</code> returns <code>null</code> (<a href="https://issues.jboss.org/browse/WELD-2464" target="_blank" rel="noopener">WELD-2464</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Weld SE</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Fields in <code>org.jboss.weld.environment.se.Weld</code> are now <code>protected</code> (<a href="https://issues.jboss.org/browse/WELD-2451" target="_blank" rel="noopener">WELD-2451</a>)</p>
-                  </li>
-                  <li>
-                  <p>Allow to register custom <code>BeanArchiveHandler</code> using <code>ServiceLoader</code> mechanism (<a href="https://issues.jboss.org/browse/WELD-2450" target="_blank" rel="noopener">WELD-2450</a>)</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>This applies to SE and Servlet environments</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Other</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>With OSGi, <code>javax.ejb</code> is now imported optionally (<a href="https://issues.jboss.org/browse/WELD-2458" target="_blank" rel="noopener">WELD-2458</a>)</p>
-                  </li>
-                  <li>
-                  <p>Weld now uses SpotBugs (a successor to FindBugs) (<a href="https://issues.jboss.org/browse/WELD-2462" target="_blank" rel="noopener">WELD-2462</a>)</p>
-                  </li>
-                  <li>
-                  <p><code>module-info</code>, if present, is now correctly ignored during bean discovery phase (<a href="https://issues.jboss.org/browse/WELD-2459" target="_blank" rel="noopener">WELD-2459</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.7.Final/wildfly-11.0.0.Final-weld-2.4.7.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.7.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=12336351" 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>
               <hr>
               <div>
diff --git a/news/page/8.html b/news/page/8.html
index fc695289..ccecaf42 100644
--- a/news/page/8.html
+++ b/news/page/8.html
@@ -141,6 +141,151 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2018/03/20/weld-247Final/">Weld 2.4.7.Final</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2018-3-20
+                  &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.4.7.Final is now available.
+                  It includes multiple important bugfixes, many of them focused around proxy generation and/or invocation.</p>
+                  </div>
+                  <div class="admonitionblock note">
+                  <table>
+                  <tr>
+                  <td class="icon">
+                  <div class="title">Note</div>
+                  </td>
+                  <td class="content">
+                  Weld 2.4 now enters maintenance mode - there will be no further active development on Weld 2. We will be channeling our efforts into Weld 3 instead.
+                  </td>
+                  </tr>
+                  </table>
+                  </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>Proxy-related issues:</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Fixed possible NPE with multiple deployments one of which uses <code>relaxed construction</code> configuration (<a href="https://issues.jboss.org/browse/WELD-2448" target="_blank" rel="noopener">WELD-2448</a>)</p>
+                  </li>
+                  <li>
+                  <p><code>BeanManager.getInjectableReference</code> was using unnecessarily strict checks for proxyability (<a href="https://issues.jboss.org/browse/WELD-2466" target="_blank" rel="noopener">WELD-2466</a>)</p>
+                  </li>
+                  <li>
+                  <p>Proxy serialization is now container agnostic (<a href="https://issues.jboss.org/browse/WELD-2447" target="_blank" rel="noopener">WELD-2447</a>)</p>
+                  </li>
+                  <li>
+                  <p>Fix invocation of private observer method (<a href="https://issues.jboss.org/browse/WELD-2443" target="_blank" rel="noopener">WELD-2443</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>This only applies to private observer method which is not intercepted but is declared on a bean which has some other intercepted methods</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Correct proxy generation for class hierarchy with abstract class and generics (<a href="https://issues.jboss.org/browse/WELD-2470" target="_blank" rel="noopener">WELD-2470</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Other issues:</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Minor optimization in internal structures of <code>InterceptionModel</code> (<a href="https://issues.jboss.org/browse/WELD-2455" target="_blank" rel="noopener">WELD-2455</a>)</p>
+                  </li>
+                  <li>
+                  <p>Improve exception logging for <code>DeploymentException</code> (<a href="https://issues.jboss.org/browse/WELD-2453" target="_blank" rel="noopener">WELD-2453</a>)</p>
+                  </li>
+                  <li>
+                  <p>Prevent NPE if <code>ProtectionDomain.getPermissions()</code> returns <code>null</code> (<a href="https://issues.jboss.org/browse/WELD-2464" target="_blank" rel="noopener">WELD-2464</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Weld SE</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Fields in <code>org.jboss.weld.environment.se.Weld</code> are now <code>protected</code> (<a href="https://issues.jboss.org/browse/WELD-2451" target="_blank" rel="noopener">WELD-2451</a>)</p>
+                  </li>
+                  <li>
+                  <p>Allow to register custom <code>BeanArchiveHandler</code> using <code>ServiceLoader</code> mechanism (<a href="https://issues.jboss.org/browse/WELD-2450" target="_blank" rel="noopener">WELD-2450</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>This applies to SE and Servlet environments</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Other</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>With OSGi, <code>javax.ejb</code> is now imported optionally (<a href="https://issues.jboss.org/browse/WELD-2458" target="_blank" rel="noopener">WELD-2458</a>)</p>
+                  </li>
+                  <li>
+                  <p>Weld now uses SpotBugs (a successor to FindBugs) (<a href="https://issues.jboss.org/browse/WELD-2462" target="_blank" rel="noopener">WELD-2462</a>)</p>
+                  </li>
+                  <li>
+                  <p><code>module-info</code>, if present, is now correctly ignored during bean discovery phase (<a href="https://issues.jboss.org/browse/WELD-2459" target="_blank" rel="noopener">WELD-2459</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.7.Final/wildfly-11.0.0.Final-weld-2.4.7.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.7.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=12336351" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2018/02/09/weld-303Final/">Weld 3.0.3.Final</a>
@@ -625,101 +770,6 @@ <h2 id="_wildfly_patch">WildFly Patch</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2017/09/11/weld-245Final/">Weld 2.4.5.Final</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2017-9-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>It&#8217;s about time we delivered another regular bugfix release for Weld 2.
-                  And while the list of fixes isn&#8217;t exhausting, some of them are quite crucial.</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>Revise Java 8 default methods plus proxies/sublasing behaviour (<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>All POMs in Weld core project should now have correct MIME types; this corrects issues with Nexus 3 (<a href="https://issues.jboss.org/browse/WELD-2417" target="_blank" rel="noopener">WELD-2417</a>)</p>
-                  </li>
-                  <li>
-                  <p>Proxies for signed packages should now be generated in custom packages (<a href="https://issues.jboss.org/browse/WELD-2402" target="_blank" rel="noopener">WELD-2402</a>)</p>
-                  </li>
-                  <li>
-                  <p>The behaviour of Weld Core and integrator provided implementation of <code>org.jboss.weld.bootstrap.api.Environment</code> is back to what it was in Weld 2.4.3.Final (<a href="https://issues.jboss.org/browse/WELD-2401" target="_blank" rel="noopener">WELD-2401</a>)</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>We found out this change could cause serious headaches to integrators so we will leave it as it is - sorry for the mess</p>
-                  </li>
-                  <li>
-                  <p>For Weld 3, we already have a better solution in <a href="https://issues.jboss.org/browse/WELD-2398" target="_blank" rel="noopener">place</a></p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Weld SE and Servlet</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Both, Weld SE and Weld Servlet, will now explicitly bring in dependency on jboss-classfilewriter 1.2+ (<a href="https://issues.jboss.org/browse/WELD-2406" target="_blank" rel="noopener">WELD-2406</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>
-                  </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.5.Final/wildfly-10.1.0.Final-weld-2.4.5.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly 10.1.0.Final</a> is available.
-                  But since WildFly 11 has already reached CR stage, we have decided to also provide you with <a href="http://download.jboss.org/weld/2.4.5.Final/wildfly-11.0.0.CR1-weld-2.4.5.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly 11.0.0.CR1</a>.
-                  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.5.Final/en-US/html/" target="_blank" rel="noopener">Documentation</a> &#93;
-                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?version=12334958&amp;styleName=Html&amp;projectId=12310891" target="_blank" rel="noopener">Release notes</a> &#93;</p>
-                  </div>
-                  </div>
-                  </div>
-                </div>
-                <hr>
-              </div>
               <div class="pagination-links"><a href="/news/page/7.html" class="previous-link">Previous</a> <a href="/news/" class="page-link">1</a> <a href="/news/page/2.html" class="page-link">2</a> <span class="skip">...</span><a href="/news/page/7.html" class="page-link">7</a> <span class="current-page">8</span> <a href="/news/page/9.html" class="page-link">9</a> <span class="skip">...</span><a href="/news/page/18.html" class="page-link">18</a> <a href="/news/page/19.html" class="page-link">19</a> <a href="/news/page/9.html" class="next-link">Next</a> </div>
               <hr>
               <div>
diff --git a/news/page/9.html b/news/page/9.html
index 6162e24f..3abfe584 100644
--- a/news/page/9.html
+++ b/news/page/9.html
@@ -141,6 +141,101 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2017/09/11/weld-245Final/">Weld 2.4.5.Final</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2017-9-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>It&#8217;s about time we delivered another regular bugfix release for Weld 2.
+                  And while the list of fixes isn&#8217;t exhausting, some of them are quite crucial.</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>Revise Java 8 default methods plus proxies/sublasing behaviour (<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>All POMs in Weld core project should now have correct MIME types; this corrects issues with Nexus 3 (<a href="https://issues.jboss.org/browse/WELD-2417" target="_blank" rel="noopener">WELD-2417</a>)</p>
+                  </li>
+                  <li>
+                  <p>Proxies for signed packages should now be generated in custom packages (<a href="https://issues.jboss.org/browse/WELD-2402" target="_blank" rel="noopener">WELD-2402</a>)</p>
+                  </li>
+                  <li>
+                  <p>The behaviour of Weld Core and integrator provided implementation of <code>org.jboss.weld.bootstrap.api.Environment</code> is back to what it was in Weld 2.4.3.Final (<a href="https://issues.jboss.org/browse/WELD-2401" target="_blank" rel="noopener">WELD-2401</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>We found out this change could cause serious headaches to integrators so we will leave it as it is - sorry for the mess</p>
+                  </li>
+                  <li>
+                  <p>For Weld 3, we already have a better solution in <a href="https://issues.jboss.org/browse/WELD-2398" target="_blank" rel="noopener">place</a></p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Weld SE and Servlet</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Both, Weld SE and Weld Servlet, will now explicitly bring in dependency on jboss-classfilewriter 1.2+ (<a href="https://issues.jboss.org/browse/WELD-2406" target="_blank" rel="noopener">WELD-2406</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>
+                  </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.5.Final/wildfly-10.1.0.Final-weld-2.4.5.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly 10.1.0.Final</a> is available.
+                  But since WildFly 11 has already reached CR stage, we have decided to also provide you with <a href="http://download.jboss.org/weld/2.4.5.Final/wildfly-11.0.0.CR1-weld-2.4.5.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly 11.0.0.CR1</a>.
+                  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.5.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/08/25/weld-301Final/">Weld 3.0.1.Final</a>
@@ -843,155 +938,6 @@ <h2 id="_trimmed_bean_archives">Trimmed Bean Archives</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2017/05/15/weld-300Final/">Weld 3.0.0.Final - the first implementation of CDI 2.0!</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2017-5-15
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/release">release</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Martin Kouba
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>I am very pleased to announce the release of Weld <strong>3.0.0.Final</strong> - the first implementation of <strong>CDI 2.0</strong>!
-                  I would like to thank not only to everyone involved in this particular release but also to the Weld community as a whole and also to all active CDI EG members who invested a lot of energy into the specification process!</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>[ source, java ]</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre>/**&#x000A;     * TODO: Continue to deliver bugfixes and improvements&#x000A;     */&#x000A;    public class WeldTeam extends OpenSourceCommunity {&#x000A;    &#x000A;      @Inject&#x000A;      @AwesomeNews&#x000A;      Event&lt;String&gt; event;&#x000A;    &#x000A;      public void release() {&#x000A;        // Fire asynchronously so that we don't need to wait for observer notification before we start celebrating!&#x000A;        event.fireAsync("CDI 1.2 is dead, long live CDI 2.0!");&#x000A;        celebrate();&#x000A;      }&#x000A;    &#x000A;    }</pre>
-                  </div>
-                  </div>
-                  <div class="admonitionblock note">
-                  <table>
-                  <tr>
-                  <td class="icon">
-                  <div class="title">Note</div>
-                  </td>
-                  <td class="content">
-                  Weld 3 is an IMPORTANT MILESTONE.
-                  Therefore, we&#8217;re preparing a special blogpost summarizing all the important stuff that was added.
-                  Expect the <strong>Tour around Weld 3</strong> blogpost within a few days.
-                  </td>
-                  </tr>
-                  </table>
-                  </div>
-                  <div class="paragraph">
-                  <p>Let&#8217;s sum up the notable changes since <strong>3.0.0.CR2</strong>:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Weld defines two non-portable <strong>notification options</strong> to configure the notification of asynchronous observer methods (see also <a href="http://docs.jboss.org/weld/reference/3.0.0.Final/en-US/html/events.html#_notification_options" target="_blank" rel="noopener">Notification options</a> for more info):</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p><code>weld.async.notification.mode</code> - the notification mode, possible values are: <code>SERIAL</code> (default) and <code>PARALLEL</code></p>
-                  </li>
-                  <li>
-                  <p><code>weld.async.notification.timeout</code> - the notification timeout (in milliseconds) after which the returned completion stage must be completed.</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>If the time expires the stage is completed exceptionally with a <code>CompletionException</code> holding the <code>java.util.concurrent.TimeoutException</code> as its cause</p>
-                  </li>
-                  <li>
-                  <p>The expiration does not abort the notification of the observers</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Session replication - 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>
-                  <li>
-                  <p>Fire <code>@Initialied(RequestScoped.class)</code>/<code>@Destroyed(RequestScoped.class)</code> events for a <code>@PostConstruct</code> callback if the request context was activated for the specific callback</p>
-                  </li>
-                  <li>
-                  <p>Weld SE</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>It&#8217;s possible to easily register a <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> 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>Weld Servlet</p>
-                  <div class="ulist">
-                  <ul>
-                  <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>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Added option to disable Jandex in Weld SE and Weld Servlet (<a href="https://issues.jboss.org/browse/WELD-2374" target="_blank" rel="noopener">WELD-2374</a>)</p>
-                  </li>
-                  <li>
-                  <p>Development tools</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>If a deployment validation fails and the development mode is enabled a simple <strong>validation HTML report</strong> (which contains a lot of useful information) is generated</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Users are encouraged to always attach this report when asking a question on the mailing list or any other communication channel</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Updated documentation and migration notes for integrators</p>
-                  </li>
-                  <li>
-                  <p>Examples cleanup (dropped GAE support, etc.)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_wildfly_patch">WildFly Patch</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>As usual, a <a href="http://wildfly.org/" target="_blank" rel="noopener">patch for WildFly</a> is available.
-                  This time the target platforms are <a href="http://download.jboss.org/weld/3.0.0.Final/wildfly-10.1.0.Final-weld-3.0.0.Final-patch.zip" target="_blank" rel="noopener">WildFly 10.1.0.Final</a> and <a href="http://download.jboss.org/weld/3.0.0.Final/wildfly-11.0.0.Alpha1-weld-3.0.0.Final-patch.zip" target="_blank" rel="noopener">WildFly 11.0.0.Alpha1</a>.
-                  If you’re not familiar with patching WildFly, check the <a href="/documentation/#12">FAQ</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>&#91; <a href="/download/">Download</a> &#93;
-                  &#91; <a href="http://docs.jboss.org/weld/reference/3.0.0.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=12333608" 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>
               <hr>
               <div>
diff --git a/news/tags/release/index.html b/news/tags/release/index.html
index 4d7bd1b6..657e27ce 100644
--- a/news/tags/release/index.html
+++ b/news/tags/release/index.html
@@ -141,6 +141,84 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2024/08/27/weld-513Final/">Weld 5.1.3.Final</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2024-8-27
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/release">release</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Matej Novotny
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>A new version of Weld 5.1 has landed in Maven Central.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>This is a bug squashing round which backports several notable fixes and changes from Weld 6 into Weld 5:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Change <code>BeanManager</code> resolution process for <code>BuildCompatibleExtension</code> not belonging to any bean archive (<a href="https://issues.redhat.com/browse/WELD-2794">WELD-2794</a>)</p>
+                  </li>
+                  <li>
+                  <p><code>LazySessionBeanStore</code> no longer swallows exceptions happening when attempting to initiate HTTP session (<a href="https://issues.redhat.com/browse/WELD-2762">WELD-2762</a>)</p>
+                  </li>
+                  <li>
+                  <p>Correct how we determine proxy package for beans with unassignable types in their bean type set (<a href="https://issues.redhat.com/browse/WELD-2763">WELD-2763</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>This was only problematic in environments using WeldDefaultProxyServices to define their proxies (such as Weld SE)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </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>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>Correct inheritance of producer fields if there is an extension present (<a href="https://issues.redhat.com/browse/WELD-2773">WELD-2773</a>)</p>
+                  </li>
+                  <li>
+                  <p>Make sure <code>@Default</code> qualifier is added to events fired via <code>BeanManager#getEvent()</code> where appropriate (<a href="https://issues.redhat.com/browse/WELD-2775">WELD-2775</a>)</p>
+                  </li>
+                  <li>
+                  <p>Observer method confiurator now correctly allows 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>Clean up legacy Jetty integration parts (<a href="https://issues.redhat.com/browse/WELD-2787">WELD-2787</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>Ensure OSGi bundle has access to all dependencies needed for built-in beans (<a href="https://issues.redhat.com/browse/WELD-2796">WELD-2796</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="/download/">Download</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/5.1.3.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=12414627" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2024/07/03/weld-600Beta4/">Weld 6.0.0.Beta4</a>
@@ -821,42 +899,6 @@ <h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2022/06/08/weld-500SP2/">Weld 5.0.0.SP2</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2022-6-8
-                  &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>Another quick turnaround as more integrators adopt Weld 5 and help us squash bugs.
-                  Weld 5.0.0.SP2 is headed into Central as we speak.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>The main reason for this service release is <a href="https://issues.redhat.com/browse/WELD-2721">WELD-2721</a> which was a spec violation in how <code>AfterBeanDiscovery</code> methods were treated outside of lifecycle observer method invocations.
-                  Apart from that, there was also a corner case NPE during Weld Servlet and SE cooperation bootstrap (<a href="https://issues.redhat.com/browse/WELD-2720">WELD-2720</a>).</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>As always, if there are more problems with Weld 5, let us know and we&#8217;ll try to help.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>&#91; <a href="/download/">Download</a> &#93;
-                  &#91; <a href="http://docs.jboss.org/weld/reference/5.0.0.SP2/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=12390013" 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 0c444093..f82e11b0 100644
--- a/news/tags/release/page/2.html
+++ b/news/tags/release/page/2.html
@@ -141,6 +141,42 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2022/06/08/weld-500SP2/">Weld 5.0.0.SP2</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2022-6-8
+                  &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>Another quick turnaround as more integrators adopt Weld 5 and help us squash bugs.
+                  Weld 5.0.0.SP2 is headed into Central as we speak.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>The main reason for this service release is <a href="https://issues.redhat.com/browse/WELD-2721">WELD-2721</a> which was a spec violation in how <code>AfterBeanDiscovery</code> methods were treated outside of lifecycle observer method invocations.
+                  Apart from that, there was also a corner case NPE during Weld Servlet and SE cooperation bootstrap (<a href="https://issues.redhat.com/browse/WELD-2720">WELD-2720</a>).</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>As always, if there are more problems with Weld 5, let us know and we&#8217;ll try to help.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="/download/">Download</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/5.0.0.SP2/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=12390013" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2022/05/04/weld-500SP1/">Weld 5.0.0.SP1</a>
@@ -951,105 +987,6 @@ <h2 id="_wildfly_patch">WildFly Patch</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2021/03/18/weld-317Final/">Weld 3.1.7.Final</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2021-3-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>Weld 3.1.7.Final along with API 3.1.SP4 is now up for grabs!</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Along a few bugfixes, the flagship of this release is a rework of Weld&#8217;s default class defining utilities which should eliminate those pesky JDK 11+ warnings about illegal reflective access.
-                  You can find more details on it below or in the <a href="https://issues.redhat.com/browse/WELD-2581">JIRA ticket</a>; in case you encounter any issue with it, please don&#8217;t hesitate to reach out to us.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>So, let&#8217;s take a closer look:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Class Defining in Weld</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Weld Core is now a Multi-Release JAR providing two different implementations for JDK 8 and JDK 11 or newer</p>
-                  </li>
-                  <li>
-                  <p>Integrators are still encouraged to implement <a href="https://github.com/weld/api/blob/3.1.SP4/weld-spi/src/main/java/org/jboss/weld/serialization/spi/ProxyServices.java"><code>ProxyServices</code></a> class from our API</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>All implementations of this interface are now presumed to support class defining (<a href="https://github.com/weld/api/blob/3.1.SP4/weld-spi/src/main/java/org/jboss/weld/serialization/spi/ProxyServices.java#L138-L150"><code>ProxyServices#supportsClassDefining()</code></a> is now deprecated and not used)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>For SE environment or an integrator that doesn&#8217;t implement the aforementioned API, Weld now provides a default implementation of <code>ProxyServices</code> which:</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>On JDK 8 behaves the same as it did until now - it cracks open <code>ClassLoader.defineClass(&#8230;&#8203;)</code> method and uses that</p>
-                  </li>
-                  <li>
-                  <p>On JDK 11+ it uses a combination of <code>MethodHandles.Lookup</code> and a custom <code>ClassLoader</code>; the former is used for vast majority of cases with class loader being a solution for edge cases such as default packages or beans from signed JARs</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Other Weld Core Fixes</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p><code>BeanAttributesConfigurator</code> could incorrectly initialize default qualifiers when <code>@Named</code> was involved (<a href="https://issues.jboss.org/browse/WELD-2659" target="_blank" rel="noopener">WELD-2659</a>)</p>
-                  </li>
-                  <li>
-                  <p>Synthetic alternative beans did not trigger <code>ProcessBean</code> event as they should when enabled (<a href="https://issues.jboss.org/browse/WELD-2658" target="_blank" rel="noopener">WELD-2658</a>)</p>
-                  </li>
-                  <li>
-                  <p>Fixed proxy creation for beans in default package (<a href="https://issues.jboss.org/browse/WELD-2657" target="_blank" rel="noopener">WELD-2657</a>)</p>
-                  </li>
-                  <li>
-                  <p>Fixed a corner case scenario where a hierarchy of classes with bridge methods would not get correctly intercepted (<a href="https://issues.jboss.org/browse/WELD-2656" target="_blank" rel="noopener">WELD-2656</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>There is no WildFly patch at the moment. We are currently exploring how to properly ship a patch that would align with WildFly usage of Galleon; the tracking JIRA can be seen (<a href="https://issues.redhat.com/browse/WELD-2660">here</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.7.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=12353263" 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 88a9b14d..b4276a9e 100644
--- a/news/tags/release/page/3.html
+++ b/news/tags/release/page/3.html
@@ -141,6 +141,105 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2021/03/18/weld-317Final/">Weld 3.1.7.Final</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2021-3-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>Weld 3.1.7.Final along with API 3.1.SP4 is now up for grabs!</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Along a few bugfixes, the flagship of this release is a rework of Weld&#8217;s default class defining utilities which should eliminate those pesky JDK 11+ warnings about illegal reflective access.
+                  You can find more details on it below or in the <a href="https://issues.redhat.com/browse/WELD-2581">JIRA ticket</a>; in case you encounter any issue with it, please don&#8217;t hesitate to reach out to us.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>So, let&#8217;s take a closer look:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Class Defining in Weld</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Weld Core is now a Multi-Release JAR providing two different implementations for JDK 8 and JDK 11 or newer</p>
+                  </li>
+                  <li>
+                  <p>Integrators are still encouraged to implement <a href="https://github.com/weld/api/blob/3.1.SP4/weld-spi/src/main/java/org/jboss/weld/serialization/spi/ProxyServices.java"><code>ProxyServices</code></a> class from our API</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>All implementations of this interface are now presumed to support class defining (<a href="https://github.com/weld/api/blob/3.1.SP4/weld-spi/src/main/java/org/jboss/weld/serialization/spi/ProxyServices.java#L138-L150"><code>ProxyServices#supportsClassDefining()</code></a> is now deprecated and not used)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>For SE environment or an integrator that doesn&#8217;t implement the aforementioned API, Weld now provides a default implementation of <code>ProxyServices</code> which:</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>On JDK 8 behaves the same as it did until now - it cracks open <code>ClassLoader.defineClass(&#8230;&#8203;)</code> method and uses that</p>
+                  </li>
+                  <li>
+                  <p>On JDK 11+ it uses a combination of <code>MethodHandles.Lookup</code> and a custom <code>ClassLoader</code>; the former is used for vast majority of cases with class loader being a solution for edge cases such as default packages or beans from signed JARs</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Other Weld Core Fixes</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p><code>BeanAttributesConfigurator</code> could incorrectly initialize default qualifiers when <code>@Named</code> was involved (<a href="https://issues.jboss.org/browse/WELD-2659" target="_blank" rel="noopener">WELD-2659</a>)</p>
+                  </li>
+                  <li>
+                  <p>Synthetic alternative beans did not trigger <code>ProcessBean</code> event as they should when enabled (<a href="https://issues.jboss.org/browse/WELD-2658" target="_blank" rel="noopener">WELD-2658</a>)</p>
+                  </li>
+                  <li>
+                  <p>Fixed proxy creation for beans in default package (<a href="https://issues.jboss.org/browse/WELD-2657" target="_blank" rel="noopener">WELD-2657</a>)</p>
+                  </li>
+                  <li>
+                  <p>Fixed a corner case scenario where a hierarchy of classes with bridge methods would not get correctly intercepted (<a href="https://issues.jboss.org/browse/WELD-2656" target="_blank" rel="noopener">WELD-2656</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>There is no WildFly patch at the moment. We are currently exploring how to properly ship a patch that would align with WildFly usage of Galleon; the tracking JIRA can be seen (<a href="https://issues.redhat.com/browse/WELD-2660">here</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.7.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=12353263" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2021/01/13/weld-316Final/">Weld 3.1.6.Final</a>
@@ -1097,248 +1196,6 @@ <h2 id="_wildfly_patch">WildFly Patch</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2019/02/06/weld-310Final/">Weld 3.1.0.Final</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2019-2-6
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/release">release</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Matej Novotny
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>Weld 3.1.0.Final and Weld API 3.1.Final are now up for grabs. What&#8217;s in it for you?</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>There are quite a few new things in the mix - <code>InterceptionFactory</code> improvements, new API clases and methods, improvements to class defining for integrators in preparation for JDK 12.
-                  We now also support CDI context propagation between threads; there is a whole new SPI that allows users and/or frameworks to propagate request, session or conversation contexts.
-                  Last but no least, there are bug fixes, so let&#8217;s get right into it!</p>
-                  </div>
-                  <div class="admonitionblock note">
-                  <table>
-                  <tr>
-                  <td class="icon">
-                  <div class="title">Note</div>
-                  </td>
-                  <td class="content">
-                  Integrators (WildFly, Liberty, GlassFish, &#8230;&#8203;) will have to adjust to the changes made in SPI. Those are, most notably, the removal of long deprecated methods (<a href="https://issues.jboss.org/browse/WELD-2558" target="_blank" rel="noopener">WELD-2558</a>) and reworked <code>ProxyServices</code> which now delegate class defining responsibility to the integrator (<a href="https://issues.jboss.org/browse/WELD-2556" target="_blank" rel="noopener">WELD-2556</a>). This is crucial for Weld to operate on newer JDKs (12) and while Weld will work with the old approach for now, we will eventually fully swap to this new SPI.
-                  </td>
-                  </tr>
-                  </table>
-                  </div>
-                  <div class="paragraph">
-                  <p>Fixes and improvements:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Weld API/SPI</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Added API to allow for CDI context propagation between threads (<a href="https://issues.jboss.org/browse/WELD-2497" target="_blank" rel="noopener">WELD-2497</a>)</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>New API class was introduced (<code>WeldAlterableContext</code>), this class offers methods to manipulate context state</p>
-                  </li>
-                  <li>
-                  <p>You can now propagate <code>Request</code>, <code>Session</code> and <code>Conversation</code> contexts between threads as they all implement <code>WeldAlterableContext</code></p>
-                  </li>
-                  <li>
-                  <p>This comes with certain limitations and is mostly designed for frameworks which would do this for you (such as MicroProfile Concurrency) but anyone can use it</p>
-                  </li>
-                  <li>
-                  <p>For more information, please glance at <a href="http://docs.jboss.org/weld/reference/latest/en-US/html_single/#_propagating_built_in_contexts">this part of Weld documentation</a></p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p><code>WeldManager</code>, providing extra methods over what <code>BeanManager</code> offers, is now an injectable bean (<a href="https://issues.jboss.org/browse/WELD-2538" target="_blank" rel="noopener">WELD-2538</a>)</p>
-                  </li>
-                  <li>
-                  <p><code>WeldManager</code> now offers new util methods allowing you to easily grab active contexts</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>This is mainly for the purpose of context propagation as it also allows you to grab all active contexts that support it</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p><code>WeldManager</code> can now be used to check if any given context is active without having to care about exceptions (<a href="https://issues.jboss.org/browse/WELD-2537" target="_blank" rel="noopener">WELD-2537</a>)</p>
-                  </li>
-                  <li>
-                  <p>Added new SPI for class defining, deprecated old approach in <code>ProxyServices</code> (<a href="https://issues.jboss.org/browse/WELD-2556" target="_blank" rel="noopener">WELD-2556</a>)</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Integrators will have to implement this new API to be able to operate on JDK 12+</p>
-                  </li>
-                  <li>
-                  <p>Weld now delegates class defining to integrators in order to avoid having to crack open <code>ClassLoader</code> methods</p>
-                  </li>
-                  <li>
-                  <p>Previously, integrators provided <code>ClassLoader</code> instance which Weld then used to invoke <code>defineClass()</code> methods</p>
-                  </li>
-                  <li>
-                  <p>We now ask integrators to invoke those methods themselves while providing them with all the necessary bits for doing so</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Remove deprecated parts of API/SPI (<a href="https://issues.jboss.org/browse/WELD-2558" target="_blank" rel="noopener">WELD-2558</a>)</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Lots of unused and long deprecated methods were removed, should have no effect on code as those weren&#8217;t used anyway (most of them since Weld 3.0.0)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Weld Core</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Weld will now log a <code>WARNING</code> if you try to register an invalid qualifier (<a href="https://issues.jboss.org/browse/WELD-2522" target="_blank" rel="noopener">WELD-2522</a>)</p>
-                  </li>
-                  <li>
-                  <p>You can now use <code>InterceptionFactory</code> with an interface as a parameter (<a href="https://issues.jboss.org/browse/WELD-2550" target="_blank" rel="noopener">WELD-2550</a>, <a href="https://issues.jboss.org/browse/WELD-2533" target="_blank" rel="noopener">WELD-2533</a>)</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>This means the proxy class will be based off an interface which is by definition always proxyable</p>
-                  </li>
-                  <li>
-                  <p>You can therefore even supply an unproxyable implementation and it will still work</p>
-                  </li>
-                  <li>
-                  <p>Note that this is experimental feature with some limitations to it, see <a href="http://docs.jboss.org/weld/reference/latest/en-US/html_single/#_loosening_the_limitations_of_literal_interceptionfactory_literal">Weld docs</a> for more details</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Correct atomic behaviour in <code>RequestContextController</code> (<a href="https://issues.jboss.org/browse/WELD-2536" target="_blank" rel="noopener">WELD-2536</a>)</p>
-                  </li>
-                  <li>
-                  <p>Fix rare race condition in <code>ConcurrentValidator</code> (<a href="https://issues.jboss.org/browse/WELD-2545" target="_blank" rel="noopener">WELD-2545</a>)</p>
-                  </li>
-                  <li>
-                  <p>Small correction to interceptor resolution when they have no bindings (<a href="https://issues.jboss.org/browse/WELD-2521" target="_blank" rel="noopener">WELD-2521</a>)</p>
-                  </li>
-                  <li>
-                  <p>Enforce consistent behaviour between <code>AnnotatedType</code> and <code>WithAnnotations</code> in regards to default methods (<a href="https://issues.jboss.org/browse/WELD-2551" target="_blank" rel="noopener">WELD-2551</a>)</p>
-                  </li>
-                  <li>
-                  <p>All proxy-specific methods added by Weld now have more complex names to avoid (very rare) method clashes (<a href="https://issues.jboss.org/browse/WELD-2508" target="_blank" rel="noopener">WELD-2508</a>)</p>
-                  </li>
-                  <li>
-                  <p>Lower logging level of <code>InterceptorLogger.unableToDetermineInterceptedBean()</code> from <code>WARN</code> to <code>INFO</code> (<a href="https://issues.jboss.org/browse/WELD-2546" target="_blank" rel="noopener">WELD-2546</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Weld SE</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>You can now extend the set of bean defining annotations in Weld SE (<a href="https://issues.jboss.org/browse/WELD-2523" target="_blank" rel="noopener">WELD-2523</a>)</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>This is handy for when you have discovery on and want custom beans automatically picked up while still avoiding the <code>all</code> discovery mode</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Fix bug in handling JAR dependencies added onto classpath where you could accidentally add more packages than desired (<a href="https://issues.jboss.org/browse/WELD-2535" target="_blank" rel="noopener">WELD-2535</a>)</p>
-                  </li>
-                  <li>
-                  <p>Correct <code>ALLOW_OPTIMIZED_CLEANUP</code> configuration key value (<a href="https://issues.jboss.org/browse/WELD-2547" target="_blank" rel="noopener">WELD-2547</a>)</p>
-                  </li>
-                  <li>
-                  <p>When running with <code>SecurityManager</code> enabled, Weld will now refuse to use <code>ForkJoinPool</code> for startup and will pick different pool instead (<a href="https://issues.jboss.org/browse/WELD-2517" target="_blank" rel="noopener">WELD-2517</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Probe development tool</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Make sure <code>ProbeExtension</code> has priority over any other existing extensions (<a href="https://issues.jboss.org/browse/WELD-2524" target="_blank" rel="noopener">WELD-2524</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Other</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Stabilize testsuite and make sure dependencies are EE 8 based (<a href="https://issues.jboss.org/browse/WELD-2519" target="_blank" rel="noopener">WELD-2519</a>, <a href="https://issues.jboss.org/browse/WELD-2553" target="_blank" rel="noopener">WELD-2553</a>)</p>
-                  </li>
-                  <li>
-                  <p>Documentation has been updated to reflects EE 8 versions of servers (<a href="https://issues.jboss.org/browse/WELD-2529" target="_blank" rel="noopener">WELD-2529</a>)</p>
-                  </li>
-                  <li>
-                  <p>Documented all changes coming to Weld API in 3.1 update (<a href="https://issues.jboss.org/browse/WELD-2540" target="_blank" rel="noopener">WELD-2540</a>)</p>
-                  </li>
-                  <li>
-                  <p>Re-enable SpotBugs code quality checking on JDK 11+ (<a href="https://issues.jboss.org/browse/WELD-2544" target="_blank" rel="noopener">WELD-2544</a>)</p>
-                  </li>
-                  <li>
-                  <p>Upgraded WildFly Arquillian adapter to 2.1.1.Final (<a href="https://issues.jboss.org/browse/WELD-2543" target="_blank" rel="noopener">WELD-2543</a>)</p>
-                  </li>
-                  <li>
-                  <p>Revisit testing on Jetty (<a href="https://issues.jboss.org/browse/WELD-2528" target="_blank" rel="noopener">WELD-2528</a>)</p>
-                  </li>
-                  <li>
-                  <p>We are now regularly testing with JDK 11 and looking into JDK 12 testing</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.0.Final/wildfly-15.0.1.Final-weld-3.1.0.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly 15.0.1.Final</a> is available.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>If you’re not familiar with patching WildFly, check the <a href="/documentation/#12">FAQ</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>&#91; <a href="/download/">Download</a> &#93;
-                  &#91; <a href="http://docs.jboss.org/weld/reference/3.1.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=12339977" 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 03c851d3..140b0834 100644
--- a/news/tags/release/page/4.html
+++ b/news/tags/release/page/4.html
@@ -141,6 +141,248 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2019/02/06/weld-310Final/">Weld 3.1.0.Final</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2019-2-6
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/release">release</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Matej Novotny
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>Weld 3.1.0.Final and Weld API 3.1.Final are now up for grabs. What&#8217;s in it for you?</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>There are quite a few new things in the mix - <code>InterceptionFactory</code> improvements, new API clases and methods, improvements to class defining for integrators in preparation for JDK 12.
+                  We now also support CDI context propagation between threads; there is a whole new SPI that allows users and/or frameworks to propagate request, session or conversation contexts.
+                  Last but no least, there are bug fixes, so let&#8217;s get right into it!</p>
+                  </div>
+                  <div class="admonitionblock note">
+                  <table>
+                  <tr>
+                  <td class="icon">
+                  <div class="title">Note</div>
+                  </td>
+                  <td class="content">
+                  Integrators (WildFly, Liberty, GlassFish, &#8230;&#8203;) will have to adjust to the changes made in SPI. Those are, most notably, the removal of long deprecated methods (<a href="https://issues.jboss.org/browse/WELD-2558" target="_blank" rel="noopener">WELD-2558</a>) and reworked <code>ProxyServices</code> which now delegate class defining responsibility to the integrator (<a href="https://issues.jboss.org/browse/WELD-2556" target="_blank" rel="noopener">WELD-2556</a>). This is crucial for Weld to operate on newer JDKs (12) and while Weld will work with the old approach for now, we will eventually fully swap to this new SPI.
+                  </td>
+                  </tr>
+                  </table>
+                  </div>
+                  <div class="paragraph">
+                  <p>Fixes and improvements:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Weld API/SPI</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Added API to allow for CDI context propagation between threads (<a href="https://issues.jboss.org/browse/WELD-2497" target="_blank" rel="noopener">WELD-2497</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>New API class was introduced (<code>WeldAlterableContext</code>), this class offers methods to manipulate context state</p>
+                  </li>
+                  <li>
+                  <p>You can now propagate <code>Request</code>, <code>Session</code> and <code>Conversation</code> contexts between threads as they all implement <code>WeldAlterableContext</code></p>
+                  </li>
+                  <li>
+                  <p>This comes with certain limitations and is mostly designed for frameworks which would do this for you (such as MicroProfile Concurrency) but anyone can use it</p>
+                  </li>
+                  <li>
+                  <p>For more information, please glance at <a href="http://docs.jboss.org/weld/reference/latest/en-US/html_single/#_propagating_built_in_contexts">this part of Weld documentation</a></p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p><code>WeldManager</code>, providing extra methods over what <code>BeanManager</code> offers, is now an injectable bean (<a href="https://issues.jboss.org/browse/WELD-2538" target="_blank" rel="noopener">WELD-2538</a>)</p>
+                  </li>
+                  <li>
+                  <p><code>WeldManager</code> now offers new util methods allowing you to easily grab active contexts</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>This is mainly for the purpose of context propagation as it also allows you to grab all active contexts that support it</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p><code>WeldManager</code> can now be used to check if any given context is active without having to care about exceptions (<a href="https://issues.jboss.org/browse/WELD-2537" target="_blank" rel="noopener">WELD-2537</a>)</p>
+                  </li>
+                  <li>
+                  <p>Added new SPI for class defining, deprecated old approach in <code>ProxyServices</code> (<a href="https://issues.jboss.org/browse/WELD-2556" target="_blank" rel="noopener">WELD-2556</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Integrators will have to implement this new API to be able to operate on JDK 12+</p>
+                  </li>
+                  <li>
+                  <p>Weld now delegates class defining to integrators in order to avoid having to crack open <code>ClassLoader</code> methods</p>
+                  </li>
+                  <li>
+                  <p>Previously, integrators provided <code>ClassLoader</code> instance which Weld then used to invoke <code>defineClass()</code> methods</p>
+                  </li>
+                  <li>
+                  <p>We now ask integrators to invoke those methods themselves while providing them with all the necessary bits for doing so</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Remove deprecated parts of API/SPI (<a href="https://issues.jboss.org/browse/WELD-2558" target="_blank" rel="noopener">WELD-2558</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Lots of unused and long deprecated methods were removed, should have no effect on code as those weren&#8217;t used anyway (most of them since Weld 3.0.0)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Weld Core</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Weld will now log a <code>WARNING</code> if you try to register an invalid qualifier (<a href="https://issues.jboss.org/browse/WELD-2522" target="_blank" rel="noopener">WELD-2522</a>)</p>
+                  </li>
+                  <li>
+                  <p>You can now use <code>InterceptionFactory</code> with an interface as a parameter (<a href="https://issues.jboss.org/browse/WELD-2550" target="_blank" rel="noopener">WELD-2550</a>, <a href="https://issues.jboss.org/browse/WELD-2533" target="_blank" rel="noopener">WELD-2533</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>This means the proxy class will be based off an interface which is by definition always proxyable</p>
+                  </li>
+                  <li>
+                  <p>You can therefore even supply an unproxyable implementation and it will still work</p>
+                  </li>
+                  <li>
+                  <p>Note that this is experimental feature with some limitations to it, see <a href="http://docs.jboss.org/weld/reference/latest/en-US/html_single/#_loosening_the_limitations_of_literal_interceptionfactory_literal">Weld docs</a> for more details</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Correct atomic behaviour in <code>RequestContextController</code> (<a href="https://issues.jboss.org/browse/WELD-2536" target="_blank" rel="noopener">WELD-2536</a>)</p>
+                  </li>
+                  <li>
+                  <p>Fix rare race condition in <code>ConcurrentValidator</code> (<a href="https://issues.jboss.org/browse/WELD-2545" target="_blank" rel="noopener">WELD-2545</a>)</p>
+                  </li>
+                  <li>
+                  <p>Small correction to interceptor resolution when they have no bindings (<a href="https://issues.jboss.org/browse/WELD-2521" target="_blank" rel="noopener">WELD-2521</a>)</p>
+                  </li>
+                  <li>
+                  <p>Enforce consistent behaviour between <code>AnnotatedType</code> and <code>WithAnnotations</code> in regards to default methods (<a href="https://issues.jboss.org/browse/WELD-2551" target="_blank" rel="noopener">WELD-2551</a>)</p>
+                  </li>
+                  <li>
+                  <p>All proxy-specific methods added by Weld now have more complex names to avoid (very rare) method clashes (<a href="https://issues.jboss.org/browse/WELD-2508" target="_blank" rel="noopener">WELD-2508</a>)</p>
+                  </li>
+                  <li>
+                  <p>Lower logging level of <code>InterceptorLogger.unableToDetermineInterceptedBean()</code> from <code>WARN</code> to <code>INFO</code> (<a href="https://issues.jboss.org/browse/WELD-2546" target="_blank" rel="noopener">WELD-2546</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Weld SE</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>You can now extend the set of bean defining annotations in Weld SE (<a href="https://issues.jboss.org/browse/WELD-2523" target="_blank" rel="noopener">WELD-2523</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>This is handy for when you have discovery on and want custom beans automatically picked up while still avoiding the <code>all</code> discovery mode</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Fix bug in handling JAR dependencies added onto classpath where you could accidentally add more packages than desired (<a href="https://issues.jboss.org/browse/WELD-2535" target="_blank" rel="noopener">WELD-2535</a>)</p>
+                  </li>
+                  <li>
+                  <p>Correct <code>ALLOW_OPTIMIZED_CLEANUP</code> configuration key value (<a href="https://issues.jboss.org/browse/WELD-2547" target="_blank" rel="noopener">WELD-2547</a>)</p>
+                  </li>
+                  <li>
+                  <p>When running with <code>SecurityManager</code> enabled, Weld will now refuse to use <code>ForkJoinPool</code> for startup and will pick different pool instead (<a href="https://issues.jboss.org/browse/WELD-2517" target="_blank" rel="noopener">WELD-2517</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Probe development tool</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Make sure <code>ProbeExtension</code> has priority over any other existing extensions (<a href="https://issues.jboss.org/browse/WELD-2524" target="_blank" rel="noopener">WELD-2524</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Other</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Stabilize testsuite and make sure dependencies are EE 8 based (<a href="https://issues.jboss.org/browse/WELD-2519" target="_blank" rel="noopener">WELD-2519</a>, <a href="https://issues.jboss.org/browse/WELD-2553" target="_blank" rel="noopener">WELD-2553</a>)</p>
+                  </li>
+                  <li>
+                  <p>Documentation has been updated to reflects EE 8 versions of servers (<a href="https://issues.jboss.org/browse/WELD-2529" target="_blank" rel="noopener">WELD-2529</a>)</p>
+                  </li>
+                  <li>
+                  <p>Documented all changes coming to Weld API in 3.1 update (<a href="https://issues.jboss.org/browse/WELD-2540" target="_blank" rel="noopener">WELD-2540</a>)</p>
+                  </li>
+                  <li>
+                  <p>Re-enable SpotBugs code quality checking on JDK 11+ (<a href="https://issues.jboss.org/browse/WELD-2544" target="_blank" rel="noopener">WELD-2544</a>)</p>
+                  </li>
+                  <li>
+                  <p>Upgraded WildFly Arquillian adapter to 2.1.1.Final (<a href="https://issues.jboss.org/browse/WELD-2543" target="_blank" rel="noopener">WELD-2543</a>)</p>
+                  </li>
+                  <li>
+                  <p>Revisit testing on Jetty (<a href="https://issues.jboss.org/browse/WELD-2528" target="_blank" rel="noopener">WELD-2528</a>)</p>
+                  </li>
+                  <li>
+                  <p>We are now regularly testing with JDK 11 and looking into JDK 12 testing</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.0.Final/wildfly-15.0.1.Final-weld-3.1.0.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly 15.0.1.Final</a> is available.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>If you’re not familiar with patching WildFly, check the <a href="/documentation/#12">FAQ</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="/download/">Download</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/3.1.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=12339977" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2018/09/26/weld-248Final/">Weld 2.4.8.Final</a>
@@ -1324,124 +1566,6 @@ <h2 id="_wildfly_patch">WildFly Patch</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2017/06/14/weld-244Final/">Weld 2.4.4.Final</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2017-6-14
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/release">release</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Matej Novotny
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>We have been busy chasing down some annoying little bugs and it&#8217;s high time you got the fruits of those efforts into your hands.
-                  Say hello to Weld 2.4.4.Final.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Notable fixes and improvements:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Weld Core</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Fixed bean discovery event ordering when processing producers (<a href="https://issues.jboss.org/browse/WELD-2393" target="_blank" rel="noopener">WELD-2393</a>)</p>
-                  </li>
-                  <li>
-                  <p>Eliminated an NPE for a corner case with abstract decorator (<a href="https://issues.jboss.org/browse/WELD-2273" target="_blank" rel="noopener">WELD-2273</a>)</p>
-                  </li>
-                  <li>
-                  <p>Corrected <code>@Initialized(RequestScoped.class)</code> event firing in <code>@PostConstruct</code> callbacks (<a href="https://issues.jboss.org/browse/WELD-2372" target="_blank" rel="noopener">WELD-2372</a>)</p>
-                  </li>
-                  <li>
-                  <p>Fixed <code>BeanManager.isStereotype()</code> behavior when checking a qualifier annotated with yet another qualifier (<a href="https://issues.jboss.org/browse/WELD-2390" target="_blank" rel="noopener">WELD-2390</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Weld SE</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Added a convenience static method <code>WeldContainer.current()</code>, a shortcut for <code>CDI.current()</code> with no need to cast the result (<a href="https://issues.jboss.org/browse/WELD-2399" target="_blank" rel="noopener">WELD-2399</a>)</p>
-                  </li>
-                  <li>
-                  <p>Allowed to specify bean discovery mode for synthetic archives (<a href="https://issues.jboss.org/browse/WELD-2386" target="_blank" rel="noopener">WELD-2386</a>)</p>
-                  </li>
-                  <li>
-                  <p>Fixed bean class discovery problem when adding whole packages (<a href="https://issues.jboss.org/browse/WELD-2395" target="_blank" rel="noopener">WELD-2395</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Weld Servlet</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Improved logging and make checks more lenient in case the container is not yet bootstrapped (<a href="https://issues.jboss.org/browse/WELD-2382" target="_blank" rel="noopener">WELD-2382</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Configuration options</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>In SE and Servlet environments, Jandex can now be forcibly prohibited from processing your archives. This is useful when a third-party dependecy brings in some unsupported Jandex version (<a href="https://issues.jboss.org/browse/WELD-2374" target="_blank" rel="noopener">WELD-2374</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Development tools</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>If a deployment validation fails and the development mode is enabled, a simple <strong>validation HTML report</strong> (which contains a lot of useful information) is generated</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Users are encouraged to always attach this report when asking a question on the mailing list or any other communication channel</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_wildfly_patch">WildFly Patch</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>As usual, a <a href="http://download.jboss.org/weld/2.4.4.Final/wildfly-10.1.0.Final-weld-2.4.4.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly</a> is available.
-                  Target platform is <strong>WildFly 10.1.0.Final</strong>.
-                  If you’re not familiar with patching WildFly, check the <a href="/documentation/#12">FAQ</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>&#91; <a href="/download/">Download</a> &#93;
-                  &#91; <a href="http://docs.jboss.org/weld/reference/2.4.4.Final/en-US/html/" target="_blank" rel="noopener">Documentation</a> &#93;
-                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?version=12334296&amp;styleName=Html&amp;projectId=12310891" target="_blank" rel="noopener">Release notes</a> &#93;</p>
-                  </div>
-                  </div>
-                  </div>
-                </div>
-                <hr>
-              </div>
               <div class="pagination-links"><a href="/news/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 57fc0f6a..2b912283 100644
--- a/news/tags/release/page/5.html
+++ b/news/tags/release/page/5.html
@@ -141,6 +141,124 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2017/06/14/weld-244Final/">Weld 2.4.4.Final</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2017-6-14
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/release">release</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Matej Novotny
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>We have been busy chasing down some annoying little bugs and it&#8217;s high time you got the fruits of those efforts into your hands.
+                  Say hello to Weld 2.4.4.Final.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Notable fixes and improvements:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Weld Core</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Fixed bean discovery event ordering when processing producers (<a href="https://issues.jboss.org/browse/WELD-2393" target="_blank" rel="noopener">WELD-2393</a>)</p>
+                  </li>
+                  <li>
+                  <p>Eliminated an NPE for a corner case with abstract decorator (<a href="https://issues.jboss.org/browse/WELD-2273" target="_blank" rel="noopener">WELD-2273</a>)</p>
+                  </li>
+                  <li>
+                  <p>Corrected <code>@Initialized(RequestScoped.class)</code> event firing in <code>@PostConstruct</code> callbacks (<a href="https://issues.jboss.org/browse/WELD-2372" target="_blank" rel="noopener">WELD-2372</a>)</p>
+                  </li>
+                  <li>
+                  <p>Fixed <code>BeanManager.isStereotype()</code> behavior when checking a qualifier annotated with yet another qualifier (<a href="https://issues.jboss.org/browse/WELD-2390" target="_blank" rel="noopener">WELD-2390</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Weld SE</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Added a convenience static method <code>WeldContainer.current()</code>, a shortcut for <code>CDI.current()</code> with no need to cast the result (<a href="https://issues.jboss.org/browse/WELD-2399" target="_blank" rel="noopener">WELD-2399</a>)</p>
+                  </li>
+                  <li>
+                  <p>Allowed to specify bean discovery mode for synthetic archives (<a href="https://issues.jboss.org/browse/WELD-2386" target="_blank" rel="noopener">WELD-2386</a>)</p>
+                  </li>
+                  <li>
+                  <p>Fixed bean class discovery problem when adding whole packages (<a href="https://issues.jboss.org/browse/WELD-2395" target="_blank" rel="noopener">WELD-2395</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Weld Servlet</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Improved logging and make checks more lenient in case the container is not yet bootstrapped (<a href="https://issues.jboss.org/browse/WELD-2382" target="_blank" rel="noopener">WELD-2382</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Configuration options</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>In SE and Servlet environments, Jandex can now be forcibly prohibited from processing your archives. This is useful when a third-party dependecy brings in some unsupported Jandex version (<a href="https://issues.jboss.org/browse/WELD-2374" target="_blank" rel="noopener">WELD-2374</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Development tools</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>If a deployment validation fails and the development mode is enabled, a simple <strong>validation HTML report</strong> (which contains a lot of useful information) is generated</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Users are encouraged to always attach this report when asking a question on the mailing list or any other communication channel</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_wildfly_patch">WildFly Patch</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>As usual, a <a href="http://download.jboss.org/weld/2.4.4.Final/wildfly-10.1.0.Final-weld-2.4.4.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly</a> is available.
+                  Target platform is <strong>WildFly 10.1.0.Final</strong>.
+                  If you’re not familiar with patching WildFly, check the <a href="/documentation/#12">FAQ</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="/download/">Download</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/2.4.4.Final/en-US/html/" target="_blank" rel="noopener">Documentation</a> &#93;
+                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?version=12334296&amp;styleName=Html&amp;projectId=12310891" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2017/05/15/weld-300Final/">Weld 3.0.0.Final - the first implementation of CDI 2.0!</a>
@@ -1065,123 +1183,6 @@ <h2 id="_wildfly_patch">WildFly Patch</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2016/07/01/weld-235Final/">Weld 2.3.5.Final</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2016-7-1
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/release">release</a>
-                    ,
-                    <a href="/news/tags/plans">plans</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Martin Kouba
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>The next version of the stable 2.3 branch has been released!
-                  See also <a href="https://issues.jboss.org/projects/WELD/versions/12330052" target="_blank" rel="noopener">the release details</a>.
-                  Thanks to everyone involved in this release!</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>We plan to create the <strong>2.4 branch</strong> of Weld within a few weeks.
-                  Weld 2.4 will remain a <strong>CDI 1.2</strong> implementation.
-                  We would like to do some cleanup (e.g. remove deprecated classes from Weld SE), enhance the API and also add some new features.
-                  See also <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12330683" target="_blank" rel="noopener">the list of issues for 2.4.0.CR1</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Notable bugfixes and improvements:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>fixed static disposer method invocation (<a href="https://issues.jboss.org/browse/WELD-2176" target="_blank" rel="noopener">WELD-2176</a>)</p>
-                  </li>
-                  <li>
-                  <p>fixed private observer/producer/disposer invocation on a bean with decorator (<a href="https://issues.jboss.org/browse/WELD-2179" target="_blank" rel="noopener">WELD-2179</a>)</p>
-                  </li>
-                  <li>
-                  <p>fixed <code>Instance.destroy()</code> for dependent session beans (<a href="https://issues.jboss.org/browse/WELD-2148" target="_blank" rel="noopener">WELD-2148</a>)</p>
-                  </li>
-                  <li>
-                  <p>fixed <code>ArraySet.hashCode()</code> to comply with <code>java.util.Set.hashCode()</code> contract (<a href="https://issues.jboss.org/browse/WELD-2185" target="_blank" rel="noopener">WELD-2185</a>)</p>
-                  </li>
-                  <li>
-                  <p>log veto actions and modifications of lists returned by <code>AfterTypeDiscovery</code> (<a href="https://issues.jboss.org/browse/WELD-2170" target="_blank" rel="noopener">WELD-2170</a>, <a href="https://issues.jboss.org/browse/WELD-2171" target="_blank" rel="noopener">WELD-2171</a>)</p>
-                  </li>
-                  <li>
-                  <p>log a warning when a class is annotated with a scope but does not declare an appropriate constructor (<a href="https://issues.jboss.org/browse/WELD-2178" target="_blank" rel="noopener">WELD-2178</a>)</p>
-                  </li>
-                  <li>
-                  <p>support extension deployed in multiple WARs in an EAR (<a href="https://issues.jboss.org/browse/WELD-2143" target="_blank" rel="noopener">WELD-2143</a>)</p>
-                  </li>
-                  <li>
-                  <p>detect non-unique <code>BeanDeploymentArchive</code> identifier (<a href="https://issues.jboss.org/browse/WELD-2165" target="_blank" rel="noopener">WELD-2165</a>)</p>
-                  </li>
-                  <li>
-                  <p>Weld Servlet</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>fixed extraction of bean archive id - problem occures with embedded Jetty (<a href="https://issues.jboss.org/browse/WELD-2161" target="_blank" rel="noopener">WELD-2161</a>)</p>
-                  </li>
-                  <li>
-                  <p>improve the way <code>JandexDiscoveryStrategy</code> identifies an annotation annotated with <code>@NormalScope</code> (<a href="https://issues.jboss.org/browse/WELD-2160" target="_blank" rel="noopener">WELD-2160</a>)</p>
-                  </li>
-                  <li>
-                  <p><code>weld-servlet-core</code> declares dependency on <code>weld-core-jsf</code></p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Weld SE</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>do not pass system properties to Weld configuration (<a href="https://issues.jboss.org/browse/WELD-2146" target="_blank" rel="noopener">WELD-2146</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Probe - allow to test bean availability in a given bean archive</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>check for example the availability of an alternative in the demo application</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>many documentation and reference guide updates</p>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_wildfly_patch">WildFly Patch</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>As usual, a <a href="http://download.jboss.org/weld/2.3.5.Final/wildfly-10.0.0.Final-weld-2.3.5.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly</a> is available. This time the target platform is <strong>WildFly 10.0.0.Final</strong>.  If you’re not familiar with patching WildFly, check <a href="http://blog.eisele.net/2015/02/playing-with-weld-probe-see-all-of-your.html" target="_blank" rel="noopener">Markus&#8217;s tutorial</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>&#91; <a href="http://docs.jboss.org/cdi/api/1.2/" target="_blank" rel="noopener">CDI 1.2 API</a> &#93;
-                  &#91; <a href="/download/">Download</a> &#93;
-                  &#91; <a href="http://docs.jboss.org/weld/reference/2.3.5.Final/en-US/html/" target="_blank" rel="noopener">Documentation</a> &#93;
-                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12330052" 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 9f6c1696..1be39dbb 100644
--- a/news/tags/release/page/6.html
+++ b/news/tags/release/page/6.html
@@ -141,6 +141,123 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2016/07/01/weld-235Final/">Weld 2.3.5.Final</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2016-7-1
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/release">release</a>
+                    ,
+                    <a href="/news/tags/plans">plans</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Martin Kouba
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>The next version of the stable 2.3 branch has been released!
+                  See also <a href="https://issues.jboss.org/projects/WELD/versions/12330052" target="_blank" rel="noopener">the release details</a>.
+                  Thanks to everyone involved in this release!</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>We plan to create the <strong>2.4 branch</strong> of Weld within a few weeks.
+                  Weld 2.4 will remain a <strong>CDI 1.2</strong> implementation.
+                  We would like to do some cleanup (e.g. remove deprecated classes from Weld SE), enhance the API and also add some new features.
+                  See also <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12330683" target="_blank" rel="noopener">the list of issues for 2.4.0.CR1</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Notable bugfixes and improvements:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>fixed static disposer method invocation (<a href="https://issues.jboss.org/browse/WELD-2176" target="_blank" rel="noopener">WELD-2176</a>)</p>
+                  </li>
+                  <li>
+                  <p>fixed private observer/producer/disposer invocation on a bean with decorator (<a href="https://issues.jboss.org/browse/WELD-2179" target="_blank" rel="noopener">WELD-2179</a>)</p>
+                  </li>
+                  <li>
+                  <p>fixed <code>Instance.destroy()</code> for dependent session beans (<a href="https://issues.jboss.org/browse/WELD-2148" target="_blank" rel="noopener">WELD-2148</a>)</p>
+                  </li>
+                  <li>
+                  <p>fixed <code>ArraySet.hashCode()</code> to comply with <code>java.util.Set.hashCode()</code> contract (<a href="https://issues.jboss.org/browse/WELD-2185" target="_blank" rel="noopener">WELD-2185</a>)</p>
+                  </li>
+                  <li>
+                  <p>log veto actions and modifications of lists returned by <code>AfterTypeDiscovery</code> (<a href="https://issues.jboss.org/browse/WELD-2170" target="_blank" rel="noopener">WELD-2170</a>, <a href="https://issues.jboss.org/browse/WELD-2171" target="_blank" rel="noopener">WELD-2171</a>)</p>
+                  </li>
+                  <li>
+                  <p>log a warning when a class is annotated with a scope but does not declare an appropriate constructor (<a href="https://issues.jboss.org/browse/WELD-2178" target="_blank" rel="noopener">WELD-2178</a>)</p>
+                  </li>
+                  <li>
+                  <p>support extension deployed in multiple WARs in an EAR (<a href="https://issues.jboss.org/browse/WELD-2143" target="_blank" rel="noopener">WELD-2143</a>)</p>
+                  </li>
+                  <li>
+                  <p>detect non-unique <code>BeanDeploymentArchive</code> identifier (<a href="https://issues.jboss.org/browse/WELD-2165" target="_blank" rel="noopener">WELD-2165</a>)</p>
+                  </li>
+                  <li>
+                  <p>Weld Servlet</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>fixed extraction of bean archive id - problem occures with embedded Jetty (<a href="https://issues.jboss.org/browse/WELD-2161" target="_blank" rel="noopener">WELD-2161</a>)</p>
+                  </li>
+                  <li>
+                  <p>improve the way <code>JandexDiscoveryStrategy</code> identifies an annotation annotated with <code>@NormalScope</code> (<a href="https://issues.jboss.org/browse/WELD-2160" target="_blank" rel="noopener">WELD-2160</a>)</p>
+                  </li>
+                  <li>
+                  <p><code>weld-servlet-core</code> declares dependency on <code>weld-core-jsf</code></p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Weld SE</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>do not pass system properties to Weld configuration (<a href="https://issues.jboss.org/browse/WELD-2146" target="_blank" rel="noopener">WELD-2146</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Probe - allow to test bean availability in a given bean archive</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>check for example the availability of an alternative in the demo application</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>many documentation and reference guide updates</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_wildfly_patch">WildFly Patch</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>As usual, a <a href="http://download.jboss.org/weld/2.3.5.Final/wildfly-10.0.0.Final-weld-2.3.5.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly</a> is available. This time the target platform is <strong>WildFly 10.0.0.Final</strong>.  If you’re not familiar with patching WildFly, check <a href="http://blog.eisele.net/2015/02/playing-with-weld-probe-see-all-of-your.html" target="_blank" rel="noopener">Markus&#8217;s tutorial</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="http://docs.jboss.org/cdi/api/1.2/" target="_blank" rel="noopener">CDI 1.2 API</a> &#93;
+                  &#91; <a href="/download/">Download</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/2.3.5.Final/en-US/html/" target="_blank" rel="noopener">Documentation</a> &#93;
+                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12330052" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2016/04/28/weld-300Alpha16/">Weld 3.0.0.Alpha16</a>
@@ -956,160 +1073,6 @@ <h2 id="_wildfly_patch">WildFly Patch</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2015/04/21/weld-300Alpha8/">Weld 3.0.0.Alpha8</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2015-4-21
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/release">release</a>
-                    ,
-                    <a href="/news/tags/cdi2">cdi2</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Jozef Hartinger
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>Weld 3.0.0.Alpha8 has been released.
-                  The main change is the enhanced API for using Weld in Java SE environment. In addition, this release comes with several weld-probe improvements.</p>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_enhanced_api_for_weld_se">Enhanced API for Weld SE</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>Weld has provided <a href="http://docs.jboss.org/weld/reference/latest-2.2/en-US/html/environments.html#_java_se">support for the Java SE environment</a> for a long time with the weld-se module.
-                  The API provides an easy way for an application to initialize Weld and use it in a standalone mode.
-                  On initialization Weld SE scans the classpath for bean archives with the <code>beans.xml</code> file, similarly to how it&#8217;s done in the Java EE environment.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>In this release we are extending the API further.
-                  This is partially inspired by the current discussion in the CDI expert group where a standardized CDI API for Java SE is being proposed as part of <a href="https://issues.jboss.org/browse/CDI-26">CDI-26</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>The following code snippet shows the new API in action:</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">Weld builder = new Weld()&#x000A;        .disableDiscovery()&#x000A;        .packages(Main.class, Utils.class)&#x000A;        .interceptors(TransactionalInterceptor.class)&#x000A;        .property("org.jboss.weld.construction.relaxed", true);&#x000A;    &#x000A;    try (WeldContainer weld = builder.initialize()) {&#x000A;        MyBean bean = weld.select(MyBean.class).get();&#x000A;        System.out.println(bean.computeResult());&#x000A;    }</code></pre>
-                  </div>
-                  </div>
-                  <div class="paragraph">
-                  <p>There are several new things to notice:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>the <code>Weld</code> class is used as a builder to configure Weld before it is initialized</p>
-                  </li>
-                  <li>
-                  <p>automatic scanning can be disabled</p>
-                  </li>
-                  <li>
-                  <p>instead of scanning, classes or packages can be selected explicitly. All classes in those packages will be managed by Weld</p>
-                  </li>
-                  <li>
-                  <p>interceptors, decorators, extensions and <a href="http://docs.jboss.org/weld/reference/3.0.0.Alpha8/en-US/html/configure.html#_weld_configuration">Weld-specific configuration options</a> can be specified using the builder</p>
-                  </li>
-                  <li>
-                  <p><code>WeldContainer</code> now implements <code>AutoCloseable</code> and can therefore be used in a <code>try-with-resources</code> block. At any time that execution gets outside of the code block, the Weld instance is shut down and all managed instances are safely destroyed.</p>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>It is also possible to start multiple independent Weld instances:</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">new Weld().disableDiscovery().containerId("one").beanClasses(MyBean.class).initialize();&#x000A;    new Weld().disableDiscovery().containerId("two").beanClasses(OtherBean.class).initialize();&#x000A;    &#x000A;    MyBean bean = WeldContainer.instance("one").select(MyBean.class).get();&#x000A;    System.out.println(bean.computeResult());&#x000A;    &#x000A;    WeldContainer.instance("one").shutdown();&#x000A;    WeldContainer.instance("two").shutdown();</code></pre>
-                  </div>
-                  </div>
-                  <div class="paragraph">
-                  <p>Here, two independent <code>WeldContainer</code> instances are initialized.
-                  Each of them is given a unique ID.
-                  The ID can subsequently be used to obtain a <code>WeldContainer</code> reference in a different place of the code.
-                  One possible use-case this enables is for a library or framework (e.g. a testing framework) to use an embedded instance of Weld internally for its own needs (dependency injection, events, extensibility).
-                  This instance would not interfere with the Weld instance used by the application.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Obviously, automatic classpath scanning can still be used as before:</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">try (WeldContainer weld = new Weld().enableDiscovery().initialize()) {&#x000A;        MyBean bean = weld.select(MyBean.class).get();&#x000A;        System.out.println(bean.computeResult());&#x000A;    }</code></pre>
-                  </div>
-                  </div>
-                  <div class="paragraph">
-                  <p><strong>Update:</strong></p>
-                  </div>
-                  <div class="paragraph">
-                  <p>To play with the new API use the following dependency in you Maven project:</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;dependency&gt;&#x000A;        &lt;groupId&gt;org.jboss.weld.se&lt;/groupId&gt;&#x000A;        &lt;artifactId&gt;weld-se-core&lt;/artifactId&gt;&#x000A;        &lt;version&gt;3.0.0.Alpha8&lt;/version&gt;&#x000A;    &lt;/dependency&gt;</code></pre>
-                  </div>
-                  </div>
-                  <div class="paragraph">
-                  <p>Aforementioned classes are from the <code>org.jboss.weld.environment.se</code> package.</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_weld_probe_enhancements">Weld Probe Enhancements</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>Since the last Alpha releases there were several enhancements to Weld Probe.
-                  If you are not familiar with Weld Probe, check this <a href="http://weld.cdi-spec.org/news/2015/02/05/weld-300Alpha4/">introductory blog post first</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>A new feature of Probe is that, when the development mode is enabled, it now embeds a tiny information bar directly into the application&#8217;s HTML output.
-                  That makes it easy to navigate to Probe directly from the application anytime.
-                  Furthermore, if invocation tracking is enabled, the information bar helps navigate directly to the invocation tree related to the request that rendered the output.</p>
-                  </div>
-                  <div class="imageblock">
-                  <div class="content">
-                  <img src="/images/blog/probe-bar.png" alt="Weld Probe information bar embedded in application&#8217;s HTML output">
-                  </div>
-                  </div>
-                  <div class="paragraph">
-                  <p><br></p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Additionally, the following Probe improvements were implemented:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>tracked invocations are now grouped into a invocation tree instead of being tracked in isolation</p>
-                  </li>
-                  <li>
-                  <p>a special type of edges is now used in the overview graph to represent a "declared by" relation (when a bean declares a producer method or field)</p>
-                  </li>
-                  <li>
-                  <p>Instance&lt;?&gt; injection points are now treated specially - a resolved bean is show as injection point&#8217;s dependency</p>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>&#91; <a href="http://docs.jboss.org/weld/javadoc/3.0/weld-api/org/jboss/weld/experimental/package-frame.html">Experimental API documentation</a> &#93;
-                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12326881">Release notes</a> &#93;
-                  &#91; <a href="https://sourceforge.net/projects/jboss/files/Weld/3.0.0.Alpha8">Distribution</a> &#93;
-                  &#91; Patch for Wildfly
-                  (<a href="http://sourceforge.net/projects/jboss/files/Weld/3.0.0.Alpha8/wildfly-8.2.0.Final-weld-3.0.0.Alpha8-patch.zip/download">8.2</a>,
-                  <a href="http://sourceforge.net/projects/jboss/files/Weld/3.0.0.Alpha8/wildfly-9.0.0.Beta2-weld-3.0.0.Alpha8-patch.zip/download">9 Beta</a>)
-                  &#93;</p>
-                  </div>
-                  </div>
-                  </div>
-                </div>
-                <hr>
-              </div>
               <div class="pagination-links"><a href="/news/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 da3c95d2..4a79f6f0 100644
--- a/news/tags/release/page/7.html
+++ b/news/tags/release/page/7.html
@@ -141,6 +141,160 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2015/04/21/weld-300Alpha8/">Weld 3.0.0.Alpha8</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2015-4-21
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/release">release</a>
+                    ,
+                    <a href="/news/tags/cdi2">cdi2</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Jozef Hartinger
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>Weld 3.0.0.Alpha8 has been released.
+                  The main change is the enhanced API for using Weld in Java SE environment. In addition, this release comes with several weld-probe improvements.</p>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_enhanced_api_for_weld_se">Enhanced API for Weld SE</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>Weld has provided <a href="http://docs.jboss.org/weld/reference/latest-2.2/en-US/html/environments.html#_java_se">support for the Java SE environment</a> for a long time with the weld-se module.
+                  The API provides an easy way for an application to initialize Weld and use it in a standalone mode.
+                  On initialization Weld SE scans the classpath for bean archives with the <code>beans.xml</code> file, similarly to how it&#8217;s done in the Java EE environment.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>In this release we are extending the API further.
+                  This is partially inspired by the current discussion in the CDI expert group where a standardized CDI API for Java SE is being proposed as part of <a href="https://issues.jboss.org/browse/CDI-26">CDI-26</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>The following code snippet shows the new API in action:</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">Weld builder = new Weld()&#x000A;        .disableDiscovery()&#x000A;        .packages(Main.class, Utils.class)&#x000A;        .interceptors(TransactionalInterceptor.class)&#x000A;        .property("org.jboss.weld.construction.relaxed", true);&#x000A;    &#x000A;    try (WeldContainer weld = builder.initialize()) {&#x000A;        MyBean bean = weld.select(MyBean.class).get();&#x000A;        System.out.println(bean.computeResult());&#x000A;    }</code></pre>
+                  </div>
+                  </div>
+                  <div class="paragraph">
+                  <p>There are several new things to notice:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>the <code>Weld</code> class is used as a builder to configure Weld before it is initialized</p>
+                  </li>
+                  <li>
+                  <p>automatic scanning can be disabled</p>
+                  </li>
+                  <li>
+                  <p>instead of scanning, classes or packages can be selected explicitly. All classes in those packages will be managed by Weld</p>
+                  </li>
+                  <li>
+                  <p>interceptors, decorators, extensions and <a href="http://docs.jboss.org/weld/reference/3.0.0.Alpha8/en-US/html/configure.html#_weld_configuration">Weld-specific configuration options</a> can be specified using the builder</p>
+                  </li>
+                  <li>
+                  <p><code>WeldContainer</code> now implements <code>AutoCloseable</code> and can therefore be used in a <code>try-with-resources</code> block. At any time that execution gets outside of the code block, the Weld instance is shut down and all managed instances are safely destroyed.</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>It is also possible to start multiple independent Weld instances:</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">new Weld().disableDiscovery().containerId("one").beanClasses(MyBean.class).initialize();&#x000A;    new Weld().disableDiscovery().containerId("two").beanClasses(OtherBean.class).initialize();&#x000A;    &#x000A;    MyBean bean = WeldContainer.instance("one").select(MyBean.class).get();&#x000A;    System.out.println(bean.computeResult());&#x000A;    &#x000A;    WeldContainer.instance("one").shutdown();&#x000A;    WeldContainer.instance("two").shutdown();</code></pre>
+                  </div>
+                  </div>
+                  <div class="paragraph">
+                  <p>Here, two independent <code>WeldContainer</code> instances are initialized.
+                  Each of them is given a unique ID.
+                  The ID can subsequently be used to obtain a <code>WeldContainer</code> reference in a different place of the code.
+                  One possible use-case this enables is for a library or framework (e.g. a testing framework) to use an embedded instance of Weld internally for its own needs (dependency injection, events, extensibility).
+                  This instance would not interfere with the Weld instance used by the application.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Obviously, automatic classpath scanning can still be used as before:</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">try (WeldContainer weld = new Weld().enableDiscovery().initialize()) {&#x000A;        MyBean bean = weld.select(MyBean.class).get();&#x000A;        System.out.println(bean.computeResult());&#x000A;    }</code></pre>
+                  </div>
+                  </div>
+                  <div class="paragraph">
+                  <p><strong>Update:</strong></p>
+                  </div>
+                  <div class="paragraph">
+                  <p>To play with the new API use the following dependency in you Maven project:</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;dependency&gt;&#x000A;        &lt;groupId&gt;org.jboss.weld.se&lt;/groupId&gt;&#x000A;        &lt;artifactId&gt;weld-se-core&lt;/artifactId&gt;&#x000A;        &lt;version&gt;3.0.0.Alpha8&lt;/version&gt;&#x000A;    &lt;/dependency&gt;</code></pre>
+                  </div>
+                  </div>
+                  <div class="paragraph">
+                  <p>Aforementioned classes are from the <code>org.jboss.weld.environment.se</code> package.</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_weld_probe_enhancements">Weld Probe Enhancements</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>Since the last Alpha releases there were several enhancements to Weld Probe.
+                  If you are not familiar with Weld Probe, check this <a href="http://weld.cdi-spec.org/news/2015/02/05/weld-300Alpha4/">introductory blog post first</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>A new feature of Probe is that, when the development mode is enabled, it now embeds a tiny information bar directly into the application&#8217;s HTML output.
+                  That makes it easy to navigate to Probe directly from the application anytime.
+                  Furthermore, if invocation tracking is enabled, the information bar helps navigate directly to the invocation tree related to the request that rendered the output.</p>
+                  </div>
+                  <div class="imageblock">
+                  <div class="content">
+                  <img src="/images/blog/probe-bar.png" alt="Weld Probe information bar embedded in application&#8217;s HTML output">
+                  </div>
+                  </div>
+                  <div class="paragraph">
+                  <p><br></p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Additionally, the following Probe improvements were implemented:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>tracked invocations are now grouped into a invocation tree instead of being tracked in isolation</p>
+                  </li>
+                  <li>
+                  <p>a special type of edges is now used in the overview graph to represent a "declared by" relation (when a bean declares a producer method or field)</p>
+                  </li>
+                  <li>
+                  <p>Instance&lt;?&gt; injection points are now treated specially - a resolved bean is show as injection point&#8217;s dependency</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="http://docs.jboss.org/weld/javadoc/3.0/weld-api/org/jboss/weld/experimental/package-frame.html">Experimental API documentation</a> &#93;
+                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12326881">Release notes</a> &#93;
+                  &#91; <a href="https://sourceforge.net/projects/jboss/files/Weld/3.0.0.Alpha8">Distribution</a> &#93;
+                  &#91; Patch for Wildfly
+                  (<a href="http://sourceforge.net/projects/jboss/files/Weld/3.0.0.Alpha8/wildfly-8.2.0.Final-weld-3.0.0.Alpha8-patch.zip/download">8.2</a>,
+                  <a href="http://sourceforge.net/projects/jboss/files/Weld/3.0.0.Alpha8/wildfly-9.0.0.Beta2-weld-3.0.0.Alpha8-patch.zip/download">9 Beta</a>)
+                  &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2015/02/25/weld-300Alpha5/">Weld 3.0.0.Alpha5</a>
diff --git a/sitemap.xml b/sitemap.xml
index 2cfd2417..1354663a 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -2,37 +2,37 @@
 <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
   <url>
     <loc>https://weld.cdi-spec.org/bug/</loc>
-    <lastmod>2024-07-03</lastmod>
+    <lastmod>2024-08-27</lastmod>
     <priority>0.5</priority>
     <changefreq>weekly</changefreq>
   </url>
   <url>
     <loc>https://weld.cdi-spec.org/community/</loc>
-    <lastmod>2024-07-03</lastmod>
+    <lastmod>2024-08-27</lastmod>
     <priority>0.5</priority>
     <changefreq>weekly</changefreq>
   </url>
   <url>
     <loc>https://weld.cdi-spec.org/dist/</loc>
-    <lastmod>2024-07-03</lastmod>
+    <lastmod>2024-08-27</lastmod>
     <priority>1</priority>
     <changefreq>daily</changefreq>
   </url>
   <url>
     <loc>https://weld.cdi-spec.org/documentation/</loc>
-    <lastmod>2024-07-03</lastmod>
+    <lastmod>2024-08-27</lastmod>
     <priority>0.5</priority>
     <changefreq>weekly</changefreq>
   </url>
   <url>
     <loc>https://weld.cdi-spec.org/download/</loc>
-    <lastmod>2024-07-03</lastmod>
+    <lastmod>2024-08-27</lastmod>
     <priority>0.5</priority>
     <changefreq>weekly</changefreq>
   </url>
   <url>
     <loc>https://weld.cdi-spec.org/</loc>
-    <lastmod>2024-07-03</lastmod>
+    <lastmod>2024-08-27</lastmod>
     <priority>0.5</priority>
     <changefreq>weekly</changefreq>
   </url>
@@ -582,9 +582,15 @@
     <priority>1</priority>
     <changefreq>weekly</changefreq>
   </url>
+  <url>
+    <loc>https://weld.cdi-spec.org/news/2024/08/27/weld-513Final/</loc>
+    <lastmod>2024-08-27</lastmod>
+    <priority>1</priority>
+    <changefreq>weekly</changefreq>
+  </url>
   <url>
     <loc>https://weld.cdi-spec.org/news/</loc>
-    <lastmod>2024-07-03</lastmod>
+    <lastmod>2024-08-27</lastmod>
     <priority>1</priority>
     <changefreq>daily</changefreq>
   </url>