From 14d771977bb7f62ea1ecdee11b614fad8c0768fa Mon Sep 17 00:00:00 2001
From: Matej Novotny <manovotn@redhat.com>
Date: Wed, 13 Nov 2024 07:48:55 +0000
Subject: [PATCH] Published master to GitHub pages.

---
 dist/index.html                        |  23 ++
 download/index.html                    |  48 +--
 index.html                             |  30 +-
 news.atom                              | 461 ++++++++-----------------
 news/2024/11/13/weld-600CR1/index.html | 269 +++++++++++++++
 news/index.html                        | 139 ++++----
 news/page/10.html                      | 448 +++++++++++++-----------
 news/page/11.html                      | 423 +++++++++++------------
 news/page/12.html                      | 342 +++++++++++-------
 news/page/13.html                      | 211 ++++++-----
 news/page/14.html                      | 136 +++++---
 news/page/15.html                      | 114 +++---
 news/page/16.html                      | 215 ++++--------
 news/page/17.html                      | 220 +++++++-----
 news/page/18.html                      |  95 ++++-
 news/page/19.html                      |  18 +
 news/page/2.html                       | 119 +++----
 news/page/3.html                       | 107 +++---
 news/page/4.html                       | 154 +++------
 news/page/5.html                       | 223 ++++++------
 news/page/6.html                       | 222 ++++++------
 news/page/7.html                       | 298 ++++++----------
 news/page/8.html                       | 317 ++++++++++-------
 news/page/9.html                       | 374 +++++++-------------
 news/tags/release/index.html           | 138 ++++----
 news/tags/release/page/2.html          | 165 ++++-----
 news/tags/release/page/3.html          | 211 +++++------
 news/tags/release/page/4.html          | 242 ++++++-------
 news/tags/release/page/5.html          | 315 ++++++++---------
 news/tags/release/page/6.html          | 361 ++++++++++---------
 news/tags/release/page/7.html          | 183 ++++++++++
 sitemap.xml                            |  20 +-
 32 files changed, 3466 insertions(+), 3175 deletions(-)
 create mode 100644 news/2024/11/13/weld-600CR1/index.html

diff --git a/dist/index.html b/dist/index.html
index dd2eb5a2..50f6b8e7 100644
--- a/dist/index.html
+++ b/dist/index.html
@@ -157,6 +157,29 @@ <h1>Download - binary distribution archive</h1>
                     Download
                   </th>
                 </tr>
+                <tr>
+                  <td class="version">
+                    6.0.0.CR1
+                  </td>
+                  <td>
+                    Preview
+                  </td>
+                  <td>
+                  </td>
+                  <td>
+                    13.11.2024
+                  </td>
+                  <td>
+                    <a href="https://issues.redhat.com/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12429945">
+                      Changelog
+                    </a>
+                  </td>
+                  <td>
+                    <a href="http://download.jboss.org/weld/6.0.0.CR1">
+                      Download
+                    </a>
+                  </td>
+                </tr>
                 <tr>
                   <td class="version">
                     5.1.3.Final
diff --git a/download/index.html b/download/index.html
index 2056c52b..7f6a1146 100644
--- a/download/index.html
+++ b/download/index.html
@@ -207,6 +207,30 @@ <h2>Binary distribution</h2>
                     Download
                   </th>
                 </tr>
+                <tr>
+                  <td class="version">
+                    6.0.0.CR1
+                  </td>
+                  <td>
+                    Preview
+                  </td>
+                  <td>
+                    4.1
+                  </td>
+                  <td>
+                    13.11.2024
+                  </td>
+                  <td>
+                    <a href="https://issues.redhat.com/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12429945">
+                      Changelog
+                    </a>
+                  </td>
+                  <td>
+                    <a href="https://download.jboss.org/weld/6.0.0.CR1">
+                      Download
+                    </a>
+                  </td>
+                </tr>
                 <tr>
                   <td class="version">
                     5.1.3.Final
@@ -429,30 +453,6 @@ <h2>Binary distribution</h2>
                     </a>
                   </td>
                 </tr>
-                <tr>
-                  <td class="version">
-                    5.0.1.Final
-                  </td>
-                  <td>
-                    Final
-                  </td>
-                  <td>
-                    4.0
-                  </td>
-                  <td>
-                    24.06.2022
-                  </td>
-                  <td>
-                    <a href="https://issues.redhat.com/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12385166">
-                      Changelog
-                    </a>
-                  </td>
-                  <td>
-                    <a href="https://download.jboss.org/weld/5.0.1.Final">
-                      Download
-                    </a>
-                  </td>
-                </tr>
               </table>
               <p></p>
               <a href="/dist">
diff --git a/index.html b/index.html
index ee6f0603..7769e297 100644
--- a/index.html
+++ b/index.html
@@ -549,10 +549,10 @@ <h2>
                     <ul class="newsColumn">
                       <li>
                         <h3>
-                          <a href="/news/2024/08/27/weld-513Final/">Weld 5.1.3.Final</a>
+                          <a href="/news/2024/11/13/weld-600CR1/">Weld 6.0.0.CR1</a>
                         </h3>
                         <div class="news-date news-boxed">
-                          2024-8-27
+                          2024-11-13
                           &nbsp;
                           <span class="tags">
                             <i class="fa fa-tags"></i>
@@ -560,16 +560,16 @@ <h3>
                           </span>
                         </div>
                         <p>
-                          Squashing bugs with Weld 5.1.3.Final!
+                          Weld 6.0.0.CR1 is now available
                         </p>
                         <hr>
                       </li>
                       <li>
                         <h3>
-                          <a href="/news/2024/07/03/weld-600Beta4/">Weld 6.0.0.Beta4</a>
+                          <a href="/news/2024/08/27/weld-513Final/">Weld 5.1.3.Final</a>
                         </h3>
                         <div class="news-date news-boxed">
-                          2024-7-3
+                          2024-8-27
                           &nbsp;
                           <span class="tags">
                             <i class="fa fa-tags"></i>
@@ -577,16 +577,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>
@@ -594,16 +594,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>
@@ -611,16 +611,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>
@@ -628,7 +628,7 @@ <h3>
                           </span>
                         </div>
                         <p>
-                          Weld 5.1.2.Final is now available
+                          Weld 6.0.0.Alpha1 is now available
                         </p>
                         <hr>
                       </li>
diff --git a/news.atom b/news.atom
index 85a14e33..b281d8e1 100644
--- a/news.atom
+++ b/news.atom
@@ -2,13 +2,111 @@
 <feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
   <id>https://weld.cdi-spec.org/</id>
   <title>Weld</title>
-  <updated>2024-08-27T14:27:45+00:00</updated>
+  <updated>2024-11-13T07:46:56+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/11/13/weld-600CR1/</id>
+    <title>Weld 6.0.0.CR1</title>
+    <updated>2024-11-13T07:46:56+00:00</updated>
+    <published>2024-11-13T00:00:00+00:00</published>
+    <link href="https://weld.cdi-spec.org/news/2024/11/13/weld-600CR1/" rel="alternate" type="text/html" />
+    <author>
+      <name>Matej Novotny</name>
+    </author>
+    <category term="release"></category>
+    <summary>
+      First version of the Jakarta EE TCKs has finally landed in Central and with that, we have re-enabled all remaining TCK tests and are confident enough to issue a candidate release for Weld 6!
+      
+      
+      Note that both, Weld API and Weld Core artifacts have been released.
+      
+      
+      Here is the list of changes from last Beta:
+      
+      
+      
+      
+      Implement validation for unproxyability of sealed types (WELD-2799)
+      
+      
+      Correct injection into @Resource fields of beans registered through extensions (WELD-2798)
+      
+      
+      Improve the algorithm that determines BeanManager instance for synthetic beans coming from build compatible extensions (WELD-2794)
+      
+      
+      Weld OSGi bundle now correctly exports org.jboss.weld.util.reflection (WELD-2793)
+      
+      
+      Weld OSGi bundle now contains imports for built-in bean...
+    </summary>
+    <content type="html">
+      &lt;div class=&quot;paragraph&quot;&gt;
+      &lt;p&gt;First version of the Jakarta EE TCKs has finally landed in Central and with that, we have re-enabled all remaining TCK tests and are confident enough to issue a candidate release for Weld 6!&lt;/p&gt;
+      &lt;/div&gt;
+      &lt;div class=&quot;paragraph&quot;&gt;
+      &lt;p&gt;Note that both, Weld API and Weld Core artifacts have been released.&lt;/p&gt;
+      &lt;/div&gt;
+      &lt;div class=&quot;paragraph&quot;&gt;
+      &lt;p&gt;Here is the list of changes from last Beta:&lt;/p&gt;
+      &lt;/div&gt;
+      &lt;div class=&quot;ulist&quot;&gt;
+      &lt;ul&gt;
+      &lt;li&gt;
+      &lt;p&gt;Implement validation for unproxyability of sealed types (&lt;a href=&quot;https://issues.redhat.com/browse/WELD-2799&quot;&gt;WELD-2799&lt;/a&gt;)&lt;/p&gt;
+      &lt;/li&gt;
+      &lt;li&gt;
+      &lt;p&gt;Correct injection into &lt;code&gt;@Resource&lt;/code&gt; fields of beans registered through extensions (&lt;a href=&quot;https://issues.redhat.com/browse/WELD-2798&quot;&gt;WELD-2798&lt;/a&gt;)&lt;/p&gt;
+      &lt;/li&gt;
+      &lt;li&gt;
+      &lt;p&gt;Improve the algorithm that determines &lt;code&gt;BeanManager&lt;/code&gt; instance for synthetic beans coming from build compatible extensions (&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;Weld OSGi bundle now correctly exports &lt;code&gt;org.jboss.weld.util.reflection&lt;/code&gt; (&lt;a href=&quot;https://issues.redhat.com/browse/WELD-2793&quot;&gt;WELD-2793&lt;/a&gt;)&lt;/p&gt;
+      &lt;/li&gt;
+      &lt;li&gt;
+      &lt;p&gt;Weld OSGi bundle now contains imports for built-in bean proxies (&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;li&gt;
+      &lt;p&gt;Re-introduce Jakarta EE CDI TCK into continuous integration (&lt;a href=&quot;https://issues.redhat.com/browse/WELD-2778&quot;&gt;WELD-2778&lt;/a&gt;)&lt;/p&gt;
+      &lt;div class=&quot;ulist&quot;&gt;
+      &lt;ul&gt;
+      &lt;li&gt;
+      &lt;p&gt;The TCK artifact in Central is not yet final (it is &lt;code&gt;M1&lt;/code&gt;) but it is enough to make sure Weld passes all related CDI tests with WildFly&lt;/p&gt;
+      &lt;/li&gt;
+      &lt;/ul&gt;
+      &lt;/div&gt;
+      &lt;/li&gt;
+      &lt;li&gt;
+      &lt;p&gt;Fix possible file leak in &lt;code&gt;org.jboss.weld.util.ServiceLoader&lt;/code&gt; (&lt;a href=&quot;https://issues.redhat.com/browse/WELD-2800&quot;&gt;WELD-2800&lt;/a&gt;)&lt;/p&gt;
+      &lt;div class=&quot;ulist&quot;&gt;
+      &lt;ul&gt;
+      &lt;li&gt;
+      &lt;p&gt;This was only reported during GlassFish testing and affected just Windows machines&lt;/p&gt;
+      &lt;/li&gt;
+      &lt;/ul&gt;
+      &lt;/div&gt;
+      &lt;/li&gt;
+      &lt;li&gt;
+      &lt;p&gt;Resolve license conflict of &lt;code&gt;jboss-logging-processor&lt;/code&gt; inside shaded Weld SE JAR (&lt;a href=&quot;https://issues.redhat.com/browse/WELD-2795&quot;&gt;WELD-2795&lt;/a&gt;)&lt;/p&gt;
+      &lt;/li&gt;
+      &lt;/ul&gt;
+      &lt;/div&gt;
+      &lt;div class=&quot;paragraph&quot;&gt;
+      &lt;p&gt;As per usual, please report any issues you discover with this release so that we can squash those bugs.&lt;/p&gt;
+      &lt;/div&gt;
+      &lt;div class=&quot;paragraph&quot;&gt;
+      &lt;p&gt;[ &lt;a href=&quot;https://weld.cdi-spec.org/download/&quot;&gt;Download&lt;/a&gt; ]
+      [ &lt;a href=&quot;http://docs.jboss.org/weld/reference/6.0.0.CR1/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=12429945&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/08/27/weld-513Final/</id>
     <title>Weld 5.1.3.Final</title>
-    <updated>2024-08-27T14:27:45+00:00</updated>
+    <updated>2024-11-13T07:46:56+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>
@@ -109,7 +207,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2024/07/03/weld-600Beta4/</id>
     <title>Weld 6.0.0.Beta4</title>
-    <updated>2024-08-27T14:08:13+00:00</updated>
+    <updated>2024-08-27T14:29:44+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>
@@ -226,7 +324,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2024/02/26/weld-600Beta1/</id>
     <title>Weld 6.0.0.Beta1</title>
-    <updated>2024-08-27T14:08:13+00:00</updated>
+    <updated>2024-08-27T14:29:44+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>
@@ -347,7 +445,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2023/10/26/weld-600Alpha1/</id>
     <title>Weld 6.0.0.Alpha1</title>
-    <updated>2024-08-27T14:08:13+00:00</updated>
+    <updated>2024-08-27T14:29:44+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>
@@ -484,7 +582,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2023/10/05/weld-512Final/</id>
     <title>Weld 5.1.2.Final</title>
-    <updated>2024-08-27T14:08:13+00:00</updated>
+    <updated>2024-08-27T14:29:44+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>
@@ -572,7 +670,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2023/08/09/weld-511SP2/</id>
     <title>Weld 5.1.1.SP2</title>
-    <updated>2024-08-27T14:08:13+00:00</updated>
+    <updated>2024-08-27T14:29:44+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>
@@ -615,7 +713,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2023/07/11/weld-511SP1/</id>
     <title>Weld 5.1.1.SP1</title>
-    <updated>2024-08-27T14:08:13+00:00</updated>
+    <updated>2024-08-27T14:29:44+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>
@@ -679,7 +777,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2023/06/12/weld-511Final/</id>
     <title>Weld 5.1.1.Final</title>
-    <updated>2024-08-27T14:08:13+00:00</updated>
+    <updated>2024-08-27T14:29:44+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>
@@ -768,7 +866,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2022/10/03/weld-510Final/</id>
     <title>Weld 5.1.0.Final</title>
-    <updated>2024-08-27T14:08:13+00:00</updated>
+    <updated>2024-08-27T14:29:44+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>
@@ -860,7 +958,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2022/06/24/weld-501Final/</id>
     <title>Weld 5.0.1.Final</title>
-    <updated>2024-08-27T14:08:13+00:00</updated>
+    <updated>2024-08-27T14:29:44+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>
@@ -935,7 +1033,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2022/06/08/weld-500SP2/</id>
     <title>Weld 5.0.0.SP2</title>
-    <updated>2024-08-27T14:08:13+00:00</updated>
+    <updated>2024-08-27T14:29:44+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>
@@ -980,7 +1078,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2022/05/04/weld-500SP1/</id>
     <title>Weld 5.0.0.SP1</title>
-    <updated>2024-08-27T14:08:13+00:00</updated>
+    <updated>2024-08-27T14:29:44+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>
@@ -1025,7 +1123,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2022/04/29/weld-500Final/</id>
     <title>Weld 5.0.0.Final</title>
-    <updated>2024-08-27T14:08:13+00:00</updated>
+    <updated>2024-08-27T14:29:44+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>
@@ -1108,7 +1206,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2022/03/23/weld-500CR2/</id>
     <title>Weld 5.0.0.CR2</title>
-    <updated>2024-08-27T14:08:13+00:00</updated>
+    <updated>2024-08-27T14:29:44+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>
@@ -1148,7 +1246,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2022/02/23/weld-500CR1/</id>
     <title>Weld 5.0.0.CR1</title>
-    <updated>2024-08-27T14:08:13+00:00</updated>
+    <updated>2024-08-27T14:29:44+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>
@@ -1217,7 +1315,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-08-27T14:08:13+00:00</updated>
+    <updated>2024-08-27T14:29:44+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>
@@ -1314,7 +1412,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2022/01/24/weld-500Beta1/</id>
     <title>Weld 5.0.0.Beta1</title>
-    <updated>2024-08-27T14:08:13+00:00</updated>
+    <updated>2024-08-27T14:29:44+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>
@@ -1625,7 +1723,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-08-27T14:08:13+00:00</updated>
+    <updated>2024-08-27T14:29:44+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>
@@ -1706,7 +1804,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-08-27T14:08:13+00:00</updated>
+    <updated>2024-08-27T14:29:44+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>
@@ -1786,7 +1884,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2021/03/22/weld-401Final/</id>
     <title>Weld 4.0.1.Final</title>
-    <updated>2024-08-27T14:08:13+00:00</updated>
+    <updated>2024-08-27T14:29:44+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>
@@ -1905,7 +2003,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2021/03/18/weld-317Final/</id>
     <title>Weld 3.1.7.Final</title>
-    <updated>2024-08-27T14:08:13+00:00</updated>
+    <updated>2024-08-27T14:29:44+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>
@@ -2019,7 +2117,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2021/01/13/weld-316Final/</id>
     <title>Weld 3.1.6.Final</title>
-    <updated>2024-08-27T14:08:13+00:00</updated>
+    <updated>2024-08-27T14:29:44+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>
@@ -2177,7 +2275,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2020/12/16/weld-400Final/</id>
     <title>Weld 4.0.0.Final</title>
-    <updated>2024-08-27T14:08:13+00:00</updated>
+    <updated>2024-08-27T14:29:44+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>
@@ -2255,7 +2353,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2020/09/18/weld-400Beta1/</id>
     <title>Weld 4.0.0.Beta1</title>
-    <updated>2024-08-27T14:08:13+00:00</updated>
+    <updated>2024-08-27T14:29:44+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>
@@ -2372,7 +2470,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2020/08/12/weld-315Final/</id>
     <title>Weld 3.1.5.Final</title>
-    <updated>2024-08-27T14:08:13+00:00</updated>
+    <updated>2024-08-27T14:29:44+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>
@@ -2510,7 +2608,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-08-27T14:08:13+00:00</updated>
+    <updated>2024-08-27T14:29:44+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>
@@ -2649,7 +2747,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2020/03/28/weld-314Final/</id>
     <title>Weld 3.1.4.Final</title>
-    <updated>2024-08-27T14:08:13+00:00</updated>
+    <updated>2024-08-27T14:29:44+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>
@@ -2761,7 +2859,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2019/11/28/weld-313Final/</id>
     <title>Weld 3.1.3.Final</title>
-    <updated>2024-08-27T14:08:13+00:00</updated>
+    <updated>2024-08-27T14:29:44+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>
@@ -2895,7 +2993,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2019/08/06/weld-312Final/</id>
     <title>Weld 3.1.2.Final</title>
-    <updated>2024-08-27T14:08:13+00:00</updated>
+    <updated>2024-08-27T14:29:44+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>
@@ -3049,7 +3147,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2019/05/07/weld-311Final/</id>
     <title>Weld 3.1.1.Final</title>
-    <updated>2024-08-27T14:08:13+00:00</updated>
+    <updated>2024-08-27T14:29:44+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>
@@ -3182,7 +3280,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2019/02/06/weld-310Final/</id>
     <title>Weld 3.1.0.Final</title>
-    <updated>2024-08-27T14:08:13+00:00</updated>
+    <updated>2024-08-27T14:29:44+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>
@@ -3434,7 +3532,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2018/09/26/weld-248Final/</id>
     <title>Weld 2.4.8.Final</title>
-    <updated>2024-08-27T14:08:13+00:00</updated>
+    <updated>2024-08-27T14:29:44+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>
@@ -3571,7 +3669,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2018/07/26/weld-305Final/</id>
     <title>Weld 3.0.5.Final</title>
-    <updated>2024-08-27T14:08:13+00:00</updated>
+    <updated>2024-08-27T14:29:44+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>
@@ -3735,7 +3833,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2018/07/10/weld-team-changes/</id>
     <title>Weld team changes</title>
-    <updated>2024-08-27T14:08:13+00:00</updated>
+    <updated>2024-08-27T14:29:44+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>
@@ -3784,7 +3882,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2018/04/26/weld-304Final/</id>
     <title>Weld 3.0.4.Final</title>
-    <updated>2024-08-27T14:08:13+00:00</updated>
+    <updated>2024-08-27T14:29:44+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>
@@ -3983,7 +4081,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2018/03/20/weld-247Final/</id>
     <title>Weld 2.4.7.Final</title>
-    <updated>2024-08-27T14:08:13+00:00</updated>
+    <updated>2024-08-27T14:29:44+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>
@@ -4166,7 +4264,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2018/02/09/weld-303Final/</id>
     <title>Weld 3.0.3.Final</title>
-    <updated>2024-08-27T14:08:13+00:00</updated>
+    <updated>2024-08-27T14:29:44+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>
@@ -4301,7 +4399,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2017/12/19/weld-meets-junit5/</id>
     <title>Weld meets JUnit 5</title>
-    <updated>2024-08-27T14:08:13+00:00</updated>
+    <updated>2024-08-27T14:29:44+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>
@@ -4478,7 +4576,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2017/12/18/weld-246Final/</id>
     <title>Weld 2.4.6.Final</title>
-    <updated>2024-08-27T14:08:13+00:00</updated>
+    <updated>2024-08-27T14:29:44+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>
@@ -4657,7 +4755,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2017/11/23/weld-302Final/</id>
     <title>Weld 3.0.2.Final</title>
-    <updated>2024-08-27T14:08:13+00:00</updated>
+    <updated>2024-08-27T14:29:44+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>
@@ -4832,7 +4930,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2017/09/11/weld-245Final/</id>
     <title>Weld 2.4.5.Final</title>
-    <updated>2024-08-27T14:08:13+00:00</updated>
+    <updated>2024-08-27T14:29:44+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>
@@ -4949,7 +5047,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2017/08/25/weld-301Final/</id>
     <title>Weld 3.0.1.Final</title>
-    <updated>2024-08-27T14:08:13+00:00</updated>
+    <updated>2024-08-27T14:29:44+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>
@@ -5100,7 +5198,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2017/08/07/weld-vertx-next/</id>
     <title>Weld Vert.x Next?</title>
-    <updated>2024-08-27T14:08:13+00:00</updated>
+    <updated>2024-08-27T14:29:44+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>
@@ -5359,7 +5457,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2017/06/14/weld-244Final/</id>
     <title>Weld 2.4.4.Final</title>
-    <updated>2024-08-27T14:08:13+00:00</updated>
+    <updated>2024-08-27T14:29:44+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>
@@ -5511,7 +5609,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-08-27T14:08:13+00:00</updated>
+    <updated>2024-08-27T14:29:44+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>
@@ -5829,7 +5927,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-08-27T14:08:13+00:00</updated>
+    <updated>2024-08-27T14:29:44+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>
@@ -6007,7 +6105,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2017/04/07/weld-243Final/</id>
     <title>Weld 2.4.3.Final</title>
-    <updated>2024-08-27T14:08:13+00:00</updated>
+    <updated>2024-08-27T14:29:44+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>
@@ -6135,7 +6233,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2017/03/03/weld-300CR2/</id>
     <title>Weld 3.0.0.CR2</title>
-    <updated>2024-08-27T14:08:13+00:00</updated>
+    <updated>2024-08-27T14:29:44+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>
@@ -6271,7 +6369,7 @@
   <entry>
     <id>https://weld.cdi-spec.org/news/2017/02/02/weld-242Final/</id>
     <title>Weld 2.4.2.Final</title>
-    <updated>2024-08-27T14:08:13+00:00</updated>
+    <updated>2024-08-27T14:29:44+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>
@@ -6386,267 +6484,4 @@
       &lt;/div&gt;
     </content>
   </entry>
-  <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-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>
-      <name>Tomas Remes, Matej Novotny</name>
-    </author>
-    <category term="tips"></category>
-    <summary>
-      Contents
-      
-      Using Weld in JUnit tests
-      Arquillian as the chosen framework for testing
-      Java EE application server
-      Servlet environment
-      Java SE environment
-      Arquillian Weld Embedded container
-      
-      
-      
-      In this follow-up article of our Weld Tips series we are going to focus on testing of CDI/Weld applications.
-      Let&#8217;s discover options for unit testing in the first part and then continue with integration testing.
-      To set things straight - by integration testing we mean testing in some kind of container and hence in certain environment (SE, servlet, full EE server).
-      However, no matter the environment we always make use of Arquillian integration testing framework.
-      
-      
-      Using Weld in JUnit tests
-      
-      
-      Recently we created Weld JUnit extension...
-    </summary>
-    <content type="html">
-      &lt;div id=&quot;toc&quot; class=&quot;toc&quot;&gt;
-      &lt;div id=&quot;toctitle&quot; class=&quot;title&quot;&gt;Contents&lt;/div&gt;
-      &lt;ul class=&quot;sectlevel1&quot;&gt;
-      &lt;li&gt;&lt;a href=&quot;#_using_weld_in_junit_tests&quot;&gt;Using Weld in JUnit tests&lt;/a&gt;&lt;/li&gt;
-      &lt;li&gt;&lt;a href=&quot;#_arquillian_as_the_chosen_framework_for_testing&quot;&gt;Arquillian as the chosen framework for testing&lt;/a&gt;&lt;/li&gt;
-      &lt;li&gt;&lt;a href=&quot;#_java_ee_application_server&quot;&gt;Java EE application server&lt;/a&gt;&lt;/li&gt;
-      &lt;li&gt;&lt;a href=&quot;#_servlet_environment&quot;&gt;Servlet environment&lt;/a&gt;&lt;/li&gt;
-      &lt;li&gt;&lt;a href=&quot;#_java_se_environment&quot;&gt;Java SE environment&lt;/a&gt;&lt;/li&gt;
-      &lt;li&gt;&lt;a href=&quot;#_arquillian_weld_embedded_container&quot;&gt;Arquillian Weld Embedded container&lt;/a&gt;&lt;/li&gt;
-      &lt;/ul&gt;
-      &lt;/div&gt;
-      &lt;div class=&quot;paragraph&quot;&gt;
-      &lt;p&gt;In this follow-up article of our Weld Tips series we are going to focus on testing of CDI/Weld applications.
-      Let’s discover options for unit testing in the first part and then continue with integration testing.
-      To set things straight - by integration testing we mean testing in some kind of container and hence in certain environment (SE, servlet, full EE server).
-      However, no matter the environment we always make use of &lt;a href=&quot;http://arquillian.org/&quot;&gt;Arquillian&lt;/a&gt; integration testing framework.&lt;/p&gt;
-      &lt;/div&gt;
-      &lt;div class=&quot;sect1&quot;&gt;
-      &lt;h2 id=&quot;_using_weld_in_junit_tests&quot;&gt;Using Weld in JUnit tests&lt;/h2&gt;
-      &lt;div class=&quot;sectionbody&quot;&gt;
-      &lt;div class=&quot;paragraph&quot;&gt;
-      &lt;p&gt;Recently we created Weld JUnit extension which uses JUnit4 &lt;code&gt;@Rule&lt;/code&gt; to initialize a Weld SE container before each test method execution. For further information please check following &lt;a href=&quot;https://developer.jboss.org/people/mkouba/blog/2017/01/24/easy-testing-of-cdi-components-with-weld-and-junit4/&quot;&gt;blogpost&lt;/a&gt;.&lt;/p&gt;
-      &lt;/div&gt;
-      &lt;/div&gt;
-      &lt;/div&gt;
-      &lt;div class=&quot;sect1&quot;&gt;
-      &lt;h2 id=&quot;_arquillian_as_the_chosen_framework_for_testing&quot;&gt;Arquillian as the chosen framework for testing&lt;/h2&gt;
-      &lt;div class=&quot;sectionbody&quot;&gt;
-      &lt;div class=&quot;paragraph&quot;&gt;
-      &lt;p&gt;While Arquillian may look complex at first, it is certainly worth it. Here are some of the advantages it gives you:&lt;/p&gt;
-      &lt;/div&gt;
-      &lt;div class=&quot;ulist&quot;&gt;
-      &lt;ul&gt;
-      &lt;li&gt;
-      &lt;p&gt;Allows usage of CDI &lt;code&gt;@javax.inject.Inject&lt;/code&gt; directly in test classes&lt;/p&gt;
-      &lt;/li&gt;
-      &lt;li&gt;
-      &lt;p&gt;Works well with ShrinkWrap making archive creation and deployment a breeze&lt;/p&gt;
-      &lt;div class=&quot;ulist&quot;&gt;
-      &lt;ul&gt;
-      &lt;li&gt;
-      &lt;p&gt;&lt;a href=&quot;http://arquillian.org/guides/shrinkwrap_introduction/&quot;&gt;ShrinkWrap&lt;/a&gt; can create any type of deployment archive (WAR, JAR, even infamous EAR) with exactly the capabilities you wish it to have&lt;/p&gt;
-      &lt;/li&gt;
-      &lt;li&gt;
-      &lt;p&gt;You can use dedicated &lt;code&gt;beans.xml&lt;/code&gt; or &lt;code&gt;@Alternatives&lt;/code&gt; for given test case&lt;/p&gt;
-      &lt;/li&gt;
-      &lt;/ul&gt;
-      &lt;/div&gt;
-      &lt;/li&gt;
-      &lt;li&gt;
-      &lt;p&gt;Portability - allows to write one test and run it on any container&lt;/p&gt;
-      &lt;div class=&quot;ulist&quot;&gt;
-      &lt;ul&gt;
-      &lt;li&gt;
-      &lt;p&gt;Arquillian only needs correct adapter; therefore, combined with Maven profiles this gives you some nice fire power for matrix testing&lt;/p&gt;
-      &lt;/li&gt;
-      &lt;/ul&gt;
-      &lt;/div&gt;
-      &lt;/li&gt;
-      &lt;li&gt;
-      &lt;p&gt;Allows for very complex testing scenarios&lt;/p&gt;
-      &lt;div class=&quot;ulist&quot;&gt;
-      &lt;ul&gt;
-      &lt;li&gt;
-      &lt;p&gt;For instance you can create several deployments which you then manually (if you so wish) deploy/undeploy&lt;/p&gt;
-      &lt;/li&gt;
-      &lt;li&gt;
-      &lt;p&gt;This makes it viable even for cluster testing (session replication, failover scenarios, …​)&lt;/p&gt;
-      &lt;/li&gt;
-      &lt;/ul&gt;
-      &lt;/div&gt;
-      &lt;/li&gt;
-      &lt;li&gt;
-      &lt;p&gt;Can start the application server itself or can just connect to running one&lt;/p&gt;
-      &lt;/li&gt;
-      &lt;/ul&gt;
-      &lt;/div&gt;
-      &lt;div class=&quot;paragraph&quot;&gt;
-      &lt;p&gt;In fact writing tests with Arquillian is quite straightforward. It’s basically about right usage of right annotations. Basic test could like this:
-      [ source, java ]&lt;/p&gt;
-      &lt;/div&gt;
-      &lt;div class=&quot;listingblock&quot;&gt;
-      &lt;div class=&quot;content&quot;&gt;
-      &lt;pre&gt; package org.arquillian.example;
-      
-       import javax.inject.Inject;
-       import org.jboss.arquillian.container.test.api.Deployment;
-       import org.jboss.arquillian.junit.Arquillian;
-       import org.jboss.shrinkwrap.api.ShrinkWrap;
-       import org.jboss.shrinkwrap.api.asset.EmptyAsset;
-       import org.jboss.shrinkwrap.api.spec.JavaArchive;
-       import org.junit.Assert;
-       import org.junit.Test;
-       import org.junit.runner.RunWith;
-      
-       @RunWith(Arquillian.class)
-       public class GreeterTest {
-      
-           // This static method builds the virtual test deployment archive
-           @Deployment
-           public static JavaArchive createDeployment() {
-               return ShrinkWrap.create(JavaArchive.class)
-                   .addClass(Greeter.class)
-                   .addAsManifestResource(EmptyAsset.INSTANCE, &quot;beans.xml&quot;);
-           }
-      
-           @Inject
-           Greeter greeter;
-      
-           @Test
-           public void should_create_greeting() {
-              Assert.assertEquals(&quot;Hello, Earthling!&quot;, greeter.createGreeting(&quot;Earthling&quot;));
-           }
-       }&lt;/pre&gt;
-      &lt;/div&gt;
-      &lt;/div&gt;
-      &lt;div class=&quot;paragraph&quot;&gt;
-      &lt;p&gt;If you are a complete Arquillian rookie, you might want to look at their &lt;a href=&quot;http://arquillian.org/guides/getting_started_rinse_and_repeat/&quot;&gt;Getting started guide&lt;/a&gt;.
-      Should you just need an inspiration, you needn’t look any further than our &lt;a href=&quot;https://github.com/weld/core/tree/master/tests-arquillian/src/test/java/org/jboss/weld/tests&quot;&gt;testsuite&lt;/a&gt;.
-      To support the though of Arquillian usefulness for CDI/Weld testing, we may also point out that even &lt;a href=&quot;https://github.com/cdi-spec/cdi-tck/tree/master/impl/src/main/java/org/jboss/cdi/tck/tests&quot;&gt;CDI TCK tests&lt;/a&gt; use it.&lt;/p&gt;
-      &lt;/div&gt;
-      &lt;div class=&quot;paragraph&quot;&gt;
-      &lt;p&gt;Now, let’s take a look at different environments and then round it up with &lt;a href=&quot;https://github.com/arquillian/arquillian-container-weld&quot;&gt;Arquillian Weld Embedded container&lt;/a&gt;, which can be used in each and every environment.&lt;/p&gt;
-      &lt;/div&gt;
-      &lt;/div&gt;
-      &lt;/div&gt;
-      &lt;div class=&quot;sect1&quot;&gt;
-      &lt;h2 id=&quot;_java_ee_application_server&quot;&gt;Java EE application server&lt;/h2&gt;
-      &lt;div class=&quot;sectionbody&quot;&gt;
-      &lt;div class=&quot;paragraph&quot;&gt;
-      &lt;p&gt;When you want to test your application in Java EE application server you basically need to create your test deployment archive, deploy it, execute the test and undeploy the archive.
-      As stated above, &lt;a href=&quot;http://arquillian.org/modules/shrinkwrap-shrinkwrap/&quot;&gt;ShrinkWrap&lt;/a&gt; covers the archive creation (typically WAR or EAR).
-      When it comes to deployment/undeployment, Arquillian controls that, unless you take the reins and control it yourself - just keep an eye for dangling deployments.
-      You also get to chose between using so called managed container, where Arquillian starts and stops the desired container for you, and remote container where Arquillian tries to connect to already running container.
-      Since we are talking Java EE application server, you can use CDI out of the box.
-      Just pay attention to &lt;a href=&quot;https://docs.jboss.org/author/display/ARQ/Test+run+modes&quot;&gt;test mode&lt;/a&gt; you are using.
-      You can check available Arquillian container adapters &lt;a href=&quot;http://arquillian.org/modules/&quot;&gt;here&lt;/a&gt;.&lt;/p&gt;
-      &lt;/div&gt;
-      &lt;div class=&quot;paragraph&quot;&gt;
-      &lt;p&gt;For example to use Arquillian WildFly Managed container you need to define following dependency:
-      [ source, xml ]&lt;/p&gt;
-      &lt;/div&gt;
-      &lt;div class=&quot;listingblock&quot;&gt;
-      &lt;div class=&quot;content&quot;&gt;
-      &lt;pre&gt;               &amp;lt;dependency&amp;gt;
-                         &amp;lt;groupId&amp;gt;org.wildfly.arquillian&amp;lt;/groupId&amp;gt;
-                         &amp;lt;artifactId&amp;gt;wildfly-arquillian-container-managed&amp;lt;/artifactId&amp;gt;
-                         &amp;lt;version&amp;gt;1.1.0.Final&amp;lt;/version&amp;gt;
-                         &amp;lt;scope&amp;gt;test&amp;lt;/scope&amp;gt;
-                     &amp;lt;/dependency&amp;gt;&lt;/pre&gt;
-      &lt;/div&gt;
-      &lt;/div&gt;
-      &lt;/div&gt;
-      &lt;/div&gt;
-      &lt;div class=&quot;sect1&quot;&gt;
-      &lt;h2 id=&quot;_servlet_environment&quot;&gt;Servlet environment&lt;/h2&gt;
-      &lt;div class=&quot;sectionbody&quot;&gt;
-      &lt;div class=&quot;paragraph&quot;&gt;
-      &lt;p&gt;In basic Servlet environment you need to deploy all the dependencies of Weld Servlet integration (as CDI API, Interceptors API, etc.) to your Servlet container and thus embedded container option could be sufficient.
-      As you can &lt;a href=&quot;http://arquillian.org/modules/&quot;&gt;see&lt;/a&gt; Arquillian offers embedded container adapters for all well known Servlet containers such as Tomcat, Jetty and Undertow.&lt;/p&gt;
-      &lt;/div&gt;
-      &lt;div class=&quot;paragraph&quot;&gt;
-      &lt;p&gt;For example to use Arquillian Embedded Tomcat container you need to define following dependency:
-      [ source, xml ]&lt;/p&gt;
-      &lt;/div&gt;
-      &lt;div class=&quot;listingblock&quot;&gt;
-      &lt;div class=&quot;content&quot;&gt;
-      &lt;pre&gt;               &amp;lt;dependency&amp;gt;
-                          &amp;lt;groupId&amp;gt;org.jboss.arquillian.container&amp;lt;/groupId&amp;gt;
-                          &amp;lt;artifactId&amp;gt;arquillian-tomcat-embedded-8&amp;lt;/artifactId&amp;gt;
-                          &amp;lt;version&amp;gt;1.0.0.CR8&amp;lt;/version&amp;gt;
-                          &amp;lt;scope&amp;gt;test&amp;lt;/scope&amp;gt;
-                      &amp;lt;/dependency&amp;gt;&lt;/pre&gt;
-      &lt;/div&gt;
-      &lt;/div&gt;
-      &lt;/div&gt;
-      &lt;/div&gt;
-      &lt;div class=&quot;sect1&quot;&gt;
-      &lt;h2 id=&quot;_java_se_environment&quot;&gt;Java SE environment&lt;/h2&gt;
-      &lt;div class=&quot;sectionbody&quot;&gt;
-      &lt;div class=&quot;paragraph&quot;&gt;
-      &lt;p&gt;Java SE is not effectively a container, however it could be very handy to have an option to easily configure classpath elements of your test.
-      This is exactly what &lt;a href=&quot;https://github.com/arquillian/arquillian-container-se&quot;&gt;Arquillian container SE&lt;/a&gt; offers.
-      With this extension you can build your test classpath and the test executes remotely over JMX in new isolated JVM process.
-      You can find basic information in &lt;a href=&quot;https://github.com/arquillian/arquillian-container-se/blob/master/README.adoc&quot;&gt;README&lt;/a&gt; or you can take look into already mentioned &lt;a href=&quot;https://github.com/cdi-spec/cdi-tck/tree/master/impl/src/main/java/org/jboss/cdi/tck/tests&quot;&gt;CDI TCK tests&lt;/a&gt; where you can find &lt;a href=&quot;https://github.com/cdi-spec/cdi-tck/blob/master/impl/src/main/java/org/jboss/cdi/tck/TestGroups.java#L100&quot;&gt;SE testgroup&lt;/a&gt; which involves all SE related tests.&lt;/p&gt;
-      &lt;/div&gt;
-      &lt;div class=&quot;paragraph&quot;&gt;
-      &lt;p&gt;The maven dependency for this extension looks like this:
-      [ source, xml ]&lt;/p&gt;
-      &lt;/div&gt;
-      &lt;div class=&quot;listingblock&quot;&gt;
-      &lt;div class=&quot;content&quot;&gt;
-      &lt;pre&gt;               &amp;lt;dependency&amp;gt;
-                         &amp;lt;groupId&amp;gt;org.jboss.arquillian.container&amp;lt;/groupId&amp;gt;
-                         &amp;lt;artifactId&amp;gt;container-se-managed&amp;lt;/artifactId&amp;gt;
-                         &amp;lt;version&amp;gt;1.0.1.Final&amp;lt;/version&amp;gt;
-                     &amp;lt;/dependency&amp;gt;&lt;/pre&gt;
-      &lt;/div&gt;
-      &lt;/div&gt;
-      &lt;/div&gt;
-      &lt;/div&gt;
-      &lt;div class=&quot;sect1&quot;&gt;
-      &lt;h2 id=&quot;_arquillian_weld_embedded_container&quot;&gt;Arquillian Weld Embedded container&lt;/h2&gt;
-      &lt;div class=&quot;sectionbody&quot;&gt;
-      &lt;div class=&quot;paragraph&quot;&gt;
-      &lt;p&gt;First of all - this test container is suitable in situations when you know you don’t need to work with full Java EE application server and you are OK with dummy mock EJB, JTA, JPA etc. services.
-      As stated in the beginning of this article, you can use it for any environment but you have to keep it mind, that other technologies/services will be mocked only.
-      By default, this container operates in SE mode, as you don’t need to mock anything there, but you can use a system property (&lt;code&gt;Denvironment=EE&lt;/code&gt;) or a programmatic approach in order to make it work in other environments.
-      For full list of supported environments, see &lt;a href=&quot;https://github.com/weld/api/blob/master/weld-spi/src/main/java/org/jboss/weld/bootstrap/api/Environments.java&quot;&gt;&lt;code&gt;Environments.java&lt;/code&gt;&lt;/a&gt;.
-      We recommend you to take a glance at &lt;a href=&quot;https://github.com/arquillian/arquillian-container-weld/blob/master/README.adoc&quot;&gt;README&lt;/a&gt; file - especially those few lines about flat deployment structure (this means this container is not very suitable for testing EAR deployments) and configuration property for setting testing environment.&lt;/p&gt;
-      &lt;/div&gt;
-      &lt;div class=&quot;paragraph&quot;&gt;
-      &lt;p&gt;The maven dependency for this container could look like this:
-      [ source, xml ]&lt;/p&gt;
-      &lt;/div&gt;
-      &lt;div class=&quot;listingblock&quot;&gt;
-      &lt;div class=&quot;content&quot;&gt;
-      &lt;pre&gt;               &amp;lt;dependency&amp;gt;
-                          &amp;lt;groupId&amp;gt;org.jboss.arquillian.container&amp;lt;/groupId&amp;gt;
-                          &amp;lt;artifactId&amp;gt;arquillian-weld-embedded&amp;lt;/artifactId&amp;gt;
-                          &amp;lt;version&amp;gt;2.0.0.Beta4&amp;lt;/version&amp;gt;
-                          &amp;lt;scope&amp;gt;test&amp;lt;/scope&amp;gt;
-                      &amp;lt;/dependency&amp;gt;&lt;/pre&gt;
-      &lt;/div&gt;
-      &lt;/div&gt;
-      &lt;/div&gt;
-      &lt;/div&gt;
-    </content>
-  </entry>
 </feed>
diff --git a/news/2024/11/13/weld-600CR1/index.html b/news/2024/11/13/weld-600CR1/index.html
new file mode 100644
index 00000000..42d7673e
--- /dev/null
+++ b/news/2024/11/13/weld-600CR1/index.html
@@ -0,0 +1,269 @@
+<!DOCTYPE html>
+<html>
+  <head>
+    <meta charset="utf-8">
+    <title>
+      Weld: Weld 6.0.0.CR1
+    </title>
+    <meta content="width=device-width, initial-scale=1.0" name="viewport">
+    <meta content="Weld 6.0.0.CR1 is now available" name="description">
+    <link href="/images/weld_icon_32x.ico" rel="shortcut icon" type="image/x-icon">
+    <link href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.5/css/bootstrap.min.css" rel="stylesheet" type="text/css">
+    <link href="https://maxcdn.bootstrapcdn.com/font-awesome/4.4.0/css/font-awesome.min.css" rel="stylesheet" type="text/css">
+    <link href="//static.jboss.org/css/tabzilla.css" media="screen" rel="stylesheet" type="text/css">
+    <link href="https://weld.cdi-spec.org/stylesheets/styles.css" rel="stylesheet" type="text/css">
+    <script src="//static.jboss.org/theme/js/libs/jquery/jquery-1.9.1.min.js" type="text/javascript"></script>
+    <script src="//static.jboss.org/js/_jbossorg-tabzilla.js" type="text/javascript"></script>
+    <!--[if lt IE 9]>
+      <script src="//html5shim.googlecode.com/svn/trunk/html5.js" type="text/javascript"></script>
+    <![endif]-->
+    <link href="https://weld.cdi-spec.org/news.atom" rel="alternate" type="application/atom+xml">
+    <link href="//cdn.jsdelivr.net/highlight.js/8.9.1/styles/hybrid.min.css" rel="stylesheet">
+    <script src="//cdn.jsdelivr.net/highlight.js/8.9.1/highlight.min.js" type="text/javascript"></script>
+    <script>
+      hljs.initHighlightingOnLoad();
+    </script>
+  </head>
+  <body>
+    <div class="container-fluid">
+      <div class="row">
+        <div class="col-md-2 col-sm-3">
+          <div class="sidebar-nav">
+            <div class="navbar navbar-default" role="navigation">
+              <div class="navbar-header">
+                <button ="button" class="navbar-toggle" data-target=".sidebar-navbar-collapse" data-toggle="collapse">
+                  <span class="sr-only">
+                    Toggle navigation
+                  </span>
+                  <span class="icon-bar"></span>
+                  <span class="icon-bar"></span>
+                  <span class="icon-bar"></span>
+                  <span class="icon-bar"></span>
+                </button>
+                <a ="#" class="visible-xs navbar-brand">
+                  <img alt="Weld Logo" src="/images/weld_logo_100x.png">
+                </a>
+              </div>
+              <div class="collapse navbar-collapse sidebar-navbar-collapse">
+                <ul class="nav navbar-nav">
+                  <li>
+                    <a href="/">
+                      <i class="fa fa-home"></i>
+                      &nbsp;Home
+                    </a>
+                  </li>
+                  <li>
+                    <a href="/download">
+                      <i class="fa fa-download"></i>
+                      &nbsp;Download
+                    </a>
+                  </li>
+                  <li>
+                    <a href="/news">
+                      <i class="fa fa-newspaper-o"></i>
+                      &nbsp;News
+                    </a>
+                  </li>
+                  <li>
+                    <a href="https://issues.jboss.org/projects/WELD?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page" target="_blank">
+                      <i class="fa fa-road"></i>
+                      &nbsp;Road Map
+                    </a>
+                  </li>
+                  <li>
+                    <a href="/documentation">
+                      <i class="fa fa-book"></i>
+                      &nbsp;Docs &amp; FAQ
+                    </a>
+                  </li>
+                  <li>
+                    <a href="/news/tags/tips">
+                      <i class="fa fa-lightbulb-o"></i>
+                      &nbsp;Tips and Tricks
+                    </a>
+                  </li>
+                  <li>
+                    <a href="/community">
+                      <i class="fa fa-group"></i>
+                      &nbsp;Community
+                    </a>
+                  </li>
+                  <li>
+                    <a href="http://github.com/weld" target="_blank">
+                      <i class="fa fa-github-alt"></i>
+                      &nbsp;Source Code
+                    </a>
+                  </li>
+                  <li>
+                    <a href="https://issues.jboss.org/browse/WELD#selectedTab=com.atlassian.jira.plugin.system.project%3Asummary-panel" target="_blank">
+                      <i class="fa fa-tasks"></i>
+                      &nbsp;Bug Tracker
+                    </a>
+                  </li>
+                  <li>
+                    <a href="https://twitter.com/jbossweld" target="_blank">
+                      <i class="fa fa-twitter"></i>
+                      &nbsp;Follow @jbossweld
+                    </a>
+                  </li>
+                </ul>
+              </div>
+            </div>
+          </div>
+        </div>
+        <div class="col-md-10 col-sm-9">
+          <div class="row hidden-xs">
+            <div class="dropup">
+              <div id="ajbossproject">
+                A JBoss Project
+              </div>
+              <a class="tabnav-closed" href="#" id="tab">Red Hat</a>
+              <script>
+                window.addEventListener('load', function() {renderTabzilla("Weld", "weld", false )}, false);
+              </script>
+            </div>
+          </div>
+          <div class="row">
+            <div class="col-md-4">
+              <a href="/">
+                <img alt="Weld Logo" class="hidden-xs weld-home-logo" src="/images/weld_logo_450x.png">
+              </a>
+            </div>
+            <div class="col-md-8">
+              <img alt="CDI tagcloud" class="hidden-xs hidden-sm cdi-background" src="/images/CDIbackground.png">
+            </div>
+          </div>
+          <div class="row content-wrapper">
+            <div class="col-md-12">
+              <div class="post">
+                <h1>
+                  Weld 6.0.0.CR1
+                  <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-11-13
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/release">release</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Matej Novotny
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>First version of the Jakarta EE TCKs has finally landed in Central and with that, we have re-enabled all remaining TCK tests and are confident enough to issue a candidate release for Weld 6!</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Note that both, Weld API and Weld Core artifacts have been released.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Here is the list of changes from last Beta:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Implement validation for unproxyability of sealed types (<a href="https://issues.redhat.com/browse/WELD-2799">WELD-2799</a>)</p>
+                  </li>
+                  <li>
+                  <p>Correct injection into <code>@Resource</code> fields of beans registered through extensions (<a href="https://issues.redhat.com/browse/WELD-2798">WELD-2798</a>)</p>
+                  </li>
+                  <li>
+                  <p>Improve the algorithm that determines <code>BeanManager</code> instance for synthetic beans coming from build compatible extensions (<a href="https://issues.redhat.com/browse/WELD-2794">WELD-2794</a>)</p>
+                  </li>
+                  <li>
+                  <p>Weld OSGi bundle now correctly exports <code>org.jboss.weld.util.reflection</code> (<a href="https://issues.redhat.com/browse/WELD-2793">WELD-2793</a>)</p>
+                  </li>
+                  <li>
+                  <p>Weld OSGi bundle now contains imports for built-in bean proxies (<a href="https://issues.redhat.com/browse/WELD-2796">WELD-2796</a>)</p>
+                  </li>
+                  <li>
+                  <p>Re-introduce Jakarta EE CDI TCK into continuous integration (<a href="https://issues.redhat.com/browse/WELD-2778">WELD-2778</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>The TCK artifact in Central is not yet final (it is <code>M1</code>) but it is enough to make sure Weld passes all related CDI tests with WildFly</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Fix possible file leak in <code>org.jboss.weld.util.ServiceLoader</code> (<a href="https://issues.redhat.com/browse/WELD-2800">WELD-2800</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>This was only reported during GlassFish testing and affected just Windows machines</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Resolve license conflict of <code>jboss-logging-processor</code> inside shaded Weld SE JAR (<a href="https://issues.redhat.com/browse/WELD-2795">WELD-2795</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>As per usual, please report any issues you discover with this release so that we can squash those bugs.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="/download/">Download</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/6.0.0.CR1/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=12429945" 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/11/13/weld-600CR1/";
+                            var disqus_developer = null;
+                            var disqus_identifier = "3744a7c1522b8649daf83619f9cf787125e8f739";
+                            (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 8281970b..dcd15174 100644
--- a/news/index.html
+++ b/news/index.html
@@ -141,6 +141,85 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2024/11/13/weld-600CR1/">Weld 6.0.0.CR1</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2024-11-13
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/release">release</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Matej Novotny
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>First version of the Jakarta EE TCKs has finally landed in Central and with that, we have re-enabled all remaining TCK tests and are confident enough to issue a candidate release for Weld 6!</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Note that both, Weld API and Weld Core artifacts have been released.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Here is the list of changes from last Beta:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Implement validation for unproxyability of sealed types (<a href="https://issues.redhat.com/browse/WELD-2799">WELD-2799</a>)</p>
+                  </li>
+                  <li>
+                  <p>Correct injection into <code>@Resource</code> fields of beans registered through extensions (<a href="https://issues.redhat.com/browse/WELD-2798">WELD-2798</a>)</p>
+                  </li>
+                  <li>
+                  <p>Improve the algorithm that determines <code>BeanManager</code> instance for synthetic beans coming from build compatible extensions (<a href="https://issues.redhat.com/browse/WELD-2794">WELD-2794</a>)</p>
+                  </li>
+                  <li>
+                  <p>Weld OSGi bundle now correctly exports <code>org.jboss.weld.util.reflection</code> (<a href="https://issues.redhat.com/browse/WELD-2793">WELD-2793</a>)</p>
+                  </li>
+                  <li>
+                  <p>Weld OSGi bundle now contains imports for built-in bean proxies (<a href="https://issues.redhat.com/browse/WELD-2796">WELD-2796</a>)</p>
+                  </li>
+                  <li>
+                  <p>Re-introduce Jakarta EE CDI TCK into continuous integration (<a href="https://issues.redhat.com/browse/WELD-2778">WELD-2778</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>The TCK artifact in Central is not yet final (it is <code>M1</code>) but it is enough to make sure Weld passes all related CDI tests with WildFly</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Fix possible file leak in <code>org.jboss.weld.util.ServiceLoader</code> (<a href="https://issues.redhat.com/browse/WELD-2800">WELD-2800</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>This was only reported during GlassFish testing and affected just Windows machines</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Resolve license conflict of <code>jboss-logging-processor</code> inside shaded Weld SE JAR (<a href="https://issues.redhat.com/browse/WELD-2795">WELD-2795</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>As per usual, please report any issues you discover with this release so that we can squash those bugs.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="/download/">Download</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/6.0.0.CR1/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=12429945" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2024/08/27/weld-513Final/">Weld 5.1.3.Final</a>
@@ -542,66 +621,6 @@ <h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2023/10/05/weld-512Final/">Weld 5.1.2.Final</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2023-10-5
-                  &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 5.1.2.Final has landed in Central and with it some new bufgixes.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Here is a summary of the changes:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Avoid creation of duplicated thread groups on application re-deploy (<a href="https://issues.redhat.com/browse/WELD-2755">WELD-2755</a>)</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>This could lead to a very tiny memory leak on repeated app re-deploy while on app servers (such as WildFly)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p><code>WeldInitialListener</code> can no longer throw <code>NullPointerException</code> if the application failed to start properly (<a href="https://issues.redhat.com/browse/WELD-2752">WELD-2752</a>)</p>
-                  </li>
-                  <li>
-                  <p><code>WeldManager#getContexts</code> not properly returns empty collection when there is no context for given scope (<a href="https://issues.redhat.com/browse/WELD-2761">WELD-2761</a>)</p>
-                  </li>
-                  <li>
-                  <p>Fix client proxy creation for <code>@Typed</code> beans with package-protected types (<a href="https://issues.redhat.com/browse/WELD-2758">WELD-2758</a>)</p>
-                  </li>
-                  <li>
-                  <p>Weld project now uses unified and automatic formatting and import sorting that happens during build (<a href="https://issues.redhat.com/browse/WELD-2753">WELD-2753</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>As always, if you find further issues with Weld 5, let us know and we&#8217;ll try to help.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>&#91; <a href="/download/">Download</a> &#93;
-                  &#91; <a href="http://docs.jboss.org/weld/reference/5.1.2.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=12411521" 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 dc28b8f8..a8e335bd 100644
--- a/news/page/10.html
+++ b/news/page/10.html
@@ -141,6 +141,256 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2017/05/19/tour-around-weld-3/">Tour around Weld 3</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2017-5-19
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Matej Novotny
+                </div>
+                <p></p>
+                <div class="content">
+                  <div id="toc" class="toc">
+                  <div id="toctitle" class="title">Contents</div>
+                  <ul class="sectlevel1">
+                  <li><a href="#_async_events_and_notification_options">Async Events and Notification Options</a></li>
+                  <li><a href="#_configurators_api">Configurators API</a></li>
+                  <li><a href="#_se_bootstrap_api">SE Bootstrap API</a></li>
+                  <li><a href="#_on_demand_request_context_activation">On-demand Request Context Activation</a></li>
+                  <li><a href="#_observer_method_ordering">Observer Method Ordering</a></li>
+                  <li><a href="#_intercepting_produced_beans">Intercepting Produced Beans</a></li>
+                  <li><a href="#_trimmed_bean_archives">Trimmed Bean Archives</a></li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>This post briefly describes all the main CDI 2.0 features and elaborates on Weld-specific features we added on top of that.
+                  It is not intended as a deep-dive but rather to give you the overall idea of what is going on and what can the new release offer.
+                  So, enough talk, let&#8217;s get the show on the road!</p>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_async_events_and_notification_options">Async Events and Notification Options</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>Up until now, the only way to send events was to do so synchronously.
+                  That meant stopping the work of your current thread to instead occupy it with observer resolution and subsequent notification of observer methods.
+                  Once all that was done, the thread resumed it&#8217;s work.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>With CDI 2.0 there are asynchronous events - a 'fire &amp; forget' way of handling things.
+                  Here is how to fire such and event and how to observe it:</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>[ source, java ]</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre>// nothing new here, plain old Event is used&#x000A;    @Inject Event&lt;Payload&gt; event;&#x000A;    &#x000A;    public void sendAsyncEvent() {&#x000A;        // we use a new fireAsync method for asynchronous events&#x000A;        CompletionStage&lt;Payload&gt; eventResult = event.fireAsync(new Payload()).thenAccept(...);&#x000A;    }&#x000A;    &#x000A;    public void asyncObserver (@ObservesAsync Payload payload){ … }</pre>
+                  </div>
+                  </div>
+                  <div class="paragraph">
+                  <p>Few things to note here - first of all, the return value of <code>fireAsync</code> is <code>CompletionStage</code> allowing you to chain the work for when the event is done.
+                  You can follow-up with more tasks, react on exceptional return value and so on.
+                  Another noticeable detail is that observers which are to be notified have to have <code>@ObservesAsync</code> annotation.
+                  As you might have guessed, an observer can be notified of either synchronous (<code>@Observes</code>) or asynchronous (<code>@ObservesAsync</code>) events but never both!</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Apart from this very basic usage, async events allow you to specify <code>NotificationOptions</code> - an option allowing you to tweak the way notification works.
+                  From CDI perspective, there is currently only one standardized option and that enables usage of custom executors which will be used for notifications.
+                  But the API was designed in a generic way so that implementation can enrich it with its own options.
+                  Weld currently offers two more options - timeout and parallel execution - both of which are well described in <a href="http://docs.jboss.org/weld/reference/3.0.0.Final/en-US/html/events.html#_notification_options" target="_blank" rel="noopener">Weld docs</a>.
+                  And here is a snippet showing it in action:</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>[ source, java ]</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre>public void sendAsyncEventWithOptions() {&#x000A;        // we use a secondary version of fireAsync method with NotificationOptions parameter&#x000A;        event.fireAsync(new Payload(), NotificationOptions.of("weld.async.notification.timeout", 2000));&#x000A;    }</pre>
+                  </div>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_configurators_api">Configurators API</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>Another of the key features are <a href="http://docs.jboss.org/cdi/spec/2.0/cdi-spec.html#configurators" target="blank"><code>Configurators</code></a>.
+                  They are here to ease our work when doing small tweaks in extensions.
+                  Here is a snippet showing how easy it can be to register a new bean in <code>AfterBeanDiscovery</code> using configurator.
+                  You don&#8217;t have to create a new class implementing <code>Bean&lt;X&gt;</code> anymore:</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>[ source, java ]</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre>public void addABean(@Observes AfterBeanDiscovery event) {&#x000A;        // get an instance of BeanConfigurator&#x000A;        event.addBean()&#x000A;          // set the desired data&#x000A;          .types(Foo.class)&#x000A;          .scope(RequestScoped.class)&#x000A;          .addQualifier(Custom.CustomLiteral.INSTANCE);&#x000A;          //finally, add a callback to tell CDI how to instantiate this bean&#x000A;          .produceWith(obj -&gt; new Foo());&#x000A;    }</pre>
+                  </div>
+                  </div>
+                  <div class="paragraph">
+                  <p>Following configurators were added:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p><code>AnnotatedTypeConfigurator</code></p>
+                  </li>
+                  <li>
+                  <p><code>InjectionPointConfigurator</code></p>
+                  </li>
+                  <li>
+                  <p><code>BeanAttributesConfigurator</code></p>
+                  </li>
+                  <li>
+                  <p><code>BeanConfigurator</code></p>
+                  </li>
+                  <li>
+                  <p><code>ObserverMethodConfigurator</code></p>
+                  </li>
+                  <li>
+                  <p><code>ProducerConfigurator</code></p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>On top of that, Weld adds one additional configurator - <a href="http://docs.jboss.org/weld/reference/latest/en-US/html_single/#_weld_enriched_container_lifecycle_events" target="_blank" rel="noopener"><code>InterceptorConfigurator</code></a>.
+                  This one allows you to observe <code>WeldAfterBeanDiscovery</code> and then use this configurator to create and register a custom interceptor from scratch.</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_se_bootstrap_api">SE Bootstrap API</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>A big change in CDI 2.0 is the SE support.
+                  Of course, Weld fans have had this for years now, but it has gone official, so that still counts, right?</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>The official CDI API is very similar to that of Weld, here is how it looks like:</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>[ source, java ]</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre>public void bootBasicContainer() {&#x000A;        SeContainerInitializer initializer = SeContainerInitializer.newInstance();&#x000A;        try (SeContainer container = initializer.initialize()) {&#x000A;            Assert.assertTrue(container.isRunning());&#x000A;        }&#x000A;    }</pre>
+                  </div>
+                  </div>
+                  <div class="paragraph">
+                  <p>This is the very basic way; you can also opt to use synthetic bean archive where you cherry-pick all the beans/interceptors/&#8230;&#8203; in your archive.
+                  <a href="http://docs.jboss.org/cdi/spec/2.0/cdi-spec.html#se_bootstrap" target="_blank" rel="noopener">CDI spec</a> describes this fairly well, so how about we instead shift our attention to what Weld SE offers on top of that?</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>A small reminder of how to boot SE container using pure Weld API:</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>[ source, java ]</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre>public void bootWeldSeContainer() {&#x000A;        Weld weld = new Weld();&#x000A;        try (WeldContainer container = weld.initialize()) {&#x000A;            container.select(FooBean.class).get();&#x000A;        }&#x000A;    }</pre>
+                  </div>
+                  </div>
+                  <div class="paragraph">
+                  <p>One of the things Weld makes easier, is when you want to create a quick extension, but don&#8217;t really want to write a whole new class which you then need to place in <code>META-INF/services</code> or register on bootstrap.
+                  You can easily create a 'synthetic extension' programatically:</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>[ source, java ]</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre>Extension testExtension = ContainerLifecycleObserver.extensionBuilder()&#x000A;        .add(afterBeanDiscovery((e) -&gt; System.out.println("Bean discovery completed!")))&#x000A;        .add(processAnnotatedType().notify((e) -&gt; {&#x000A;                if (e.getAnnotatedType().getJavaClass().getName().startsWith("com.foo")) {&#x000A;                    e.veto();&#x000A;                }&#x000A;            })).build();&#x000A;    &#x000A;    try (WeldContainer container = new Weld().addExtension(testExtension).initialize()) {&#x000A;        // Use the container...&#x000A;    }</pre>
+                  </div>
+                  </div>
+                  <div class="paragraph">
+                  <p>What we just did was to create an extension with two container lifecycle observer methods.
+                  It follows a familiar builder pattern and the body of the observer methods is specified as lambda expression.
+                  Before booting SE container, we register this extension as we would any other.
+                  For more information about this, don&#8217;t hesitate to check our older <a href="http://weld.cdi-spec.org/news/2016/02/08/weld-se-synth-lifecycle-events/">news post</a>.</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_on_demand_request_context_activation">On-demand Request Context Activation</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>Especially in SE (although not only there) you might want to activate a <code>RequestContext</code> manually for certain period of time.
+                  There are two ways to achieve that, first of which is an interceptor - <code>@ActivateRequestContext</code>.
+                  You can use that on either a method or a type (enabling it for all methods).
+                  As you might expect, it will activate the context before executing your method and shut it down afterwards.
+                  The other way is through means of built-in bean named <code>RequestContextController</code>.
+                  This bean can be injected as any other CDI bean and offers to self-explanatory methods: <code>activate</code> and <code>deactivate</code>.
+                  The obvious advantage of this approach is that you can enable the context for an extended period of time.</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_observer_method_ordering">Observer Method Ordering</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>A small but noteworthy improvement to observer methods.
+                  You can not leverage <code>@Priority</code> annotation in observer methods hence ordering them as you wish.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>[ source, java ]</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre>public void observeFirst (@Observes @Priority(1) EventPayload payload) {...}&#x000A;    &#x000A;    public void observeSecond (@Observes @Priority(2) EventPayload payload) {...}</pre>
+                  </div>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_intercepting_produced_beans">Intercepting Produced Beans</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>Up until now, anything you created using producers could not be easily intercepted.
+                  CDI 2.0 allows this for <code>@AroundInvoke</code> interceptors in two ways.
+                  There is a new method on <code>BeanManager</code> named <code>createInterceptionFactory</code> but most of the time you will rather use a built-in bean <code>InterceptionFactory</code> which can be injected as a producer method parameter.
+                  Here is a snippet:</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>[ source, java ]</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre>@Produces&#x000A;    @Dependent&#x000A;    public ProducedBean produceFoo(InterceptionFactory&lt;ProducedBean&gt; factory) {&#x000A;        factory.configure().add(Counter.Literal.INSTANCE);&#x000A;        return factory.createInterceptedInstance(new ProducedBean());&#x000A;    }</pre>
+                  </div>
+                  </div>
+                  <div class="paragraph">
+                  <p>To explain this a bit, we first inject the built-in bean with the type equal to the produced type we wish to intercept.
+                  Then we <code>configure()</code> it, which returns an <code>AnnotatedTypeConfigurator</code> allowing us to add interceptor binding.
+                  Finally, we invoke <code>InterceptionFactory.createInterceptedInstance()</code> which takes a the object we produce as a parameter.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>You can read more about this in <a href="http://docs.jboss.org/cdi/spec/2.0/cdi-spec.html#interception_factory" target="_blank" rel="noopener">this CDI spec chapter</a>.</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_trimmed_bean_archives">Trimmed Bean Archives</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>Last but not least feature we will mention are so called 'trimmed' bean archives.
+                  You can mark an explicit bean archive as trimmed in <code>beans.xml</code> by adding the <code>&lt;/trim&gt;</code> element.
+                  Such bean archive will perform an annotated type discovery as with <code>bean-discovery-mode="all"</code> but all types that don&#8217;t have a bean defining annotation or any scope annotation are then removed from the set of discovered types.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Even in this case, Weld allows you to go one step further and <a href="http://docs.jboss.org/weld/reference/latest/en-US/html/configure.html#veto-types-without-bean-defining-annotation">veto types based on regular expression</a>.
+                  It works on a similar principle but affects your whole application - it processess all types from all bean archives.
+                  Your archives will be scanned as they would be with bean discovery mode <code>all</code> and <code>ProcessAnnotatedType</code> will be fired for all found annotated types.
+                  Then, based on the regular expression you provide, annotated types which do not have a bean defining annotation and match the regular expression will be vetoed.</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>
@@ -595,204 +845,6 @@ <h2 id="_wildfly_patch">WildFly Patch</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2017/02/01/tip4-testing/">Weld Tip 4 - Testing CDI/Weld apps</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2017-2-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>
-                  Tomas Remes, Matej Novotny
-                </div>
-                <p></p>
-                <div class="content">
-                  <div id="toc" class="toc">
-                  <div id="toctitle" class="title">Contents</div>
-                  <ul class="sectlevel1">
-                  <li><a href="#_using_weld_in_junit_tests">Using Weld in JUnit tests</a></li>
-                  <li><a href="#_arquillian_as_the_chosen_framework_for_testing">Arquillian as the chosen framework for testing</a></li>
-                  <li><a href="#_java_ee_application_server">Java EE application server</a></li>
-                  <li><a href="#_servlet_environment">Servlet environment</a></li>
-                  <li><a href="#_java_se_environment">Java SE environment</a></li>
-                  <li><a href="#_arquillian_weld_embedded_container">Arquillian Weld Embedded container</a></li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>In this follow-up article of our Weld Tips series we are going to focus on testing of CDI/Weld applications.
-                  Let&#8217;s discover options for unit testing in the first part and then continue with integration testing.
-                  To set things straight - by integration testing we mean testing in some kind of container and hence in certain environment (SE, servlet, full EE server).
-                  However, no matter the environment we always make use of <a href="http://arquillian.org/">Arquillian</a> integration testing framework.</p>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_using_weld_in_junit_tests">Using Weld in JUnit tests</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>Recently we created Weld JUnit extension which uses JUnit4 <code>@Rule</code> to initialize a Weld SE container before each test method execution. For further information please check following <a href="https://developer.jboss.org/people/mkouba/blog/2017/01/24/easy-testing-of-cdi-components-with-weld-and-junit4/">blogpost</a>.</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_arquillian_as_the_chosen_framework_for_testing">Arquillian as the chosen framework for testing</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>While Arquillian may look complex at first, it is certainly worth it. Here are some of the advantages it gives you:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Allows usage of CDI <code>@javax.inject.Inject</code> directly in test classes</p>
-                  </li>
-                  <li>
-                  <p>Works well with ShrinkWrap making archive creation and deployment a breeze</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p><a href="http://arquillian.org/guides/shrinkwrap_introduction/">ShrinkWrap</a> can create any type of deployment archive (WAR, JAR, even infamous EAR) with exactly the capabilities you wish it to have</p>
-                  </li>
-                  <li>
-                  <p>You can use dedicated <code>beans.xml</code> or <code>@Alternatives</code> for given test case</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Portability - allows to write one test and run it on any container</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Arquillian only needs correct adapter; therefore, combined with Maven profiles this gives you some nice fire power for matrix testing</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Allows for very complex testing scenarios</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>For instance you can create several deployments which you then manually (if you so wish) deploy/undeploy</p>
-                  </li>
-                  <li>
-                  <p>This makes it viable even for cluster testing (session replication, failover scenarios, &#8230;&#8203;)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Can start the application server itself or can just connect to running one</p>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>In fact writing tests with Arquillian is quite straightforward. It&#8217;s basically about right usage of right annotations. Basic test could like this:
-                  [ source, java ]</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre> package org.arquillian.example;&#x000A;    &#x000A;     import javax.inject.Inject;&#x000A;     import org.jboss.arquillian.container.test.api.Deployment;&#x000A;     import org.jboss.arquillian.junit.Arquillian;&#x000A;     import org.jboss.shrinkwrap.api.ShrinkWrap;&#x000A;     import org.jboss.shrinkwrap.api.asset.EmptyAsset;&#x000A;     import org.jboss.shrinkwrap.api.spec.JavaArchive;&#x000A;     import org.junit.Assert;&#x000A;     import org.junit.Test;&#x000A;     import org.junit.runner.RunWith;&#x000A;    &#x000A;     @RunWith(Arquillian.class)&#x000A;     public class GreeterTest {&#x000A;    &#x000A;         // This static method builds the virtual test deployment archive&#x000A;         @Deployment&#x000A;         public static JavaArchive createDeployment() {&#x000A;             return ShrinkWrap.create(JavaArchive.class)&#x000A;                 .addClass(Greeter.class)&#x000A;                 .addAsManifestResource(EmptyAsset.INSTANCE, "beans.xml");&#x000A;         }&#x000A;    &#x000A;         @Inject&#x000A;         Greeter greeter;&#x000A;    &#x000A;         @Test&#x000A;         public void should_create_greeting() {&#x000A;            Assert.assertEquals("Hello, Earthling!", greeter.createGreeting("Earthling"));&#x000A;         }&#x000A;     }</pre>
-                  </div>
-                  </div>
-                  <div class="paragraph">
-                  <p>If you are a complete Arquillian rookie, you might want to look at their <a href="http://arquillian.org/guides/getting_started_rinse_and_repeat/">Getting started guide</a>.
-                  Should you just need an inspiration, you needn&#8217;t look any further than our <a href="https://github.com/weld/core/tree/master/tests-arquillian/src/test/java/org/jboss/weld/tests">testsuite</a>.
-                  To support the though of Arquillian usefulness for CDI/Weld testing, we may also point out that even <a href="https://github.com/cdi-spec/cdi-tck/tree/master/impl/src/main/java/org/jboss/cdi/tck/tests">CDI TCK tests</a> use it.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Now, let&#8217;s take a look at different environments and then round it up with <a href="https://github.com/arquillian/arquillian-container-weld">Arquillian Weld Embedded container</a>, which can be used in each and every environment.</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_java_ee_application_server">Java EE application server</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>When you want to test your application in Java EE application server you basically need to create your test deployment archive, deploy it, execute the test and undeploy the archive.
-                  As stated above, <a href="http://arquillian.org/modules/shrinkwrap-shrinkwrap/">ShrinkWrap</a> covers the archive creation (typically WAR or EAR).
-                  When it comes to deployment/undeployment, Arquillian controls that, unless you take the reins and control it yourself - just keep an eye for dangling deployments.
-                  You also get to chose between using so called managed container, where Arquillian starts and stops the desired container for you, and remote container where Arquillian tries to connect to already running container.
-                  Since we are talking Java EE application server, you can use CDI out of the box.
-                  Just pay attention to <a href="https://docs.jboss.org/author/display/ARQ/Test+run+modes">test mode</a> you are using.
-                  You can check available Arquillian container adapters <a href="http://arquillian.org/modules/">here</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>For example to use Arquillian WildFly Managed container you need to define following dependency:
-                  [ source, xml ]</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre>               &lt;dependency&gt;&#x000A;                       &lt;groupId&gt;org.wildfly.arquillian&lt;/groupId&gt;&#x000A;                       &lt;artifactId&gt;wildfly-arquillian-container-managed&lt;/artifactId&gt;&#x000A;                       &lt;version&gt;1.1.0.Final&lt;/version&gt;&#x000A;                       &lt;scope&gt;test&lt;/scope&gt;&#x000A;                   &lt;/dependency&gt;</pre>
-                  </div>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_servlet_environment">Servlet environment</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>In basic Servlet environment you need to deploy all the dependencies of Weld Servlet integration (as CDI API, Interceptors API, etc.) to your Servlet container and thus embedded container option could be sufficient.
-                  As you can <a href="http://arquillian.org/modules/">see</a> Arquillian offers embedded container adapters for all well known Servlet containers such as Tomcat, Jetty and Undertow.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>For example to use Arquillian Embedded Tomcat container you need to define following dependency:
-                  [ source, xml ]</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre>               &lt;dependency&gt;&#x000A;                        &lt;groupId&gt;org.jboss.arquillian.container&lt;/groupId&gt;&#x000A;                        &lt;artifactId&gt;arquillian-tomcat-embedded-8&lt;/artifactId&gt;&#x000A;                        &lt;version&gt;1.0.0.CR8&lt;/version&gt;&#x000A;                        &lt;scope&gt;test&lt;/scope&gt;&#x000A;                    &lt;/dependency&gt;</pre>
-                  </div>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_java_se_environment">Java SE environment</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>Java SE is not effectively a container, however it could be very handy to have an option to easily configure classpath elements of your test.
-                  This is exactly what <a href="https://github.com/arquillian/arquillian-container-se">Arquillian container SE</a> offers.
-                  With this extension you can build your test classpath and the test executes remotely over JMX in new isolated JVM process.
-                  You can find basic information in <a href="https://github.com/arquillian/arquillian-container-se/blob/master/README.adoc">README</a> or you can take look into already mentioned <a href="https://github.com/cdi-spec/cdi-tck/tree/master/impl/src/main/java/org/jboss/cdi/tck/tests">CDI TCK tests</a> where you can find <a href="https://github.com/cdi-spec/cdi-tck/blob/master/impl/src/main/java/org/jboss/cdi/tck/TestGroups.java#L100">SE testgroup</a> which involves all SE related tests.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>The maven dependency for this extension looks like this:
-                  [ source, xml ]</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre>               &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.1.Final&lt;/version&gt;&#x000A;                   &lt;/dependency&gt;</pre>
-                  </div>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_arquillian_weld_embedded_container">Arquillian Weld Embedded container</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>First of all - this test container is suitable in situations when you know you don&#8217;t need to work with full Java EE application server and you are OK with dummy mock EJB, JTA, JPA etc. services.
-                  As stated in the beginning of this article, you can use it for any environment but you have to keep it mind, that other technologies/services will be mocked only.
-                  By default, this container operates in SE mode, as you don&#8217;t need to mock anything there, but you can use a system property (<code>Denvironment=EE</code>) or a programmatic approach in order to make it work in other environments.
-                  For full list of supported environments, see <a href="https://github.com/weld/api/blob/master/weld-spi/src/main/java/org/jboss/weld/bootstrap/api/Environments.java"><code>Environments.java</code></a>.
-                  We recommend you to take a glance at <a href="https://github.com/arquillian/arquillian-container-weld/blob/master/README.adoc">README</a> file - especially those few lines about flat deployment structure (this means this container is not very suitable for testing EAR deployments) and configuration property for setting testing environment.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>The maven dependency for this container could look like this:
-                  [ source, xml ]</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre>               &lt;dependency&gt;&#x000A;                        &lt;groupId&gt;org.jboss.arquillian.container&lt;/groupId&gt;&#x000A;                        &lt;artifactId&gt;arquillian-weld-embedded&lt;/artifactId&gt;&#x000A;                        &lt;version&gt;2.0.0.Beta4&lt;/version&gt;&#x000A;                        &lt;scope&gt;test&lt;/scope&gt;&#x000A;                    &lt;/dependency&gt;</pre>
-                  </div>
-                  </div>
-                  </div>
-                  </div>
-                </div>
-                <hr>
-              </div>
               <div class="pagination-links"><a href="/news/page/9.html" class="previous-link">Previous</a> <a href="/news/" class="page-link">1</a> <a href="/news/page/2.html" class="page-link">2</a> <span class="skip">...</span><a href="/news/page/9.html" class="page-link">9</a> <span class="current-page">10</span> <a href="/news/page/11.html" class="page-link">11</a> <span class="skip">...</span><a href="/news/page/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 30e9e227..0b068c2d 100644
--- a/news/page/11.html
+++ b/news/page/11.html
@@ -141,6 +141,204 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2017/02/01/tip4-testing/">Weld Tip 4 - Testing CDI/Weld apps</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2017-2-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>
+                  Tomas Remes, Matej Novotny
+                </div>
+                <p></p>
+                <div class="content">
+                  <div id="toc" class="toc">
+                  <div id="toctitle" class="title">Contents</div>
+                  <ul class="sectlevel1">
+                  <li><a href="#_using_weld_in_junit_tests">Using Weld in JUnit tests</a></li>
+                  <li><a href="#_arquillian_as_the_chosen_framework_for_testing">Arquillian as the chosen framework for testing</a></li>
+                  <li><a href="#_java_ee_application_server">Java EE application server</a></li>
+                  <li><a href="#_servlet_environment">Servlet environment</a></li>
+                  <li><a href="#_java_se_environment">Java SE environment</a></li>
+                  <li><a href="#_arquillian_weld_embedded_container">Arquillian Weld Embedded container</a></li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>In this follow-up article of our Weld Tips series we are going to focus on testing of CDI/Weld applications.
+                  Let&#8217;s discover options for unit testing in the first part and then continue with integration testing.
+                  To set things straight - by integration testing we mean testing in some kind of container and hence in certain environment (SE, servlet, full EE server).
+                  However, no matter the environment we always make use of <a href="http://arquillian.org/">Arquillian</a> integration testing framework.</p>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_using_weld_in_junit_tests">Using Weld in JUnit tests</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>Recently we created Weld JUnit extension which uses JUnit4 <code>@Rule</code> to initialize a Weld SE container before each test method execution. For further information please check following <a href="https://developer.jboss.org/people/mkouba/blog/2017/01/24/easy-testing-of-cdi-components-with-weld-and-junit4/">blogpost</a>.</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_arquillian_as_the_chosen_framework_for_testing">Arquillian as the chosen framework for testing</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>While Arquillian may look complex at first, it is certainly worth it. Here are some of the advantages it gives you:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Allows usage of CDI <code>@javax.inject.Inject</code> directly in test classes</p>
+                  </li>
+                  <li>
+                  <p>Works well with ShrinkWrap making archive creation and deployment a breeze</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p><a href="http://arquillian.org/guides/shrinkwrap_introduction/">ShrinkWrap</a> can create any type of deployment archive (WAR, JAR, even infamous EAR) with exactly the capabilities you wish it to have</p>
+                  </li>
+                  <li>
+                  <p>You can use dedicated <code>beans.xml</code> or <code>@Alternatives</code> for given test case</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Portability - allows to write one test and run it on any container</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Arquillian only needs correct adapter; therefore, combined with Maven profiles this gives you some nice fire power for matrix testing</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Allows for very complex testing scenarios</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>For instance you can create several deployments which you then manually (if you so wish) deploy/undeploy</p>
+                  </li>
+                  <li>
+                  <p>This makes it viable even for cluster testing (session replication, failover scenarios, &#8230;&#8203;)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Can start the application server itself or can just connect to running one</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>In fact writing tests with Arquillian is quite straightforward. It&#8217;s basically about right usage of right annotations. Basic test could like this:
+                  [ source, java ]</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre> package org.arquillian.example;&#x000A;    &#x000A;     import javax.inject.Inject;&#x000A;     import org.jboss.arquillian.container.test.api.Deployment;&#x000A;     import org.jboss.arquillian.junit.Arquillian;&#x000A;     import org.jboss.shrinkwrap.api.ShrinkWrap;&#x000A;     import org.jboss.shrinkwrap.api.asset.EmptyAsset;&#x000A;     import org.jboss.shrinkwrap.api.spec.JavaArchive;&#x000A;     import org.junit.Assert;&#x000A;     import org.junit.Test;&#x000A;     import org.junit.runner.RunWith;&#x000A;    &#x000A;     @RunWith(Arquillian.class)&#x000A;     public class GreeterTest {&#x000A;    &#x000A;         // This static method builds the virtual test deployment archive&#x000A;         @Deployment&#x000A;         public static JavaArchive createDeployment() {&#x000A;             return ShrinkWrap.create(JavaArchive.class)&#x000A;                 .addClass(Greeter.class)&#x000A;                 .addAsManifestResource(EmptyAsset.INSTANCE, "beans.xml");&#x000A;         }&#x000A;    &#x000A;         @Inject&#x000A;         Greeter greeter;&#x000A;    &#x000A;         @Test&#x000A;         public void should_create_greeting() {&#x000A;            Assert.assertEquals("Hello, Earthling!", greeter.createGreeting("Earthling"));&#x000A;         }&#x000A;     }</pre>
+                  </div>
+                  </div>
+                  <div class="paragraph">
+                  <p>If you are a complete Arquillian rookie, you might want to look at their <a href="http://arquillian.org/guides/getting_started_rinse_and_repeat/">Getting started guide</a>.
+                  Should you just need an inspiration, you needn&#8217;t look any further than our <a href="https://github.com/weld/core/tree/master/tests-arquillian/src/test/java/org/jboss/weld/tests">testsuite</a>.
+                  To support the though of Arquillian usefulness for CDI/Weld testing, we may also point out that even <a href="https://github.com/cdi-spec/cdi-tck/tree/master/impl/src/main/java/org/jboss/cdi/tck/tests">CDI TCK tests</a> use it.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Now, let&#8217;s take a look at different environments and then round it up with <a href="https://github.com/arquillian/arquillian-container-weld">Arquillian Weld Embedded container</a>, which can be used in each and every environment.</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_java_ee_application_server">Java EE application server</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>When you want to test your application in Java EE application server you basically need to create your test deployment archive, deploy it, execute the test and undeploy the archive.
+                  As stated above, <a href="http://arquillian.org/modules/shrinkwrap-shrinkwrap/">ShrinkWrap</a> covers the archive creation (typically WAR or EAR).
+                  When it comes to deployment/undeployment, Arquillian controls that, unless you take the reins and control it yourself - just keep an eye for dangling deployments.
+                  You also get to chose between using so called managed container, where Arquillian starts and stops the desired container for you, and remote container where Arquillian tries to connect to already running container.
+                  Since we are talking Java EE application server, you can use CDI out of the box.
+                  Just pay attention to <a href="https://docs.jboss.org/author/display/ARQ/Test+run+modes">test mode</a> you are using.
+                  You can check available Arquillian container adapters <a href="http://arquillian.org/modules/">here</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>For example to use Arquillian WildFly Managed container you need to define following dependency:
+                  [ source, xml ]</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre>               &lt;dependency&gt;&#x000A;                       &lt;groupId&gt;org.wildfly.arquillian&lt;/groupId&gt;&#x000A;                       &lt;artifactId&gt;wildfly-arquillian-container-managed&lt;/artifactId&gt;&#x000A;                       &lt;version&gt;1.1.0.Final&lt;/version&gt;&#x000A;                       &lt;scope&gt;test&lt;/scope&gt;&#x000A;                   &lt;/dependency&gt;</pre>
+                  </div>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_servlet_environment">Servlet environment</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>In basic Servlet environment you need to deploy all the dependencies of Weld Servlet integration (as CDI API, Interceptors API, etc.) to your Servlet container and thus embedded container option could be sufficient.
+                  As you can <a href="http://arquillian.org/modules/">see</a> Arquillian offers embedded container adapters for all well known Servlet containers such as Tomcat, Jetty and Undertow.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>For example to use Arquillian Embedded Tomcat container you need to define following dependency:
+                  [ source, xml ]</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre>               &lt;dependency&gt;&#x000A;                        &lt;groupId&gt;org.jboss.arquillian.container&lt;/groupId&gt;&#x000A;                        &lt;artifactId&gt;arquillian-tomcat-embedded-8&lt;/artifactId&gt;&#x000A;                        &lt;version&gt;1.0.0.CR8&lt;/version&gt;&#x000A;                        &lt;scope&gt;test&lt;/scope&gt;&#x000A;                    &lt;/dependency&gt;</pre>
+                  </div>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_java_se_environment">Java SE environment</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>Java SE is not effectively a container, however it could be very handy to have an option to easily configure classpath elements of your test.
+                  This is exactly what <a href="https://github.com/arquillian/arquillian-container-se">Arquillian container SE</a> offers.
+                  With this extension you can build your test classpath and the test executes remotely over JMX in new isolated JVM process.
+                  You can find basic information in <a href="https://github.com/arquillian/arquillian-container-se/blob/master/README.adoc">README</a> or you can take look into already mentioned <a href="https://github.com/cdi-spec/cdi-tck/tree/master/impl/src/main/java/org/jboss/cdi/tck/tests">CDI TCK tests</a> where you can find <a href="https://github.com/cdi-spec/cdi-tck/blob/master/impl/src/main/java/org/jboss/cdi/tck/TestGroups.java#L100">SE testgroup</a> which involves all SE related tests.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>The maven dependency for this extension looks like this:
+                  [ source, xml ]</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre>               &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.1.Final&lt;/version&gt;&#x000A;                   &lt;/dependency&gt;</pre>
+                  </div>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_arquillian_weld_embedded_container">Arquillian Weld Embedded container</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>First of all - this test container is suitable in situations when you know you don&#8217;t need to work with full Java EE application server and you are OK with dummy mock EJB, JTA, JPA etc. services.
+                  As stated in the beginning of this article, you can use it for any environment but you have to keep it mind, that other technologies/services will be mocked only.
+                  By default, this container operates in SE mode, as you don&#8217;t need to mock anything there, but you can use a system property (<code>Denvironment=EE</code>) or a programmatic approach in order to make it work in other environments.
+                  For full list of supported environments, see <a href="https://github.com/weld/api/blob/master/weld-spi/src/main/java/org/jboss/weld/bootstrap/api/Environments.java"><code>Environments.java</code></a>.
+                  We recommend you to take a glance at <a href="https://github.com/arquillian/arquillian-container-weld/blob/master/README.adoc">README</a> file - especially those few lines about flat deployment structure (this means this container is not very suitable for testing EAR deployments) and configuration property for setting testing environment.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>The maven dependency for this container could look like this:
+                  [ source, xml ]</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre>               &lt;dependency&gt;&#x000A;                        &lt;groupId&gt;org.jboss.arquillian.container&lt;/groupId&gt;&#x000A;                        &lt;artifactId&gt;arquillian-weld-embedded&lt;/artifactId&gt;&#x000A;                        &lt;version&gt;2.0.0.Beta4&lt;/version&gt;&#x000A;                        &lt;scope&gt;test&lt;/scope&gt;&#x000A;                    &lt;/dependency&gt;</pre>
+                  </div>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2017/01/23/weld-300CR1/">Weld 3.0.0.CR1</a>
@@ -651,231 +849,6 @@ <h3 id="_bean_identifier_index_optimization">Bean identifier index optimization<
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2016/10/07/tip2-devmode/">Weld Tip 2 - Development Mode</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2016-10-7
-                  &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="#_how_to_enable_the_development_mode">How to enable the development mode</a>
-                  <ul class="sectlevel2">
-                  <li><a href="#_web_application">Web application</a></li>
-                  <li><a href="#_wildfly">WildFly</a></li>
-                  <li><a href="#_weld_se">Weld SE</a></li>
-                  </ul>
-                  </li>
-                  <li><a href="#_how_does_it_actually_work">How does it actually work?</a></li>
-                  <li><a href="#_probe_ui">Probe UI</a></li>
-                  <li><a href="#_what_if_i_dont_have_a_webapp">What if I don&#8217;t have a webapp?</a></li>
-                  <li><a href="#probe-offline">Does it work offline?</a></li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>In this article we&#8217;re going to cover the <a href="http://docs.jboss.org/weld/reference/latest/en-US/html/devmode.html" target="_blank" rel="noopener">special mode for application development</a>.
-                  When enabled, a built-in tool called <strong>Probe</strong> provides a detailed insight into internals of a CDI application.
-                  Probe makes it easy to inspect:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>bean archives</p>
-                  </li>
-                  <li>
-                  <p>beans and their properties such as qualifiers, stereotypes and name</p>
-                  </li>
-                  <li>
-                  <p>a graph of bean dependencies</p>
-                  </li>
-                  <li>
-                  <p>observers and producers declared by beans</p>
-                  </li>
-                  <li>
-                  <p>interceptors and decorators bound to a bean</p>
-                  </li>
-                  <li>
-                  <p>extensions</p>
-                  </li>
-                  <li>
-                  <p>information about current contextual instances</p>
-                  </li>
-                  <li>
-                  <p>tracking of invocations and invocation trees</p>
-                  </li>
-                  <li>
-                  <p>tracking of fired events</p>
-                  </li>
-                  <li>
-                  <p>Weld configuration</p>
-                  </li>
-                  <li>
-                  <p>and more!</p>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>Ok, now let&#8217;s get it working!</p>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_how_to_enable_the_development_mode">How to enable the development mode</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>No surprise that the development mode is <em>DISABLED</em> by default.
-                  It should <em>NEVER</em> be used in production as it may have negative impact on performance and/or represent a potential security risk.
-                  Note that if you successfully enable the development mode you should see <code>Weld Development Mode: ENABLED</code> warning in the log during application bootstrap.
-                  Make sure to disable the development mode before deploying to production!</p>
-                  </div>
-                  <div class="sect2">
-                  <h3 id="_web_application">Web application</h3>
-                  <div class="paragraph">
-                  <p>For any web application, set the Servlet initialization parameter <code>org.jboss.weld.development</code> to <code>true</code>:</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;web-app&gt;&#x000A;        &lt;context-param&gt;&#x000A;            &lt;param-name&gt;org.jboss.weld.development&lt;/param-name&gt;&#x000A;            &lt;param-value&gt;true&lt;/param-value&gt;&#x000A;        &lt;/context-param&gt;&#x000A;    &lt;/web-app&gt;</code></pre>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect2">
-                  <h3 id="_wildfly">WildFly</h3>
-                  <div class="paragraph">
-                  <p>Since WildFly 10 it&#8217;s also possible to enable the Weld development mode globally (i.e. for all the applications deployed) by setting <code>development-mode</code> attribute to true:</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre>/subsystem=weld:write-attribute(name=development-mode,value=true)</pre>
-                  </div>
-                  </div>
-                  <div class="paragraph">
-                  <p>See also <a href="https://docs.jboss.org/author/display/WFLY10/CDI+Reference" target="_blank" rel="noopener">WildFly CDI Reference</a>.</p>
-                  </div>
-                  </div>
-                  <div class="sect2">
-                  <h3 id="_weld_se">Weld SE</h3>
-                  <div class="paragraph">
-                  <p>For a Java SE application, set the system property <code>org.jboss.weld.development</code> to true:</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre>java -cp myCoolApp.jar -Dorg.jboss.weld.development=true com.foo.MyMain</pre>
-                  </div>
-                  </div>
-                  <div class="paragraph">
-                  <p>or use the <code>Weld.property()</code> method:</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">org.jboss.weld.environment.se.Weld;&#x000A;    &#x000A;    public static void main(String[] args) {&#x000A;       Weld weld = new Weld().property("org.jboss.weld.development", true);&#x000A;       try (WeldContainer container = weld.initialize()) {&#x000A;          ...&#x000A;       }&#x000A;    }</code></pre>
-                  </div>
-                  </div>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_how_does_it_actually_work">How does it actually work?</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>Probe collects CDI-related data from your application and then makes the data available through the <em>REST API</em>, eventually through the <em>MXBean</em> of name <code>org.jboss.weld.probe:type=JsonData,context=ID</code> where ID should be replaced with an idenfitier of an application.</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_probe_ui">Probe UI</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>Probe has also a <em>web UI</em> (single-page application) available at <code>{webapp-context-path}/weld-probe</code> (once your webapp starts), e.g. <code><a href="http://localhost:8080/weld-numberguess/weld-probe" class="bare">http://localhost:8080/weld-numberguess/weld-probe</a></code>.
-                  By default, Probe also embeds a tiny information bar directly into the application’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="ulist">
-                  <ul>
-                  <li>
-                  <p>The best place to start is probably the <code>Beans</code> view</p>
-                  </li>
-                  <li>
-                  <p>You may also discover the observer methods declared by an extension</p>
-                  </li>
-                  <li>
-                  <p>Monitor all the fired events and track which observer methods a particular event was delivered to</p>
-                  </li>
-                  <li>
-                  <p>And more&#8230;&#8203;</p>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>We believe the UI is quite intuitive but feel free to ask questions on any channel (irc, gitter, mailing list, etc.).</p>
-                  </div>
-                  <div class="admonitionblock tip">
-                  <table>
-                  <tr>
-                  <td class="icon">
-                  <div class="title">Tip</div>
-                  </td>
-                  <td class="content">
-                  There are some configuration properties which allow to tune or disable Probe features, e.g. to restrict the set of components which will be monitored. See also <a href="http://docs.jboss.org/weld/reference/latest/en-US/html/configure.html#config-dev-mode" target="_blank" rel="noopener">Development Mode Configuration</a>.
-                  </td>
-                  </tr>
-                  </table>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_what_if_i_dont_have_a_webapp">What if I don&#8217;t have a webapp?</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>Nothing is lost!
-                  JMX and <a href="https://github.com/weld/weld-probe-client-adapter" target="_blank" rel="noopener">weld-probe-client-adapter</a> come to rescue.
-                  This "adapter" allows to reuse the default HTML UI even if there is no REST API available (non-web environments).
-                  The adapter either connects to a JMX server (<a href="http://docs.jboss.org/weld/reference/latest/en-US/html/configure.html#config-dev-mode" target="_blank" rel="noopener">Probe JMX support must be enabled</a>) or loads data from an exported file (see also <a href="#probe-offline">Does it work offline?</a>), then starts an embedded Undertow webserver instance and exposes the default HTML client but using the data from the first step.</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="probe-offline">Does it work offline?</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>Sometimes it&#8217;s not possible to inspect a running system (e.g. due to security reasons).
-                  Probe allows to <em>export</em> the collected data and inspect it <em>offline</em>.
-                  There are two ways to export the data:</p>
-                  </div>
-                  <div class="olist arabic">
-                  <ol class="arabic">
-                  <li>
-                  <p>Using REST API: HTTP GET <code>{webapp-context-path}/weld-probe/export</code></p>
-                  </li>
-                  <li>
-                  <p>Configure Probe to export data after deployment (see also <code>org.jboss.weld.probe.exportDataAfterDeployment</code> property in <a href="http://docs.jboss.org/weld/reference/latest/en-US/html/configure.html#config-dev-mode" target="_blank" rel="noopener">Development Mode Configuration</a>)</p>
-                  </li>
-                  </ol>
-                  </div>
-                  <div class="paragraph">
-                  <p>And now use the <a href="https://github.com/weld/weld-probe-client-adapter" target="_blank" rel="noopener">weld-probe-client-adapter</a> again:</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre>java -jar weld-probe-client-adapter-1.0.0.Final-shaded.jar /home/weld/weld-probe-export.zip</pre>
-                  </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 278c3caa..c8d00031 100644
--- a/news/page/12.html
+++ b/news/page/12.html
@@ -141,6 +141,231 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2016/10/07/tip2-devmode/">Weld Tip 2 - Development Mode</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2016-10-7
+                  &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="#_how_to_enable_the_development_mode">How to enable the development mode</a>
+                  <ul class="sectlevel2">
+                  <li><a href="#_web_application">Web application</a></li>
+                  <li><a href="#_wildfly">WildFly</a></li>
+                  <li><a href="#_weld_se">Weld SE</a></li>
+                  </ul>
+                  </li>
+                  <li><a href="#_how_does_it_actually_work">How does it actually work?</a></li>
+                  <li><a href="#_probe_ui">Probe UI</a></li>
+                  <li><a href="#_what_if_i_dont_have_a_webapp">What if I don&#8217;t have a webapp?</a></li>
+                  <li><a href="#probe-offline">Does it work offline?</a></li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>In this article we&#8217;re going to cover the <a href="http://docs.jboss.org/weld/reference/latest/en-US/html/devmode.html" target="_blank" rel="noopener">special mode for application development</a>.
+                  When enabled, a built-in tool called <strong>Probe</strong> provides a detailed insight into internals of a CDI application.
+                  Probe makes it easy to inspect:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>bean archives</p>
+                  </li>
+                  <li>
+                  <p>beans and their properties such as qualifiers, stereotypes and name</p>
+                  </li>
+                  <li>
+                  <p>a graph of bean dependencies</p>
+                  </li>
+                  <li>
+                  <p>observers and producers declared by beans</p>
+                  </li>
+                  <li>
+                  <p>interceptors and decorators bound to a bean</p>
+                  </li>
+                  <li>
+                  <p>extensions</p>
+                  </li>
+                  <li>
+                  <p>information about current contextual instances</p>
+                  </li>
+                  <li>
+                  <p>tracking of invocations and invocation trees</p>
+                  </li>
+                  <li>
+                  <p>tracking of fired events</p>
+                  </li>
+                  <li>
+                  <p>Weld configuration</p>
+                  </li>
+                  <li>
+                  <p>and more!</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>Ok, now let&#8217;s get it working!</p>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_how_to_enable_the_development_mode">How to enable the development mode</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>No surprise that the development mode is <em>DISABLED</em> by default.
+                  It should <em>NEVER</em> be used in production as it may have negative impact on performance and/or represent a potential security risk.
+                  Note that if you successfully enable the development mode you should see <code>Weld Development Mode: ENABLED</code> warning in the log during application bootstrap.
+                  Make sure to disable the development mode before deploying to production!</p>
+                  </div>
+                  <div class="sect2">
+                  <h3 id="_web_application">Web application</h3>
+                  <div class="paragraph">
+                  <p>For any web application, set the Servlet initialization parameter <code>org.jboss.weld.development</code> to <code>true</code>:</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-xml hljs" data-lang="xml">&lt;web-app&gt;&#x000A;        &lt;context-param&gt;&#x000A;            &lt;param-name&gt;org.jboss.weld.development&lt;/param-name&gt;&#x000A;            &lt;param-value&gt;true&lt;/param-value&gt;&#x000A;        &lt;/context-param&gt;&#x000A;    &lt;/web-app&gt;</code></pre>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect2">
+                  <h3 id="_wildfly">WildFly</h3>
+                  <div class="paragraph">
+                  <p>Since WildFly 10 it&#8217;s also possible to enable the Weld development mode globally (i.e. for all the applications deployed) by setting <code>development-mode</code> attribute to true:</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre>/subsystem=weld:write-attribute(name=development-mode,value=true)</pre>
+                  </div>
+                  </div>
+                  <div class="paragraph">
+                  <p>See also <a href="https://docs.jboss.org/author/display/WFLY10/CDI+Reference" target="_blank" rel="noopener">WildFly CDI Reference</a>.</p>
+                  </div>
+                  </div>
+                  <div class="sect2">
+                  <h3 id="_weld_se">Weld SE</h3>
+                  <div class="paragraph">
+                  <p>For a Java SE application, set the system property <code>org.jboss.weld.development</code> to true:</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre>java -cp myCoolApp.jar -Dorg.jboss.weld.development=true com.foo.MyMain</pre>
+                  </div>
+                  </div>
+                  <div class="paragraph">
+                  <p>or use the <code>Weld.property()</code> method:</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">org.jboss.weld.environment.se.Weld;&#x000A;    &#x000A;    public static void main(String[] args) {&#x000A;       Weld weld = new Weld().property("org.jboss.weld.development", true);&#x000A;       try (WeldContainer container = weld.initialize()) {&#x000A;          ...&#x000A;       }&#x000A;    }</code></pre>
+                  </div>
+                  </div>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_how_does_it_actually_work">How does it actually work?</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>Probe collects CDI-related data from your application and then makes the data available through the <em>REST API</em>, eventually through the <em>MXBean</em> of name <code>org.jboss.weld.probe:type=JsonData,context=ID</code> where ID should be replaced with an idenfitier of an application.</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_probe_ui">Probe UI</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>Probe has also a <em>web UI</em> (single-page application) available at <code>{webapp-context-path}/weld-probe</code> (once your webapp starts), e.g. <code><a href="http://localhost:8080/weld-numberguess/weld-probe" class="bare">http://localhost:8080/weld-numberguess/weld-probe</a></code>.
+                  By default, Probe also embeds a tiny information bar directly into the application’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="ulist">
+                  <ul>
+                  <li>
+                  <p>The best place to start is probably the <code>Beans</code> view</p>
+                  </li>
+                  <li>
+                  <p>You may also discover the observer methods declared by an extension</p>
+                  </li>
+                  <li>
+                  <p>Monitor all the fired events and track which observer methods a particular event was delivered to</p>
+                  </li>
+                  <li>
+                  <p>And more&#8230;&#8203;</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>We believe the UI is quite intuitive but feel free to ask questions on any channel (irc, gitter, mailing list, etc.).</p>
+                  </div>
+                  <div class="admonitionblock tip">
+                  <table>
+                  <tr>
+                  <td class="icon">
+                  <div class="title">Tip</div>
+                  </td>
+                  <td class="content">
+                  There are some configuration properties which allow to tune or disable Probe features, e.g. to restrict the set of components which will be monitored. See also <a href="http://docs.jboss.org/weld/reference/latest/en-US/html/configure.html#config-dev-mode" target="_blank" rel="noopener">Development Mode Configuration</a>.
+                  </td>
+                  </tr>
+                  </table>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_what_if_i_dont_have_a_webapp">What if I don&#8217;t have a webapp?</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>Nothing is lost!
+                  JMX and <a href="https://github.com/weld/weld-probe-client-adapter" target="_blank" rel="noopener">weld-probe-client-adapter</a> come to rescue.
+                  This "adapter" allows to reuse the default HTML UI even if there is no REST API available (non-web environments).
+                  The adapter either connects to a JMX server (<a href="http://docs.jboss.org/weld/reference/latest/en-US/html/configure.html#config-dev-mode" target="_blank" rel="noopener">Probe JMX support must be enabled</a>) or loads data from an exported file (see also <a href="#probe-offline">Does it work offline?</a>), then starts an embedded Undertow webserver instance and exposes the default HTML client but using the data from the first step.</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="probe-offline">Does it work offline?</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>Sometimes it&#8217;s not possible to inspect a running system (e.g. due to security reasons).
+                  Probe allows to <em>export</em> the collected data and inspect it <em>offline</em>.
+                  There are two ways to export the data:</p>
+                  </div>
+                  <div class="olist arabic">
+                  <ol class="arabic">
+                  <li>
+                  <p>Using REST API: HTTP GET <code>{webapp-context-path}/weld-probe/export</code></p>
+                  </li>
+                  <li>
+                  <p>Configure Probe to export data after deployment (see also <code>org.jboss.weld.probe.exportDataAfterDeployment</code> property in <a href="http://docs.jboss.org/weld/reference/latest/en-US/html/configure.html#config-dev-mode" target="_blank" rel="noopener">Development Mode Configuration</a>)</p>
+                  </li>
+                  </ol>
+                  </div>
+                  <div class="paragraph">
+                  <p>And now use the <a href="https://github.com/weld/weld-probe-client-adapter" target="_blank" rel="noopener">weld-probe-client-adapter</a> again:</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre>java -jar weld-probe-client-adapter-1.0.0.Final-shaded.jar /home/weld/weld-probe-export.zip</pre>
+                  </div>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2016/10/01/tip1-logging/">Weld Tip 1 - Logging</a>
@@ -642,123 +867,6 @@ <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/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 e8af1364..715e648e 100644
--- a/news/page/13.html
+++ b/news/page/13.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/06/21/update-on-weld-vertx/">Update on weld-vertx</a>
@@ -543,100 +660,6 @@ <h2 id="_wildfly_patch">WildFly Patch</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2016/04/11/weld-meets-vertx/">Weld meets Vert.x</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2016-4-11
-                  &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><a href="http://vertx.io/" target="_blank" rel="noopener">Vert.x</a> defines itself as "a toolkit for building reactive applications on the JVM".
-                  Sounds cool and trendy.
-                  Weld, on the other hand, comes from the Java EE world, based on standards and traditional concepts.
-                  But wait, what if we try to combine the two worlds to get the best of them?</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Vert.x makes use of a light-weight distributed messaging system to allow application components to communicate in a loosely coupled way.
-                  This should sound familiar to all CDI users where beans may produce and consume events as well.
-                  Weld team developed a <a href="https://github.com/weld/weld-vertx">working prototype</a> of Weld/Vert.x integration that allows to automatically register certain observer methods as Vert.x message consumers.
-                  A simple echo message consumer could look like this:</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">import org.jboss.weld.vertx.VertxConsumer;&#x000A;    import org.jboss.weld.vertx.VertxEvent;&#x000A;    &#x000A;    class Foo {&#x000A;        public void echoConsumer(@Observes @VertxConsumer("test.echo.address") VertxEvent event) {&#x000A;            event.setReply(event.getMessageBody());&#x000A;        }&#x000A;    }</code></pre>
-                  </div>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p><code>@VertxConsumer</code> - a qualifier used to specify the address the consumer will be registered to: <code>test.echo.address</code></p>
-                  </li>
-                  <li>
-                  <p><code>VertxEvent</code> - a wrapper of a Vert.x message</p>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>Since we&#8217;re working with a regular observer method, additional parameters may be declared (next to the event parameter).
-                  These parameters are injection points. So it&#8217;s easy to <strong>declare a message consumer dependencies</strong>:</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">public void consumerWithDependencies(@Observes @VertxConsumer("test.dependencies.address") VertxEvent event, CoolService coolService, StatsService statsService) {&#x000A;        coolService.process(event.getMessageBody());&#x000A;        statsService.log(event);&#x000A;    }</code></pre>
-                  </div>
-                  </div>
-                  <div class="admonitionblock note">
-                  <table>
-                  <tr>
-                  <td class="icon">
-                  <div class="title">Note</div>
-                  </td>
-                  <td class="content">
-                  If you inject a dependent bean, it will be destroyed when the invocation completes.
-                  </td>
-                  </tr>
-                  </table>
-                  </div>
-                  <div class="paragraph">
-                  <p>Last but not least - an observer may also <strong>send/publish messages using the Vert.x event bus</strong>:</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">public void consumerStrikesBack(@Observes @VertxConsumer("test.publish.address") VertxEvent event) {&#x000A;        event.messageTo("test.huhu.address").publish("huhu");&#x000A;    }</code></pre>
-                  </div>
-                  </div>
-                  <div class="paragraph">
-                  <p>And how does it work under the hood?
-                  First of all, it&#8217;s necessary to deploy <code>org.jboss.weld.vertx.WeldVerticle</code>.
-                  This <code>Verticle</code> starts Weld SE container and automatically registers <code>org.jboss.weld.vertx.VertxExtension</code> to process all observer methods and detect observers which should become message consumers.
-                  Then a special handler is registered for each address to bridge the event bus to the CDI world.
-                  Handlers use <code>Vertx.executeBlocking()</code> since we expect the code to be blocking.
-                  Later on, whenever a new message is delivered to the handler, <code>Event.fire()</code> is used to notify all relevant observers.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>The prototype is surely missing some features. Nevertheless, it shows the CDI programming model might be applicable to the "reactive" world even if not a first class citizen.
-                  Moreover, the prototype demonstrates the flexibility of the CDI extension mechanism.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>If you want to try it out, you&#8217;ll have to clone the <a href="https://github.com/weld/weld-vertx" class="bare">https://github.com/weld/weld-vertx</a> repository and build it from source (i.e. run <code>mvn clean install</code>).
-                  And if you find it useful feel free to add comments to this blog post. Any feedback is appreciated!</p>
-                  </div>
-                </div>
-                <hr>
-              </div>
               <div class="pagination-links"><a href="/news/page/12.html" class="previous-link">Previous</a> <a href="/news/" class="page-link">1</a> <a href="/news/page/2.html" class="page-link">2</a> <span class="skip">...</span><a href="/news/page/12.html" class="page-link">12</a> <span class="current-page">13</span> <a href="/news/page/14.html" class="page-link">14</a> <span class="skip">...</span><a href="/news/page/18.html" class="page-link">18</a> <a href="/news/page/19.html" class="page-link">19</a> <a href="/news/page/14.html" class="next-link">Next</a> </div>
               <hr>
               <div>
diff --git a/news/page/14.html b/news/page/14.html
index 63b278b4..1fb9be51 100644
--- a/news/page/14.html
+++ b/news/page/14.html
@@ -141,6 +141,100 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2016/04/11/weld-meets-vertx/">Weld meets Vert.x</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2016-4-11
+                  &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><a href="http://vertx.io/" target="_blank" rel="noopener">Vert.x</a> defines itself as "a toolkit for building reactive applications on the JVM".
+                  Sounds cool and trendy.
+                  Weld, on the other hand, comes from the Java EE world, based on standards and traditional concepts.
+                  But wait, what if we try to combine the two worlds to get the best of them?</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Vert.x makes use of a light-weight distributed messaging system to allow application components to communicate in a loosely coupled way.
+                  This should sound familiar to all CDI users where beans may produce and consume events as well.
+                  Weld team developed a <a href="https://github.com/weld/weld-vertx">working prototype</a> of Weld/Vert.x integration that allows to automatically register certain observer methods as Vert.x message consumers.
+                  A simple echo message consumer could look like this:</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">import org.jboss.weld.vertx.VertxConsumer;&#x000A;    import org.jboss.weld.vertx.VertxEvent;&#x000A;    &#x000A;    class Foo {&#x000A;        public void echoConsumer(@Observes @VertxConsumer("test.echo.address") VertxEvent event) {&#x000A;            event.setReply(event.getMessageBody());&#x000A;        }&#x000A;    }</code></pre>
+                  </div>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p><code>@VertxConsumer</code> - a qualifier used to specify the address the consumer will be registered to: <code>test.echo.address</code></p>
+                  </li>
+                  <li>
+                  <p><code>VertxEvent</code> - a wrapper of a Vert.x message</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>Since we&#8217;re working with a regular observer method, additional parameters may be declared (next to the event parameter).
+                  These parameters are injection points. So it&#8217;s easy to <strong>declare a message consumer dependencies</strong>:</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">public void consumerWithDependencies(@Observes @VertxConsumer("test.dependencies.address") VertxEvent event, CoolService coolService, StatsService statsService) {&#x000A;        coolService.process(event.getMessageBody());&#x000A;        statsService.log(event);&#x000A;    }</code></pre>
+                  </div>
+                  </div>
+                  <div class="admonitionblock note">
+                  <table>
+                  <tr>
+                  <td class="icon">
+                  <div class="title">Note</div>
+                  </td>
+                  <td class="content">
+                  If you inject a dependent bean, it will be destroyed when the invocation completes.
+                  </td>
+                  </tr>
+                  </table>
+                  </div>
+                  <div class="paragraph">
+                  <p>Last but not least - an observer may also <strong>send/publish messages using the Vert.x event bus</strong>:</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">public void consumerStrikesBack(@Observes @VertxConsumer("test.publish.address") VertxEvent event) {&#x000A;        event.messageTo("test.huhu.address").publish("huhu");&#x000A;    }</code></pre>
+                  </div>
+                  </div>
+                  <div class="paragraph">
+                  <p>And how does it work under the hood?
+                  First of all, it&#8217;s necessary to deploy <code>org.jboss.weld.vertx.WeldVerticle</code>.
+                  This <code>Verticle</code> starts Weld SE container and automatically registers <code>org.jboss.weld.vertx.VertxExtension</code> to process all observer methods and detect observers which should become message consumers.
+                  Then a special handler is registered for each address to bridge the event bus to the CDI world.
+                  Handlers use <code>Vertx.executeBlocking()</code> since we expect the code to be blocking.
+                  Later on, whenever a new message is delivered to the handler, <code>Event.fire()</code> is used to notify all relevant observers.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>The prototype is surely missing some features. Nevertheless, it shows the CDI programming model might be applicable to the "reactive" world even if not a first class citizen.
+                  Moreover, the prototype demonstrates the flexibility of the CDI extension mechanism.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>If you want to try it out, you&#8217;ll have to clone the <a href="https://github.com/weld/weld-vertx" class="bare">https://github.com/weld/weld-vertx</a> repository and build it from source (i.e. run <code>mvn clean install</code>).
+                  And if you find it useful feel free to add comments to this blog post. Any feedback is appreciated!</p>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2016/02/12/weld-233Final/">Weld 2.3.3.Final</a>
@@ -409,48 +503,6 @@ <h2 id="_notable_bug_fixes_and_enhancements">Notable bug-fixes and enhancements<
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2015/12/04/weld-300Alpha14/">Weld 3.0.0.Alpha14</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2015-12-4
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/release">release</a>
-                    ,
-                    <a href="/news/tags/cdi2">cdi2</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Martin Kouba
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>Weld 3.0.0.Alpha14 the penultimate Weld version for this year has been released into the wild.
-                  It reflects some of the most recent changes in the CDI 2.0 specification, mostly related to asynchronous events.
-                  Moreover, this release also contains quite a lot of enhancements and bugfixes. See also <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12327856">the release details</a>.</p>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_wildfly_patch">WildFly Patch</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>As usual, a <a href="http://download.jboss.org/weld/3.0.0.Alpha14/wildfly-10.0.0.CR4-weld-3.0.0.Alpha14-patch.zip">patch for WildFly</a> is available. This patch not only upgrades Weld within an existing WildFly instance but also upgrades CDI API to 2.0 EDR1. This time the target platform is <strong>WildFly 10.0.0.CR4</strong>.  If you’re not familiar with patching WildFly, check <a href="http://blog.eisele.net/2015/02/playing-with-weld-probe-see-all-of-your.html">Markus&#8217;s tutorial</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>&#91; <a href="http://docs.jboss.org/weld/javadoc/3.0/weld-api/org/jboss/weld/experimental/package-frame.html">Experimental API documentation</a> &#93;
-                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12327856">Release notes</a> &#93;
-                  &#91; <a href="http://download.jboss.org/weld/3.0.0.Alpha14/weld-3.0.0.Alpha14.zip">Distribution</a> &#93;
-                  &#91; <a href="http://download.jboss.org/weld/3.0.0.Alpha14/wildfly-10.0.0.CR4-weld-3.0.0.Alpha14-patch.zip">Patch for Wildfly 10 CR4</a>
-                  &#93;</p>
-                  </div>
-                  </div>
-                  </div>
-                </div>
-                <hr>
-              </div>
               <div class="pagination-links"><a href="/news/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 4735fd2d..bb7b99e9 100644
--- a/news/page/15.html
+++ b/news/page/15.html
@@ -141,6 +141,48 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2015/12/04/weld-300Alpha14/">Weld 3.0.0.Alpha14</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2015-12-4
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/release">release</a>
+                    ,
+                    <a href="/news/tags/cdi2">cdi2</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Martin Kouba
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>Weld 3.0.0.Alpha14 the penultimate Weld version for this year has been released into the wild.
+                  It reflects some of the most recent changes in the CDI 2.0 specification, mostly related to asynchronous events.
+                  Moreover, this release also contains quite a lot of enhancements and bugfixes. See also <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12327856">the release details</a>.</p>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_wildfly_patch">WildFly Patch</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>As usual, a <a href="http://download.jboss.org/weld/3.0.0.Alpha14/wildfly-10.0.0.CR4-weld-3.0.0.Alpha14-patch.zip">patch for WildFly</a> is available. This patch not only upgrades Weld within an existing WildFly instance but also upgrades CDI API to 2.0 EDR1. This time the target platform is <strong>WildFly 10.0.0.CR4</strong>.  If you’re not familiar with patching WildFly, check <a href="http://blog.eisele.net/2015/02/playing-with-weld-probe-see-all-of-your.html">Markus&#8217;s tutorial</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="http://docs.jboss.org/weld/javadoc/3.0/weld-api/org/jboss/weld/experimental/package-frame.html">Experimental API documentation</a> &#93;
+                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12327856">Release notes</a> &#93;
+                  &#91; <a href="http://download.jboss.org/weld/3.0.0.Alpha14/weld-3.0.0.Alpha14.zip">Distribution</a> &#93;
+                  &#91; <a href="http://download.jboss.org/weld/3.0.0.Alpha14/wildfly-10.0.0.CR4-weld-3.0.0.Alpha14-patch.zip">Patch for Wildfly 10 CR4</a>
+                  &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2015/11/25/arq-container-se-CR1/">Arquillian container SE 1.0.0.CR1 released!</a>
@@ -446,78 +488,6 @@ <h2 id="_weld_2_2_16_sp1">Weld 2.2.16.SP1</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2015/09/15/jdk-8u60-problem/">JDK 8u60 reveals a problem in Weld</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2015-9-15
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/bug">bug</a>
-                    ,
-                    <a href="/news/tags/jdk">jdk</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Martin Kouba
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>Recently released <strong>JDK 8u60</strong> has revealed a problem in Weld where not all synthetic members were ignored correctly.
-                  This has been fixed in <strong>2.2.16.Final</strong>, <strong>2.3.0.CR2</strong> and <strong>3.0.0.Alpha14</strong> (not released yet).
-                  However, if not using a lambda referencing an event/disposed parameter inside an observer/disposer method, your application is most probably not affected.
-                  See also <a href="https://issues.jboss.org/browse/WELD-2019">the related issue - WELD-2019</a>.</p>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_use_case">Use case</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>If there is a lambda referencing an event/disposed parameter inside an observer/disposer method, the compiler creates a synthetic method with the event parameter as one of the method parameters. Since 8u60 the parameter annotations are preserved even for the synthetic method.
-                  And so Weld incorrectly recognizes these synthetic methods as observer/disposer methods.</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_symptoms">Symptoms</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>You may get <code>WELD-000409: Observer method for container lifecycle event can only&#8230;&#8203;</code> if using such a lambda in an extension or even <code>WELD-001408 Unsatisfied dependencies for type&#8230;&#8203;</code> if using such a lambda in a regular observer and the lambda is using more references (i.e. not only event/disposed parameter) - these are also the method parameters of the synthetic method, and in CDI these additional parameters are injection points.</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_example">Example</h2>
-                  <div class="sectionbody">
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">class Foo {&#x000A;      void observe(@Observes @Juicy String payload) {&#x000A;        Arrays.asList("foo").stream().filter((s) -&gt; s.equals(payload));&#x000A;      }&#x000A;    }</code></pre>
-                  </div>
-                  </div>
-                  <div class="paragraph">
-                  <p>A synthetic method is created for the lambda and the event parameter is passed as a method parameter. The annotations are preserved.
-                  As a result Weld creates two observer methods having the same event parameter: <code>@Observes @Juicy String payload</code>.</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_workaround">Workaround</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>Instead of the event parameter reference use an additional local variable with the same value assigned:</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">public void observe(@Observes @Juicy String payload) {&#x000A;       String p = payload;&#x000A;       Arrays.asList("foo").stream().filter((s) -&gt; s.equals(p));&#x000A;    }</code></pre>
-                  </div>
-                  </div>
-                  </div>
-                  </div>
-                </div>
-                <hr>
-              </div>
               <div class="pagination-links"><a href="/news/page/14.html" class="previous-link">Previous</a> <a href="/news/" class="page-link">1</a> <a href="/news/page/2.html" class="page-link">2</a> <span class="skip">...</span><a href="/news/page/14.html" class="page-link">14</a> <span class="current-page">15</span> <a href="/news/page/16.html" class="page-link">16</a> <span class="skip">...</span><a href="/news/page/18.html" class="page-link">18</a> <a href="/news/page/19.html" class="page-link">19</a> <a href="/news/page/16.html" class="next-link">Next</a> </div>
               <hr>
               <div>
diff --git a/news/page/16.html b/news/page/16.html
index 1d00f658..6bb807f1 100644
--- a/news/page/16.html
+++ b/news/page/16.html
@@ -141,6 +141,78 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2015/09/15/jdk-8u60-problem/">JDK 8u60 reveals a problem in Weld</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2015-9-15
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/bug">bug</a>
+                    ,
+                    <a href="/news/tags/jdk">jdk</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Martin Kouba
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>Recently released <strong>JDK 8u60</strong> has revealed a problem in Weld where not all synthetic members were ignored correctly.
+                  This has been fixed in <strong>2.2.16.Final</strong>, <strong>2.3.0.CR2</strong> and <strong>3.0.0.Alpha14</strong> (not released yet).
+                  However, if not using a lambda referencing an event/disposed parameter inside an observer/disposer method, your application is most probably not affected.
+                  See also <a href="https://issues.jboss.org/browse/WELD-2019">the related issue - WELD-2019</a>.</p>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_use_case">Use case</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>If there is a lambda referencing an event/disposed parameter inside an observer/disposer method, the compiler creates a synthetic method with the event parameter as one of the method parameters. Since 8u60 the parameter annotations are preserved even for the synthetic method.
+                  And so Weld incorrectly recognizes these synthetic methods as observer/disposer methods.</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_symptoms">Symptoms</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>You may get <code>WELD-000409: Observer method for container lifecycle event can only&#8230;&#8203;</code> if using such a lambda in an extension or even <code>WELD-001408 Unsatisfied dependencies for type&#8230;&#8203;</code> if using such a lambda in a regular observer and the lambda is using more references (i.e. not only event/disposed parameter) - these are also the method parameters of the synthetic method, and in CDI these additional parameters are injection points.</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_example">Example</h2>
+                  <div class="sectionbody">
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">class Foo {&#x000A;      void observe(@Observes @Juicy String payload) {&#x000A;        Arrays.asList("foo").stream().filter((s) -&gt; s.equals(payload));&#x000A;      }&#x000A;    }</code></pre>
+                  </div>
+                  </div>
+                  <div class="paragraph">
+                  <p>A synthetic method is created for the lambda and the event parameter is passed as a method parameter. The annotations are preserved.
+                  As a result Weld creates two observer methods having the same event parameter: <code>@Observes @Juicy String payload</code>.</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_workaround">Workaround</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>Instead of the event parameter reference use an additional local variable with the same value assigned:</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">public void observe(@Observes @Juicy String payload) {&#x000A;       String p = payload;&#x000A;       Arrays.asList("foo").stream().filter((s) -&gt; s.equals(p));&#x000A;    }</code></pre>
+                  </div>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2015/09/08/weld-team-changes/">Weld team changes</a>
@@ -650,149 +722,6 @@ <h2 id="_relaxed_construction">Relaxed construction</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2015/02/05/weld-300Alpha4/">Weld 3.0.0.Alpha4</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2015-2-5
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/release">release</a>
-                    ,
-                    <a href="/news/tags/cdi2">cdi2</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Jozef Hartinger
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>Here we are again with the next Alpha release of Weld 3.
-                  This time there are no additional CDI 2.0 previews.
-                  Instead, this release contains multiple performance improvements, enables <code>@Asynchronous</code>
-                  calls to be implemented simply with CDI interceptors and most importantly, it comes with
-                  <strong>weld-probe</strong>.</p>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_weld_probe">Weld Probe</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>Why isn&#8217;t my field injected?
-                  Why isn&#8217;t my interceptor triggered?
-                  What extensions do third-party libraries register?</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Have you ever found yourself asking a similar question?
-                  Making Weld developer-friendly and helpful in troubleshooting is our priority.
-                  Yet, similar problems still occur sometimes.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>But we can do event better! In Alpha4 of Weld 3 we are introducing a new tool called <strong>Weld Probe</strong>.
-                  Probe is a built-in tool that provides a detailed view into internals of a CDI application.
-                  Weld Probe has a web UI and is provided out-of-the-box.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Probe makes it easy to inspect:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>beans, their properties such as qualifiers, stereotypes and name</p>
-                  </li>
-                  <li>
-                  <p>a graph of bean dependencies</p>
-                  </li>
-                  <li>
-                  <p>observers and producers declared by beans</p>
-                  </li>
-                  <li>
-                  <p>interceptors and decorators bound to a bean</p>
-                  </li>
-                  <li>
-                  <p>extensions</p>
-                  </li>
-                  <li>
-                  <p>information about current contextual instances</p>
-                  </li>
-                  <li>
-                  <p>tracking of invocations and invocation trees</p>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>Plus more addons are planned in future.</p>
-                  </div>
-                  <div class="imageblock">
-                  <div class="content">
-                  <img src="https://developer.jboss.org/servlet/JiveServlet/showImage/38-5641-24345/probe_bean_detail.png" alt="Weld Probe Screenshot">
-                  </div>
-                  </div>
-                  <div class="paragraph">
-                  <p>To try probe all that needs to be done is to upgrade to Alpha4, enable the development mode and point your browser to the URL
-                  of your CDI application plus <code>/weld-probe</code> suffix.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>For more thorough overview of what Probe provides see
-                  <a href="http://goo.gl/ICQrRA">Martin&#8217;s blog post</a> or the
-                  <a href="http://docs.jboss.org/weld/reference/3.0.0.Alpha4/en-US/html/devmode.html#_probe">reference documentation</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Bear in mind that Probe is still work in progress and that this early preview may have defects
-                  here and there.</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_implementing_asynchronous_using_cdi_interceptor">Implementing @Asynchronous using CDI interceptor</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>It <strong>is</strong> possible to implement a substitute for EJB <code>@Asynchronous</code> method calls using CDI interceptors.
-                  Arjan Tijms recently <a href="http://jdevelopment.nl/cdi-based-asynchronous-alternative/">blogged about his solution</a>
-                  A similar one can be found in
-                  <a href="https://github.com/weld/core/blob/master/tests-arquillian/src/test/java/org/jboss/weld/tests/interceptors/thread/async/AsyncInterceptor.java">Weld&#8217;s testsuite</a>.
-                  Long story short: This would not work smoothly until now because of a limitation in Weld. This limitation is now gone in Alpha4.</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_performance">Performance</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>This release integrates various runtime performance improvements mainly around bean instance construction,
-                  producer and observer method invocation.</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_next">Next</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>Weld 3.0.0.Alpha5 is planned in 3 weeks time from now, with some more CDI 2.0 previews.
-                  We are going to continue releasing Alpha versions of Weld 3.0 roughly every 3 weeks until
-                  the early draft of CDI 2.0, which should happen sometime in March.
-                  At that point, we&#8217;ll move to Beta releases.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>In the meantime, we&#8217;d like to hear your feedback on Probe or on Weld 3.0 Alpha releases in general.
-                  Feel free to use our <a href="https://community.jboss.org/en/weld?view=discussions">forums</a> or <a href="http://webchat.freenode.net/?channels=weld-dev">#weld-dev on freenode</a></p>
-                  </div>
-                  <div class="paragraph">
-                  <p>&#91; <a href="http://docs.jboss.org/weld/javadoc/3.0/weld-api/org/jboss/weld/experimental/package-frame.html">Experimental API documentation</a> &#93;
-                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12326166">Release notes</a> &#93;
-                  &#91; <a href="https://sourceforge.net/projects/jboss/files/Weld/3.0.0.Alpha4">Distribution</a> &#93;
-                  &#91; Patch for Wildfly
-                  (<a href="http://sourceforge.net/projects/jboss/files/Weld/3.0.0.Alpha4/wildfly-8.2.0.Final-weld-3.0.0.Alpha4-patch.zip/download">8.2</a>,
-                  <a href="http://sourceforge.net/projects/jboss/files/Weld/3.0.0.Alpha4/wildfly-9.0.0.Alpha1-weld-3.0.0.Alpha4-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 0bbba1a6..f615abab 100644
--- a/news/page/17.html
+++ b/news/page/17.html
@@ -141,6 +141,149 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2015/02/05/weld-300Alpha4/">Weld 3.0.0.Alpha4</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2015-2-5
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/release">release</a>
+                    ,
+                    <a href="/news/tags/cdi2">cdi2</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Jozef Hartinger
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>Here we are again with the next Alpha release of Weld 3.
+                  This time there are no additional CDI 2.0 previews.
+                  Instead, this release contains multiple performance improvements, enables <code>@Asynchronous</code>
+                  calls to be implemented simply with CDI interceptors and most importantly, it comes with
+                  <strong>weld-probe</strong>.</p>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_weld_probe">Weld Probe</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>Why isn&#8217;t my field injected?
+                  Why isn&#8217;t my interceptor triggered?
+                  What extensions do third-party libraries register?</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Have you ever found yourself asking a similar question?
+                  Making Weld developer-friendly and helpful in troubleshooting is our priority.
+                  Yet, similar problems still occur sometimes.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>But we can do event better! In Alpha4 of Weld 3 we are introducing a new tool called <strong>Weld Probe</strong>.
+                  Probe is a built-in tool that provides a detailed view into internals of a CDI application.
+                  Weld Probe has a web UI and is provided out-of-the-box.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Probe makes it easy to inspect:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>beans, their properties such as qualifiers, stereotypes and name</p>
+                  </li>
+                  <li>
+                  <p>a graph of bean dependencies</p>
+                  </li>
+                  <li>
+                  <p>observers and producers declared by beans</p>
+                  </li>
+                  <li>
+                  <p>interceptors and decorators bound to a bean</p>
+                  </li>
+                  <li>
+                  <p>extensions</p>
+                  </li>
+                  <li>
+                  <p>information about current contextual instances</p>
+                  </li>
+                  <li>
+                  <p>tracking of invocations and invocation trees</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>Plus more addons are planned in future.</p>
+                  </div>
+                  <div class="imageblock">
+                  <div class="content">
+                  <img src="https://developer.jboss.org/servlet/JiveServlet/showImage/38-5641-24345/probe_bean_detail.png" alt="Weld Probe Screenshot">
+                  </div>
+                  </div>
+                  <div class="paragraph">
+                  <p>To try probe all that needs to be done is to upgrade to Alpha4, enable the development mode and point your browser to the URL
+                  of your CDI application plus <code>/weld-probe</code> suffix.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>For more thorough overview of what Probe provides see
+                  <a href="http://goo.gl/ICQrRA">Martin&#8217;s blog post</a> or the
+                  <a href="http://docs.jboss.org/weld/reference/3.0.0.Alpha4/en-US/html/devmode.html#_probe">reference documentation</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Bear in mind that Probe is still work in progress and that this early preview may have defects
+                  here and there.</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_implementing_asynchronous_using_cdi_interceptor">Implementing @Asynchronous using CDI interceptor</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>It <strong>is</strong> possible to implement a substitute for EJB <code>@Asynchronous</code> method calls using CDI interceptors.
+                  Arjan Tijms recently <a href="http://jdevelopment.nl/cdi-based-asynchronous-alternative/">blogged about his solution</a>
+                  A similar one can be found in
+                  <a href="https://github.com/weld/core/blob/master/tests-arquillian/src/test/java/org/jboss/weld/tests/interceptors/thread/async/AsyncInterceptor.java">Weld&#8217;s testsuite</a>.
+                  Long story short: This would not work smoothly until now because of a limitation in Weld. This limitation is now gone in Alpha4.</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_performance">Performance</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>This release integrates various runtime performance improvements mainly around bean instance construction,
+                  producer and observer method invocation.</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_next">Next</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>Weld 3.0.0.Alpha5 is planned in 3 weeks time from now, with some more CDI 2.0 previews.
+                  We are going to continue releasing Alpha versions of Weld 3.0 roughly every 3 weeks until
+                  the early draft of CDI 2.0, which should happen sometime in March.
+                  At that point, we&#8217;ll move to Beta releases.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>In the meantime, we&#8217;d like to hear your feedback on Probe or on Weld 3.0 Alpha releases in general.
+                  Feel free to use our <a href="https://community.jboss.org/en/weld?view=discussions">forums</a> or <a href="http://webchat.freenode.net/?channels=weld-dev">#weld-dev on freenode</a></p>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="http://docs.jboss.org/weld/javadoc/3.0/weld-api/org/jboss/weld/experimental/package-frame.html">Experimental API documentation</a> &#93;
+                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12326166">Release notes</a> &#93;
+                  &#91; <a href="https://sourceforge.net/projects/jboss/files/Weld/3.0.0.Alpha4">Distribution</a> &#93;
+                  &#91; Patch for Wildfly
+                  (<a href="http://sourceforge.net/projects/jboss/files/Weld/3.0.0.Alpha4/wildfly-8.2.0.Final-weld-3.0.0.Alpha4-patch.zip/download">8.2</a>,
+                  <a href="http://sourceforge.net/projects/jboss/files/Weld/3.0.0.Alpha4/wildfly-9.0.0.Alpha1-weld-3.0.0.Alpha4-patch.zip/download">9 Alpha</a>)
+                  &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2014/12/10/an-update-on-weld-3/">An update on Weld 3</a>
@@ -831,83 +974,6 @@ <h2 id="_acknowledgement">Acknowledgement</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2014/02/04/weld-220-alpha1/">CDI 1.2 and Weld 2.2</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2014-2-4
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Jozef Hartinger
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>Work on a maintenance release of the CDI specification (CDI 1.2) has started recently. Now is the best time to add feedback on <a href="http://www.cdi-spec.org/news/2013/12/16/CDI-1-2-issues-list/">issues being addressed</a>. Most of the discussion happens in the <a href="https://lists.jboss.org/mailman/listinfo/cdi-dev">cdi-dev mailing list</a> or the <a href="http://webchat.freenode.net/?channels=jsr346">IRC channel</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p><strong>Weld 2.2</strong> is going to be the reference implementation of CDI 1.2. Besides implementing the changes introduced in the maintenance release, we are going to focus on improving non-functional characteristics in this release of Weld:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>bootstrap time</p>
-                  </li>
-                  <li>
-                  <p>memory footprint</p>
-                  </li>
-                  <li>
-                  <p>throughput</p>
-                  </li>
-                  <li>
-                  <p>maximum number of concurrent clients</p>
-                  </li>
-                  <li>
-                  <p>session replication overhead</p>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>Today, we released <strong>Weld 2.2.0.Alpha1</strong>. The most significant changes include:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Added <a href="http://docs.jboss.org/weld/javadoc/2.2/weld-spi/org/jboss/weld/resources/spi/ClassFileInfo.html">new SPI</a> that allows bytecode-scanning frameworks (such as <a href="https://github.com/wildfly/jandex">jandex</a>) to be integrated. This yields improved bootstrap time especially with large deployments.</p>
-                  </li>
-                  <li>
-                  <p>Reduced memory consumption (our tests show 6-12% less memory used after bootstrap with large deployments)</p>
-                  </li>
-                  <li>
-                  <p>Improved event/observer performance</p>
-                  </li>
-                  <li>
-                  <p>Java Web Start support finally got in (thanks to Alexandre Gattiker for the patch!)</p>
-                  </li>
-                  <li>
-                  <p>Improved Servlet container support (Jetty 9.1, ServletContainerInitializer used to bootstrap Weld, Tomcat 8 support)</p>
-                  </li>
-                  <li>
-                  <p>A new Groovy example (groovy-numberguess) was added</p>
-                  </li>
-                  <li>
-                  <p>Many other bug fixes and improvements. See the <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12322332">release notes</a> for a complete list of changes</p>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>Now, we continue to work on Weld 2.2. Expect the final version in late March. In the meantime, try this release and let us know what you think in the <a href="https://community.jboss.org/en/weld">forum</a>. 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 class="paragraph">
-                  <p>&#91; <a href="https://sourceforge.net/projects/jboss/files/Weld/2.2.0.Alpha1">Distribution</a> &#93;
-                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12322332">Release notes</a> &#93;
-                  &#91; <a href="http://docs.jboss.org/weld/reference/2.2.0.Alpha1/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/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 f4cccff1..4e90b2ad 100644
--- a/news/page/18.html
+++ b/news/page/18.html
@@ -141,6 +141,83 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2014/02/04/weld-220-alpha1/">CDI 1.2 and Weld 2.2</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2014-2-4
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Jozef Hartinger
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>Work on a maintenance release of the CDI specification (CDI 1.2) has started recently. Now is the best time to add feedback on <a href="http://www.cdi-spec.org/news/2013/12/16/CDI-1-2-issues-list/">issues being addressed</a>. Most of the discussion happens in the <a href="https://lists.jboss.org/mailman/listinfo/cdi-dev">cdi-dev mailing list</a> or the <a href="http://webchat.freenode.net/?channels=jsr346">IRC channel</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p><strong>Weld 2.2</strong> is going to be the reference implementation of CDI 1.2. Besides implementing the changes introduced in the maintenance release, we are going to focus on improving non-functional characteristics in this release of Weld:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>bootstrap time</p>
+                  </li>
+                  <li>
+                  <p>memory footprint</p>
+                  </li>
+                  <li>
+                  <p>throughput</p>
+                  </li>
+                  <li>
+                  <p>maximum number of concurrent clients</p>
+                  </li>
+                  <li>
+                  <p>session replication overhead</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>Today, we released <strong>Weld 2.2.0.Alpha1</strong>. The most significant changes include:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Added <a href="http://docs.jboss.org/weld/javadoc/2.2/weld-spi/org/jboss/weld/resources/spi/ClassFileInfo.html">new SPI</a> that allows bytecode-scanning frameworks (such as <a href="https://github.com/wildfly/jandex">jandex</a>) to be integrated. This yields improved bootstrap time especially with large deployments.</p>
+                  </li>
+                  <li>
+                  <p>Reduced memory consumption (our tests show 6-12% less memory used after bootstrap with large deployments)</p>
+                  </li>
+                  <li>
+                  <p>Improved event/observer performance</p>
+                  </li>
+                  <li>
+                  <p>Java Web Start support finally got in (thanks to Alexandre Gattiker for the patch!)</p>
+                  </li>
+                  <li>
+                  <p>Improved Servlet container support (Jetty 9.1, ServletContainerInitializer used to bootstrap Weld, Tomcat 8 support)</p>
+                  </li>
+                  <li>
+                  <p>A new Groovy example (groovy-numberguess) was added</p>
+                  </li>
+                  <li>
+                  <p>Many other bug fixes and improvements. See the <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12322332">release notes</a> for a complete list of changes</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>Now, we continue to work on Weld 2.2. Expect the final version in late March. In the meantime, try this release and let us know what you think in the <a href="https://community.jboss.org/en/weld">forum</a>. 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 class="paragraph">
+                  <p>&#91; <a href="https://sourceforge.net/projects/jboss/files/Weld/2.2.0.Alpha1">Distribution</a> &#93;
+                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12322332">Release notes</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/2.2.0.Alpha1/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/2014/01/14/weld-212-final/">Three new Weld releases</a>
@@ -338,24 +415,6 @@ <h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2013/06/20/new-weld-site/">Weld has a new web site!</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2013-6-20
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Martin Kouba
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>Weld has a new web site and it&#8217;s built with Awestruct!</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 0ca6cfb0..49ea0283 100644
--- a/news/page/19.html
+++ b/news/page/19.html
@@ -141,6 +141,24 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2013/06/20/new-weld-site/">Weld has a new web site!</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2013-6-20
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Martin Kouba
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>Weld has a new web site and it&#8217;s built with Awestruct!</p>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2013/06/06/weld-201-final/">Weld 2.0.1.Final</a>
diff --git a/news/page/2.html b/news/page/2.html
index 8fd49199..0ac2aa0a 100644
--- a/news/page/2.html
+++ b/news/page/2.html
@@ -141,6 +141,66 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2023/10/05/weld-512Final/">Weld 5.1.2.Final</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2023-10-5
+                  &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 5.1.2.Final has landed in Central and with it some new bufgixes.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Here is a summary of the changes:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Avoid creation of duplicated thread groups on application re-deploy (<a href="https://issues.redhat.com/browse/WELD-2755">WELD-2755</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>This could lead to a very tiny memory leak on repeated app re-deploy while on app servers (such as WildFly)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p><code>WeldInitialListener</code> can no longer throw <code>NullPointerException</code> if the application failed to start properly (<a href="https://issues.redhat.com/browse/WELD-2752">WELD-2752</a>)</p>
+                  </li>
+                  <li>
+                  <p><code>WeldManager#getContexts</code> not properly returns empty collection when there is no context for given scope (<a href="https://issues.redhat.com/browse/WELD-2761">WELD-2761</a>)</p>
+                  </li>
+                  <li>
+                  <p>Fix client proxy creation for <code>@Typed</code> beans with package-protected types (<a href="https://issues.redhat.com/browse/WELD-2758">WELD-2758</a>)</p>
+                  </li>
+                  <li>
+                  <p>Weld project now uses unified and automatic formatting and import sorting that happens during build (<a href="https://issues.redhat.com/browse/WELD-2753">WELD-2753</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>As always, if you find further issues with Weld 5, let us know and we&#8217;ll try to help.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="/download/">Download</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/5.1.2.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=12411521" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2023/08/09/weld-511SP2/">Weld 5.1.1.SP2</a>
@@ -379,65 +439,6 @@ <h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2022/06/24/weld-501Final/">Weld 5.0.1.Final</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2022-6-24
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/release">release</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Matej Novotny
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>Weld Core 5.0.1.Final is now available and comes with Weld API 5.0.SP2.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Main highlights are as follows:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Updated all CDI related versions (API and TCKs) to their latest released variants and made sure we are passing</p>
-                  </li>
-                  <li>
-                  <p>Updated many other EE 10 APIs to their latest releases</p>
-                  </li>
-                  <li>
-                  <p>We are once again fully continuously testing against an EE container (nightly WildFly builds) which helped us polish more bumps in tests and code</p>
-                  </li>
-                  <li>
-                  <p>Tomcat 10.1 is available and supports EE 10, so we have upgraded to test against that and can therefore confirm our support for servlets is working well</p>
-                  </li>
-                  <li>
-                  <p>Jetty support is at the moment not verified as there is no public Jetty 12 release to test against</p>
-                  </li>
-                  <li>
-                  <p>Reviewed Servlet related parts of our documentation and updated them</p>
-                  </li>
-                  <li>
-                  <p>Reviewed Weld SE-Servlet cooperation and renewed continuous testing for it</p>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>As always, if you find further issues with Weld 5, let us know and we&#8217;ll try to help.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>&#91; <a href="/download/">Download</a> &#93;
-                  &#91; <a href="http://docs.jboss.org/weld/reference/5.0.1.Final/en-US/html_single/" target="_blank" rel="noopener">Documentation</a> &#93;
-                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12385166" 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 f880eafc..7ea1a698 100644
--- a/news/page/3.html
+++ b/news/page/3.html
@@ -141,6 +141,65 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2022/06/24/weld-501Final/">Weld 5.0.1.Final</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2022-6-24
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/release">release</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Matej Novotny
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>Weld Core 5.0.1.Final is now available and comes with Weld API 5.0.SP2.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Main highlights are as follows:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Updated all CDI related versions (API and TCKs) to their latest released variants and made sure we are passing</p>
+                  </li>
+                  <li>
+                  <p>Updated many other EE 10 APIs to their latest releases</p>
+                  </li>
+                  <li>
+                  <p>We are once again fully continuously testing against an EE container (nightly WildFly builds) which helped us polish more bumps in tests and code</p>
+                  </li>
+                  <li>
+                  <p>Tomcat 10.1 is available and supports EE 10, so we have upgraded to test against that and can therefore confirm our support for servlets is working well</p>
+                  </li>
+                  <li>
+                  <p>Jetty support is at the moment not verified as there is no public Jetty 12 release to test against</p>
+                  </li>
+                  <li>
+                  <p>Reviewed Servlet related parts of our documentation and updated them</p>
+                  </li>
+                  <li>
+                  <p>Reviewed Weld SE-Servlet cooperation and renewed continuous testing for it</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>As always, if you find further issues with Weld 5, let us know and we&#8217;ll try to help.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="/download/">Download</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/5.0.1.Final/en-US/html_single/" target="_blank" rel="noopener">Documentation</a> &#93;
+                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12385166" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2022/06/08/weld-500SP2/">Weld 5.0.0.SP2</a>
@@ -326,54 +385,6 @@ <h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2022/02/23/weld-500CR1/">Weld 5.0.0.CR1</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2022-2-23
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/release">release</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Matej Novotny
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>Weld 5 now has its first candidate release; Weld API 5.0.CR1 and Weld Core 5.0.0.CR1 are headed towards Maven Central.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>This release has only minor differences from the Beta but it is a testable basis for Final specification release.
-                  Here is a quick overview:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <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>Use secure actions when obtaining constructors via reflection in <code>LiteExtensionTranslator</code> (<a href="https://issues.jboss.org/browse/WELD-2705" target="_blank" rel="noopener">WELD-2705</a>)</p>
-                  </li>
-                  <li>
-                  <p>Dozens of dependabot updates for various dependencies</p>
-                  </li>
-                  <li>
-                  <p>Updated to the latest released CDI version (4.0.0-RC5) and latest CDI TCK version (4.0.0.RC6)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>&#91; <a href="/download/">Download</a> &#93;
-                  &#91; <a href="http://docs.jboss.org/weld/reference/5.0.0.CR1/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=12380311" target="_blank" rel="noopener">Release notes</a> &#93;</p>
-                  </div>
-                </div>
-                <hr>
-              </div>
               <div class="pagination-links"><a href="/news/page/2.html" class="previous-link">Previous</a> <a href="/news/" class="page-link">1</a> <a href="/news/page/2.html" class="page-link">2</a> <span class="current-page">3</span> <a href="/news/page/4.html" class="page-link">4</a> <span class="skip">...</span><a href="/news/page/18.html" class="page-link">18</a> <a href="/news/page/19.html" class="page-link">19</a> <a href="/news/page/4.html" class="next-link">Next</a> </div>
               <hr>
               <div>
diff --git a/news/page/4.html b/news/page/4.html
index 002111a9..24933264 100644
--- a/news/page/4.html
+++ b/news/page/4.html
@@ -141,6 +141,54 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2022/02/23/weld-500CR1/">Weld 5.0.0.CR1</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2022-2-23
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/release">release</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Matej Novotny
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>Weld 5 now has its first candidate release; Weld API 5.0.CR1 and Weld Core 5.0.0.CR1 are headed towards Maven Central.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>This release has only minor differences from the Beta but it is a testable basis for Final specification release.
+                  Here is a quick overview:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <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>Use secure actions when obtaining constructors via reflection in <code>LiteExtensionTranslator</code> (<a href="https://issues.jboss.org/browse/WELD-2705" target="_blank" rel="noopener">WELD-2705</a>)</p>
+                  </li>
+                  <li>
+                  <p>Dozens of dependabot updates for various dependencies</p>
+                  </li>
+                  <li>
+                  <p>Updated to the latest released CDI version (4.0.0-RC5) and latest CDI TCK version (4.0.0.RC6)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="/download/">Download</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/5.0.0.CR1/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=12380311" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                </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>
@@ -648,112 +696,6 @@ <h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2021/03/22/weld-401Final/">Weld 4.0.1.Final</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2021-3-22
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/release">release</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Matej Novotny
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>First maintainance release of Weld 4 is now available along with API version 4.0.SP1.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>The crux of this release is (much like 3.1.7.Final) a rework of Weld&#8217;s default class defining capabilities.
-                  With 4.0.1.Final you should no longer see illegal reflective access warning so long as you are on JDK 11 or newer.
-                  More details on this are below or in the respective <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/4.0.SP1/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/4.0.SP1/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>
-                  <li>
-                  <p><code>ProxyFactory</code> now creates determininistic proxy names (<a href="https://issues.jboss.org/browse/WELD-2618" target="_blank" rel="noopener">WELD-2618</a>)</p>
-                  </li>
-                  <li>
-                  <p>Decorators for interfaces with non-decorated default method now work properly (<a href="https://issues.jboss.org/browse/WELD-2647" target="_blank" rel="noopener">WELD-2647</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/4.0.1.Final/en-US/html_single/" target="_blank" rel="noopener">Documentation</a> &#93;
-                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12352776" 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 bb8f2019..506bf697 100644
--- a/news/page/5.html
+++ b/news/page/5.html
@@ -141,6 +141,112 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2021/03/22/weld-401Final/">Weld 4.0.1.Final</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2021-3-22
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/release">release</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Matej Novotny
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>First maintainance release of Weld 4 is now available along with API version 4.0.SP1.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>The crux of this release is (much like 3.1.7.Final) a rework of Weld&#8217;s default class defining capabilities.
+                  With 4.0.1.Final you should no longer see illegal reflective access warning so long as you are on JDK 11 or newer.
+                  More details on this are below or in the respective <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/4.0.SP1/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/4.0.SP1/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>
+                  <li>
+                  <p><code>ProxyFactory</code> now creates determininistic proxy names (<a href="https://issues.jboss.org/browse/WELD-2618" target="_blank" rel="noopener">WELD-2618</a>)</p>
+                  </li>
+                  <li>
+                  <p>Decorators for interfaces with non-decorated default method now work properly (<a href="https://issues.jboss.org/browse/WELD-2647" target="_blank" rel="noopener">WELD-2647</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/4.0.1.Final/en-US/html_single/" target="_blank" rel="noopener">Documentation</a> &#93;
+                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12352776" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2021/03/18/weld-317Final/">Weld 3.1.7.Final</a>
@@ -530,123 +636,6 @@ <h2 id="_wildfly_patch">WildFly Patch</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2020/08/12/weld-315Final/">Weld 3.1.5.Final</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2020-8-12
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/release">release</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Matej Novotny
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>New maintenance release is now out - Weld 3.1.5.Final.
-                  It comes along with Weld API 3.1.SP3 although there are no significant changes in the API.
-                  The release was mainly to update to a new parent project version, allowing us to consume newer plugins and prepare ground for MR JAR support.
-                  As for core artifacts, there are some bugfixes as usual, so let&#8217;s take a look at those.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Fixes and improvements:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Weld Core</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Allow to aggressively invoke <code>setAttribute()</code> when manipulating with conversation map in session (<a href="https://issues.jboss.org/browse/WELD-2626" target="_blank" rel="noopener">WELD-2626</a>)</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>This behaviour is gated behind a property; it doesn&#8217;t affect standard Weld behaviour</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Automatically cleanup leftover <code>HttpSessionDestructionContext</code> when starting new session context on a thread (<a href="https://issues.jboss.org/browse/WELD-2631" target="_blank" rel="noopener">WELD-2631</a>)</p>
-                  </li>
-                  <li>
-                  <p>Fix a rare case where an integer overflow could happen during alternative priority ordering (<a href="https://issues.jboss.org/browse/WELD-2628" target="_blank" rel="noopener">WELD-2628</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Weld Servlet Support</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Change <code>WebAppBeanArchiveScanner</code> to allow serving modules without publishing (<a href="https://issues.jboss.org/browse/WELD-2570" target="_blank" rel="noopener">WELD-2570</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Other bits</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p><code>ObserverMethodConfigurator</code> initialized by reading an <code>AnnotatedType</code> previously didn&#8217;t set the method as async when it should (<a href="https://issues.jboss.org/browse/WELD-2609" target="_blank" rel="noopener">WELD-2609</a>)</p>
-                  </li>
-                  <li>
-                  <p>Fix up generation of javadoc (especially with JDK 11) for shaded artifacts and make it include Weld API/SPI as well as CDI API javadoc</p>
-                  </li>
-                  <li>
-                  <p>Prepare ground for MR JAR releases which are a likely solution to JDK 11 class defining for SE (<a href="https://issues.jboss.org/browse/WELD-2619" target="_blank" rel="noopener">WELD-2619</a>)</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>This is hopefully coming in the very next release</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Updates to website tooling (Docker image, Ruby dependencies) and updates to some old <code>http</code> references which should now be <code>https</code></p>
-                  </li>
-                  <li>
-                  <p>Re-enable testing of CDI TCK 1.2 with Weld 3.x; this was broken sometime during migration to Jakarta artifacts (<a href="https://issues.jboss.org/browse/WELD-2624" target="_blank" rel="noopener">WELD-2624</a>)</p>
-                  </li>
-                  <li>
-                  <p>A test that assumed an order in between conversation context lifecycle and session timeouts was found to be wrong (<code>ConversationContextDestroyedOnSessionTimeoutTest</code>) and was re-written to remove the erroneous assumption (<a href="https://issues.jboss.org/browse/WELD-2629" target="_blank" rel="noopener">WELD-2629</a>)</p>
-                  </li>
-                  <li>
-                  <p>Correct JaCoCo TCK execution (<a href="https://issues.jboss.org/browse/WELD-2625" target="_blank" rel="noopener">WELD-2625</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_wildfly_patch">WildFly Patch</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>This time around, the <a href="http://download.jboss.org/weld/3.1.5.Final/wildfly-20.0.1.Final-weld-3.1.5.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly 20.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.4.Final/en-US/html/" target="_blank" rel="noopener">Documentation</a> &#93;
-                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12343306" target="_blank" rel="noopener">Release notes</a> &#93;</p>
-                  </div>
-                  </div>
-                  </div>
-                </div>
-                <hr>
-              </div>
               <div class="pagination-links"><a href="/news/page/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 69b9423b..1162c689 100644
--- a/news/page/6.html
+++ b/news/page/6.html
@@ -141,6 +141,123 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2020/08/12/weld-315Final/">Weld 3.1.5.Final</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2020-8-12
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/release">release</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Matej Novotny
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>New maintenance release is now out - Weld 3.1.5.Final.
+                  It comes along with Weld API 3.1.SP3 although there are no significant changes in the API.
+                  The release was mainly to update to a new parent project version, allowing us to consume newer plugins and prepare ground for MR JAR support.
+                  As for core artifacts, there are some bugfixes as usual, so let&#8217;s take a look at those.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Fixes and improvements:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Weld Core</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Allow to aggressively invoke <code>setAttribute()</code> when manipulating with conversation map in session (<a href="https://issues.jboss.org/browse/WELD-2626" target="_blank" rel="noopener">WELD-2626</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>This behaviour is gated behind a property; it doesn&#8217;t affect standard Weld behaviour</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Automatically cleanup leftover <code>HttpSessionDestructionContext</code> when starting new session context on a thread (<a href="https://issues.jboss.org/browse/WELD-2631" target="_blank" rel="noopener">WELD-2631</a>)</p>
+                  </li>
+                  <li>
+                  <p>Fix a rare case where an integer overflow could happen during alternative priority ordering (<a href="https://issues.jboss.org/browse/WELD-2628" target="_blank" rel="noopener">WELD-2628</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Weld Servlet Support</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Change <code>WebAppBeanArchiveScanner</code> to allow serving modules without publishing (<a href="https://issues.jboss.org/browse/WELD-2570" target="_blank" rel="noopener">WELD-2570</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Other bits</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p><code>ObserverMethodConfigurator</code> initialized by reading an <code>AnnotatedType</code> previously didn&#8217;t set the method as async when it should (<a href="https://issues.jboss.org/browse/WELD-2609" target="_blank" rel="noopener">WELD-2609</a>)</p>
+                  </li>
+                  <li>
+                  <p>Fix up generation of javadoc (especially with JDK 11) for shaded artifacts and make it include Weld API/SPI as well as CDI API javadoc</p>
+                  </li>
+                  <li>
+                  <p>Prepare ground for MR JAR releases which are a likely solution to JDK 11 class defining for SE (<a href="https://issues.jboss.org/browse/WELD-2619" target="_blank" rel="noopener">WELD-2619</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>This is hopefully coming in the very next release</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Updates to website tooling (Docker image, Ruby dependencies) and updates to some old <code>http</code> references which should now be <code>https</code></p>
+                  </li>
+                  <li>
+                  <p>Re-enable testing of CDI TCK 1.2 with Weld 3.x; this was broken sometime during migration to Jakarta artifacts (<a href="https://issues.jboss.org/browse/WELD-2624" target="_blank" rel="noopener">WELD-2624</a>)</p>
+                  </li>
+                  <li>
+                  <p>A test that assumed an order in between conversation context lifecycle and session timeouts was found to be wrong (<code>ConversationContextDestroyedOnSessionTimeoutTest</code>) and was re-written to remove the erroneous assumption (<a href="https://issues.jboss.org/browse/WELD-2629" target="_blank" rel="noopener">WELD-2629</a>)</p>
+                  </li>
+                  <li>
+                  <p>Correct JaCoCo TCK execution (<a href="https://issues.jboss.org/browse/WELD-2625" target="_blank" rel="noopener">WELD-2625</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_wildfly_patch">WildFly Patch</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>This time around, the <a href="http://download.jboss.org/weld/3.1.5.Final/wildfly-20.0.1.Final-weld-3.1.5.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly 20.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.4.Final/en-US/html/" target="_blank" rel="noopener">Documentation</a> &#93;
+                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12343306" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2020/05/13/weld-jakarta-ee-9/">Weld 4 and Jakarta EE 9</a>
@@ -585,111 +702,6 @@ <h2 id="_wildfly_patch">WildFly Patch</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2019/05/07/weld-311Final/">Weld 3.1.1.Final</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2019-5-7
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/release">release</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Matej Novotny
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>Weld 3.1.1.Final is out, it is a rather small nonetheless important maintenance release.
-                  There is bunch of fixes present here; notably one for context propagation API that could cause some headaches with context seemingly not propagating.
-                  Moving on, we also have some improvements to asynchronous events on default executors or ordering on <code>ProcessAnnotatedType</code> events.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Fixes and improvements:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Weld API/SPI</p>
-                  </li>
-                  <li>
-                  <p>Weld Core</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p><code>WeldAlterableContext#clearAndSet()</code> was incorrectly leaving some caches behind (<a href="https://issues.jboss.org/browse/WELD-2566" target="_blank" rel="noopener">WELD-2566</a>)</p>
-                  </li>
-                  <li>
-                  <p>Fix serializability issue with intercepted session beans having private methods (<a href="https://issues.jboss.org/browse/WELD-2574" target="_blank" rel="noopener">WELD-2574</a>)</p>
-                  </li>
-                  <li>
-                  <p>Asynchronous event notification on default executor should preserve TCCL (<a href="https://issues.jboss.org/browse/WELD-2573" target="_blank" rel="noopener">WELD-2573</a>)</p>
-                  </li>
-                  <li>
-                  <p>Fix ordering of <code>ProcessAnnotatedType</code> events via <code>@Priority</code> (<a href="https://issues.jboss.org/browse/WELD-2568" target="_blank" rel="noopener">WELD-2568</a>)</p>
-                  </li>
-                  <li>
-                  <p>Small optimization for distributed environment when bean index is empty (<a href="https://issues.jboss.org/browse/WELD-2577" target="_blank" rel="noopener">WELD-2577</a>)</p>
-                  </li>
-                  <li>
-                  <p>Custom <code>InjectionTarget</code> now invokes any present <code>dispose()</code> (<a href="https://issues.jboss.org/browse/WELD-2580" target="_blank" rel="noopener">WELD-2580</a>)</p>
-                  </li>
-                  <li>
-                  <p>Align behaviour of self-invocation of otherwise intercepted method from within private final observer method (<a href="https://issues.jboss.org/browse/WELD-2571" target="_blank" rel="noopener">WELD-2571</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Weld SE</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Allow to specify custom <code>DiscoveryStrategy</code> via service loader mechanism (<a href="https://issues.jboss.org/browse/WELD-2578" target="_blank" rel="noopener">WELD-2578</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Other</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Update tooling around documentation builds (<a href="https://issues.jboss.org/browse/WELD-2564" target="_blank" rel="noopener">WELD-2564</a>)</p>
-                  </li>
-                  <li>
-                  <p>Update JBoss classfilewriter to newer version working on JDK 12 (<a href="https://issues.jboss.org/browse/WELD-2572" target="_blank" rel="noopener">WELD-2572</a>)</p>
-                  </li>
-                  <li>
-                  <p>Fix Probe functional tests on latest Firefox (<a href="https://issues.jboss.org/browse/WELD-2579" target="_blank" rel="noopener">WELD-2579</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_wildfly_patch">WildFly Patch</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>This time around, the <a href="http://download.jboss.org/weld/3.1.1.Final/wildfly-16.0.0.Final-weld-3.1.1.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly 16.0.0.Final</a> is available.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>If you’re not familiar with patching WildFly, check the <a href="/documentation/#12">FAQ</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>&#91; <a href="/download/">Download</a> &#93;
-                  &#91; <a href="http://docs.jboss.org/weld/reference/3.1.1.Final/en-US/html/" target="_blank" rel="noopener">Documentation</a> &#93;
-                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12340657" 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 39f4aab3..f482cb16 100644
--- a/news/page/7.html
+++ b/news/page/7.html
@@ -141,6 +141,111 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2019/05/07/weld-311Final/">Weld 3.1.1.Final</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2019-5-7
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/release">release</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Matej Novotny
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>Weld 3.1.1.Final is out, it is a rather small nonetheless important maintenance release.
+                  There is bunch of fixes present here; notably one for context propagation API that could cause some headaches with context seemingly not propagating.
+                  Moving on, we also have some improvements to asynchronous events on default executors or ordering on <code>ProcessAnnotatedType</code> events.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Fixes and improvements:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Weld API/SPI</p>
+                  </li>
+                  <li>
+                  <p>Weld Core</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p><code>WeldAlterableContext#clearAndSet()</code> was incorrectly leaving some caches behind (<a href="https://issues.jboss.org/browse/WELD-2566" target="_blank" rel="noopener">WELD-2566</a>)</p>
+                  </li>
+                  <li>
+                  <p>Fix serializability issue with intercepted session beans having private methods (<a href="https://issues.jboss.org/browse/WELD-2574" target="_blank" rel="noopener">WELD-2574</a>)</p>
+                  </li>
+                  <li>
+                  <p>Asynchronous event notification on default executor should preserve TCCL (<a href="https://issues.jboss.org/browse/WELD-2573" target="_blank" rel="noopener">WELD-2573</a>)</p>
+                  </li>
+                  <li>
+                  <p>Fix ordering of <code>ProcessAnnotatedType</code> events via <code>@Priority</code> (<a href="https://issues.jboss.org/browse/WELD-2568" target="_blank" rel="noopener">WELD-2568</a>)</p>
+                  </li>
+                  <li>
+                  <p>Small optimization for distributed environment when bean index is empty (<a href="https://issues.jboss.org/browse/WELD-2577" target="_blank" rel="noopener">WELD-2577</a>)</p>
+                  </li>
+                  <li>
+                  <p>Custom <code>InjectionTarget</code> now invokes any present <code>dispose()</code> (<a href="https://issues.jboss.org/browse/WELD-2580" target="_blank" rel="noopener">WELD-2580</a>)</p>
+                  </li>
+                  <li>
+                  <p>Align behaviour of self-invocation of otherwise intercepted method from within private final observer method (<a href="https://issues.jboss.org/browse/WELD-2571" target="_blank" rel="noopener">WELD-2571</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Weld SE</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Allow to specify custom <code>DiscoveryStrategy</code> via service loader mechanism (<a href="https://issues.jboss.org/browse/WELD-2578" target="_blank" rel="noopener">WELD-2578</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Other</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Update tooling around documentation builds (<a href="https://issues.jboss.org/browse/WELD-2564" target="_blank" rel="noopener">WELD-2564</a>)</p>
+                  </li>
+                  <li>
+                  <p>Update JBoss classfilewriter to newer version working on JDK 12 (<a href="https://issues.jboss.org/browse/WELD-2572" target="_blank" rel="noopener">WELD-2572</a>)</p>
+                  </li>
+                  <li>
+                  <p>Fix Probe functional tests on latest Firefox (<a href="https://issues.jboss.org/browse/WELD-2579" target="_blank" rel="noopener">WELD-2579</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_wildfly_patch">WildFly Patch</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>This time around, the <a href="http://download.jboss.org/weld/3.1.1.Final/wildfly-16.0.0.Final-weld-3.1.1.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly 16.0.0.Final</a> is available.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>If you’re not familiar with patching WildFly, check the <a href="/documentation/#12">FAQ</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="/download/">Download</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/3.1.1.Final/en-US/html/" target="_blank" rel="noopener">Documentation</a> &#93;
+                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12340657" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2019/02/06/weld-310Final/">Weld 3.1.0.Final</a>
@@ -682,199 +787,6 @@ <h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2018/04/26/weld-304Final/">Weld 3.0.4.Final</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2018-4-26
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/release">release</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Matej Novotny
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>Weld 3.0.4.Final is here along with Weld API 3.0.SP3 - make sure you update both.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>In this release we took first steps towards eliminating illegal access in JDK 10+.
-                  The good news is, Weld should now be able to run with <code>--illegal-access=deny</code>.
-                  The project and CI infrastructure around it went through a lot of changes to be able to build and execute on JDK 10 and there is still more to come.
-                  There are also numerous optimizations - <code>beans.xml</code> parsing, AT identifier representation, optional memory savings.
-                  And of course, bug fixes, so let us take a look at all of it.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Noticeable amount of reports, suggestions and even fixes came from the community - for that you have our thanks (and a new version of Weld of course)!</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Fixes and improvements:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Weld Core</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Correct proxy generation for class hierarchy with abstract class and generics (<a href="https://issues.jboss.org/browse/WELD-2470" target="_blank" rel="noopener">WELD-2470</a>)</p>
-                  </li>
-                  <li>
-                  <p>Opt-in enhancement in HTTP session replication, more eager approach (<a href="https://issues.jboss.org/browse/WELD-1130" target="_blank" rel="noopener">WELD-1130</a>)</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Note that WildFly does not need or use this</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Fix NPE which could occur with <code>SecurityManager</code> if <code>getPermissions()</code> returned <code>null</code> (<a href="https://issues.jboss.org/browse/WELD-2464" target="_blank" rel="noopener">WELD-2464</a>)</p>
-                  </li>
-                  <li>
-                  <p>Relax bean type check in <code>BeanManager.getInjectableReference()</code> (<a href="https://issues.jboss.org/browse/WELD-2466" target="_blank" rel="noopener">WELD-2466</a>)</p>
-                  </li>
-                  <li>
-                  <p><code>AfterTypeDiscovery</code> did not allow to remove declared interceptors/decorators/alternatives correctly (<a href="https://issues.jboss.org/browse/WELD-2479" target="_blank" rel="noopener">WELD-2479</a>)</p>
-                  </li>
-                  <li>
-                  <p>Two globally selected alternatives with the same priority should result in ambiguous dependency (<a href="https://issues.jboss.org/browse/WELD-2482" target="_blank" rel="noopener">WELD-2482</a>)</p>
-                  </li>
-                  <li>
-                  <p><code>Configurator</code> SPI now uses sensible <code>toString()</code> so that user can tell what went wrong (<a href="https://issues.jboss.org/browse/WELD-2484" target="_blank" rel="noopener">WELD-2484</a>)</p>
-                  </li>
-                  <li>
-                  <p>Improve performance of <code>beans.xml</code> parsing (<a href="https://issues.jboss.org/browse/WELD-2469" target="_blank" rel="noopener">WELD-2469</a>)</p>
-                  </li>
-                  <li>
-                  <p>Introduce an optional configuration allowing Weld to perform cleanup after boot (<a href="https://issues.jboss.org/browse/WELD-2457" target="_blank" rel="noopener">WELD-2457</a> and <a href="https://issues.jboss.org/browse/WELD-2475" target="_blank" rel="noopener">WELD-2475</a>)</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>In EE servers, if integrators meet certain conditions and allow for this, Weld can them drop metadata from some beans which will not be used in runtime</p>
-                  </li>
-                  <li>
-                  <p>See <em>Docs</em> section for links</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Optimise <code>String</code> representation of <code>AnnotatedTypeIdentifier</code> (<a href="https://issues.jboss.org/browse/WELD-2477" target="_blank" rel="noopener">WELD-2477</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Weld SE</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Fix NPE which could occur if trying to intercept a method called by constructor (<a href="https://issues.jboss.org/browse/WELD-2478" target="_blank" rel="noopener">WELD-2478</a> and <a href="https://issues.jboss.org/browse/WELD-2473" target="_blank" rel="noopener">WELD-2473</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>JDK 9/10 and onwards (<a href="https://issues.jboss.org/browse/WELD-2460" target="_blank" rel="noopener">WELD-2460</a>)</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Weld uses JDK&#8217;s internal BCEL classes (<a href="https://issues.jboss.org/browse/WELD-2490" target="_blank" rel="noopener">WELD-2490</a>)</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>This is only used to report errors in generated bytecode on proxies/subclasses</p>
-                  </li>
-                  <li>
-                  <p>We added a dependency on <code>org.apache.bcel:bcel</code> which enables this functionality without reflective access to internal libraries</p>
-                  </li>
-                  <li>
-                  <p>In order to keep Weld&#8217;s footprint minimal, this dependency is optional only</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Upgrade JBoss Classfilewriter to 1.2.2.Final (<a href="https://issues.jboss.org/browse/WELD-2487" target="_blank" rel="noopener">WELD-2487</a>)</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Eliminates another bunch of illegal access problems</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Probe development tool</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Probe now uses JDK-agnostic <code>Annotation.toString()</code> version (<a href="https://issues.jboss.org/browse/WELD-2463" target="_blank" rel="noopener">WELD-2463</a>)</p>
-                  </li>
-                  <li>
-                  <p>Correction to licences in Probe (<a href="https://issues.jboss.org/browse/WELD-2480" target="_blank" rel="noopener">WELD-2480</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Docs</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p><code>WeldTerminalListener</code> had wrong FQCN in our documentation which resulted in errors when trying to use it in Tomcat (<a href="https://issues.jboss.org/browse/WELD-2486" target="_blank" rel="noopener">WELD-2486</a>)</p>
-                  </li>
-                  <li>
-                  <p>Newly added memory-saving option <code>ConfigurationKey.ALLOW_OPTIMIZED_CLEANUP</code> is documented (<a href="https://issues.jboss.org/browse/WELD-2472" target="_blank" rel="noopener">WELD-2472</a>)</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>If you wish to learn more, please glance <a href="http://docs.jboss.org/weld/reference/3.0.4.Final/en-US/html_single/#remove-unused-beans" target="_blank" rel="noopener">here</a></p>
-                  </li>
-                  <li>
-                  <p>Please note that integrator has to allow for this optimization, otherwise your settings won&#8217;t count (<em>psst, WildFly 12 allows this!</em>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_wildfly_patch">WildFly Patch</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>As usual, a <a href="http://download.jboss.org/weld/3.0.4.Final/wildfly-12.0.0.Final-weld-3.0.4.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly 12.0.0.Final</a> is available.
-                  Please note that Weld 3.0.4.Final will still allow you to boot up WildFly in either EE 7 or EE 8 mode, whichever you prefer.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>If this is the first time you hear about EE 8 mode for WildFly, check <a href="http://wildfly.org/news/2018/02/28/WildFly12-Final-Released" target="_blank" rel="noopener">this post</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>If you’re not familiar with patching WildFly, check the <a href="/documentation/#12">FAQ</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>&#91; <a href="/download/">Download</a> &#93;
-                  &#91; <a href="http://docs.jboss.org/weld/reference/3.0.4.Final/en-US/html/" target="_blank" rel="noopener">Documentation</a> &#93;
-                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12336871" target="_blank" rel="noopener">Release notes</a> &#93;</p>
-                  </div>
-                  </div>
-                  </div>
-                </div>
-                <hr>
-              </div>
               <div class="pagination-links"><a href="/news/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 ccecaf42..272fe217 100644
--- a/news/page/8.html
+++ b/news/page/8.html
@@ -141,6 +141,199 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2018/04/26/weld-304Final/">Weld 3.0.4.Final</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2018-4-26
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/release">release</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Matej Novotny
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>Weld 3.0.4.Final is here along with Weld API 3.0.SP3 - make sure you update both.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>In this release we took first steps towards eliminating illegal access in JDK 10+.
+                  The good news is, Weld should now be able to run with <code>--illegal-access=deny</code>.
+                  The project and CI infrastructure around it went through a lot of changes to be able to build and execute on JDK 10 and there is still more to come.
+                  There are also numerous optimizations - <code>beans.xml</code> parsing, AT identifier representation, optional memory savings.
+                  And of course, bug fixes, so let us take a look at all of it.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Noticeable amount of reports, suggestions and even fixes came from the community - for that you have our thanks (and a new version of Weld of course)!</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Fixes and improvements:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Weld Core</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Correct proxy generation for class hierarchy with abstract class and generics (<a href="https://issues.jboss.org/browse/WELD-2470" target="_blank" rel="noopener">WELD-2470</a>)</p>
+                  </li>
+                  <li>
+                  <p>Opt-in enhancement in HTTP session replication, more eager approach (<a href="https://issues.jboss.org/browse/WELD-1130" target="_blank" rel="noopener">WELD-1130</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Note that WildFly does not need or use this</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Fix NPE which could occur with <code>SecurityManager</code> if <code>getPermissions()</code> returned <code>null</code> (<a href="https://issues.jboss.org/browse/WELD-2464" target="_blank" rel="noopener">WELD-2464</a>)</p>
+                  </li>
+                  <li>
+                  <p>Relax bean type check in <code>BeanManager.getInjectableReference()</code> (<a href="https://issues.jboss.org/browse/WELD-2466" target="_blank" rel="noopener">WELD-2466</a>)</p>
+                  </li>
+                  <li>
+                  <p><code>AfterTypeDiscovery</code> did not allow to remove declared interceptors/decorators/alternatives correctly (<a href="https://issues.jboss.org/browse/WELD-2479" target="_blank" rel="noopener">WELD-2479</a>)</p>
+                  </li>
+                  <li>
+                  <p>Two globally selected alternatives with the same priority should result in ambiguous dependency (<a href="https://issues.jboss.org/browse/WELD-2482" target="_blank" rel="noopener">WELD-2482</a>)</p>
+                  </li>
+                  <li>
+                  <p><code>Configurator</code> SPI now uses sensible <code>toString()</code> so that user can tell what went wrong (<a href="https://issues.jboss.org/browse/WELD-2484" target="_blank" rel="noopener">WELD-2484</a>)</p>
+                  </li>
+                  <li>
+                  <p>Improve performance of <code>beans.xml</code> parsing (<a href="https://issues.jboss.org/browse/WELD-2469" target="_blank" rel="noopener">WELD-2469</a>)</p>
+                  </li>
+                  <li>
+                  <p>Introduce an optional configuration allowing Weld to perform cleanup after boot (<a href="https://issues.jboss.org/browse/WELD-2457" target="_blank" rel="noopener">WELD-2457</a> and <a href="https://issues.jboss.org/browse/WELD-2475" target="_blank" rel="noopener">WELD-2475</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>In EE servers, if integrators meet certain conditions and allow for this, Weld can them drop metadata from some beans which will not be used in runtime</p>
+                  </li>
+                  <li>
+                  <p>See <em>Docs</em> section for links</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Optimise <code>String</code> representation of <code>AnnotatedTypeIdentifier</code> (<a href="https://issues.jboss.org/browse/WELD-2477" target="_blank" rel="noopener">WELD-2477</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Weld SE</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Fix NPE which could occur if trying to intercept a method called by constructor (<a href="https://issues.jboss.org/browse/WELD-2478" target="_blank" rel="noopener">WELD-2478</a> and <a href="https://issues.jboss.org/browse/WELD-2473" target="_blank" rel="noopener">WELD-2473</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>JDK 9/10 and onwards (<a href="https://issues.jboss.org/browse/WELD-2460" target="_blank" rel="noopener">WELD-2460</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Weld uses JDK&#8217;s internal BCEL classes (<a href="https://issues.jboss.org/browse/WELD-2490" target="_blank" rel="noopener">WELD-2490</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>This is only used to report errors in generated bytecode on proxies/subclasses</p>
+                  </li>
+                  <li>
+                  <p>We added a dependency on <code>org.apache.bcel:bcel</code> which enables this functionality without reflective access to internal libraries</p>
+                  </li>
+                  <li>
+                  <p>In order to keep Weld&#8217;s footprint minimal, this dependency is optional only</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Upgrade JBoss Classfilewriter to 1.2.2.Final (<a href="https://issues.jboss.org/browse/WELD-2487" target="_blank" rel="noopener">WELD-2487</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Eliminates another bunch of illegal access problems</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Probe development tool</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Probe now uses JDK-agnostic <code>Annotation.toString()</code> version (<a href="https://issues.jboss.org/browse/WELD-2463" target="_blank" rel="noopener">WELD-2463</a>)</p>
+                  </li>
+                  <li>
+                  <p>Correction to licences in Probe (<a href="https://issues.jboss.org/browse/WELD-2480" target="_blank" rel="noopener">WELD-2480</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Docs</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p><code>WeldTerminalListener</code> had wrong FQCN in our documentation which resulted in errors when trying to use it in Tomcat (<a href="https://issues.jboss.org/browse/WELD-2486" target="_blank" rel="noopener">WELD-2486</a>)</p>
+                  </li>
+                  <li>
+                  <p>Newly added memory-saving option <code>ConfigurationKey.ALLOW_OPTIMIZED_CLEANUP</code> is documented (<a href="https://issues.jboss.org/browse/WELD-2472" target="_blank" rel="noopener">WELD-2472</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>If you wish to learn more, please glance <a href="http://docs.jboss.org/weld/reference/3.0.4.Final/en-US/html_single/#remove-unused-beans" target="_blank" rel="noopener">here</a></p>
+                  </li>
+                  <li>
+                  <p>Please note that integrator has to allow for this optimization, otherwise your settings won&#8217;t count (<em>psst, WildFly 12 allows this!</em>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_wildfly_patch">WildFly Patch</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>As usual, a <a href="http://download.jboss.org/weld/3.0.4.Final/wildfly-12.0.0.Final-weld-3.0.4.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly 12.0.0.Final</a> is available.
+                  Please note that Weld 3.0.4.Final will still allow you to boot up WildFly in either EE 7 or EE 8 mode, whichever you prefer.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>If this is the first time you hear about EE 8 mode for WildFly, check <a href="http://wildfly.org/news/2018/02/28/WildFly12-Final-Released" target="_blank" rel="noopener">this post</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>If you’re not familiar with patching WildFly, check the <a href="/documentation/#12">FAQ</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="/download/">Download</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/3.0.4.Final/en-US/html/" target="_blank" rel="noopener">Documentation</a> &#93;
+                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12336871" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2018/03/20/weld-247Final/">Weld 2.4.7.Final</a>
@@ -646,130 +839,6 @@ <h2 id="_wildfly_patch">WildFly Patch</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2017/11/23/weld-302Final/">Weld 3.0.2.Final</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2017-11-23
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/release">release</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Matej Novotny
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>Weld 3.0.2.Final is out and targetting WildFly 11!
-                  Ever wished you could select events and instances in a truly generic way using just <code>java.lang.reflect.Type</code>?
-                  Looking for easier way to configure SE container?
-                  We have a bunch of bugfixes and improvements for you, so read on&#8230;&#8203;</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Notable fixes and improvements:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Weld Core</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Improved subclass generation mechanism for generic interceptors (<a href="https://issues.jboss.org/browse/WELD-2414" target="_blank" rel="noopener">WELD-2414</a>)</p>
-                  </li>
-                  <li>
-                  <p>Fixed OSGi bundling, we missed out one package on last release (<a href="https://issues.jboss.org/browse/WELD-2421" target="_blank" rel="noopener">WELD-2421</a>)</p>
-                  </li>
-                  <li>
-                  <p>Improved behaviour with no-interface EJB view with non-public methods (<a href="https://issues.jboss.org/browse/WELD-2430" target="_blank" rel="noopener">WELD-2430</a>)</p>
-                  </li>
-                  <li>
-                  <p>Corrected proxy creation for signed classes (<a href="https://issues.jboss.org/browse/WELD-2425" target="_blank" rel="noopener">WELD-2425</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Weld SE</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>There are now multiple convenient error-proof methods to quickly configure SE container (<a href="https://issues.jboss.org/browse/WELD-2426" target="_blank" rel="noopener">WELD-2426</a>)</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p><code>Weld.enableDevMode()</code>, <code>Weld.scanClasspathEntries()</code>, &#8230;&#8203;</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Weld API/SPI</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p><code>WeldInstance</code> has several improvements</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>It now allows you to <code>select()</code> beans based on <code>java.lang.reflect.Type</code> (<a href="https://issues.jboss.org/browse/WELD-2427" target="_blank" rel="noopener">WELD-2427</a>)</p>
-                  </li>
-                  <li>
-                  <p><code>WeldInstance.Handler</code> had become lazy which means you can now iterate/filter/sort <code>WeldInstance</code> without actually instantiating beans (<a href="https://issues.jboss.org/browse/WELD-2258" target="_blank" rel="noopener">WELD-2258</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>There is new interface in the API - <code>WeldEvent</code> - which can be used in place of well known <code>Event</code> but allows you narrow down event type by using <code>select()</code> with <code>java.lang.reflect.Type</code> (<a href="https://issues.jboss.org/browse/WELD-2427" target="_blank" rel="noopener">WELD-2427</a>)</p>
-                  </li>
-                  <li>
-                  <p>API now contains a <code>String</code> key used to obtain interceptors binding from <code>InvocationContext</code> (<a href="https://issues.jboss.org/browse/WELD-2436" target="_blank" rel="noopener">WELD-2436</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Other</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Probe now correctly recognizes beans which have <code>@Priority</code> but aren&#8217;t alternatives (<a href="https://issues.jboss.org/browse/WELD-2432" target="_blank" rel="noopener">WELD-2432</a>)</p>
-                  </li>
-                  <li>
-                  <p>Multiple documentation improvements regarding all things, old and new (<a href="https://issues.jboss.org/browse/WELD-2440" target="_blank" rel="noopener">WELD-2440</a>, <a href="https://issues.jboss.org/browse/WELD-2431" target="_blank" rel="noopener">WELD-2431</a>, <a href="https://issues.jboss.org/browse/WELD-2434" target="_blank" rel="noopener">WELD-2434</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_wildfly_patch">WildFly Patch</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>As usual, there is a <a href="http://download.jboss.org/weld/3.0.2.Final/wildfly-11.0.0.Final-weld-3.0.2.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly 11.0.0.Final</a> is available.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>If you’re not familiar with patching WildFly, check the <a href="/documentation/#12">FAQ</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>&#91; <a href="/download/">Download</a> &#93;
-                  &#91; <a href="http://docs.jboss.org/weld/reference/3.0.2.Final/en-US/html/" target="_blank" rel="noopener">Documentation</a> &#93;
-                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12335442" target="_blank" rel="noopener">Release notes</a> &#93;</p>
-                  </div>
-                  </div>
-                  </div>
-                </div>
-                <hr>
-              </div>
               <div class="pagination-links"><a href="/news/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 3abfe584..56eddcea 100644
--- a/news/page/9.html
+++ b/news/page/9.html
@@ -141,6 +141,130 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2017/11/23/weld-302Final/">Weld 3.0.2.Final</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2017-11-23
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/release">release</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Matej Novotny
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>Weld 3.0.2.Final is out and targetting WildFly 11!
+                  Ever wished you could select events and instances in a truly generic way using just <code>java.lang.reflect.Type</code>?
+                  Looking for easier way to configure SE container?
+                  We have a bunch of bugfixes and improvements for you, so read on&#8230;&#8203;</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Notable fixes and improvements:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Weld Core</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Improved subclass generation mechanism for generic interceptors (<a href="https://issues.jboss.org/browse/WELD-2414" target="_blank" rel="noopener">WELD-2414</a>)</p>
+                  </li>
+                  <li>
+                  <p>Fixed OSGi bundling, we missed out one package on last release (<a href="https://issues.jboss.org/browse/WELD-2421" target="_blank" rel="noopener">WELD-2421</a>)</p>
+                  </li>
+                  <li>
+                  <p>Improved behaviour with no-interface EJB view with non-public methods (<a href="https://issues.jboss.org/browse/WELD-2430" target="_blank" rel="noopener">WELD-2430</a>)</p>
+                  </li>
+                  <li>
+                  <p>Corrected proxy creation for signed classes (<a href="https://issues.jboss.org/browse/WELD-2425" target="_blank" rel="noopener">WELD-2425</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Weld SE</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>There are now multiple convenient error-proof methods to quickly configure SE container (<a href="https://issues.jboss.org/browse/WELD-2426" target="_blank" rel="noopener">WELD-2426</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p><code>Weld.enableDevMode()</code>, <code>Weld.scanClasspathEntries()</code>, &#8230;&#8203;</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Weld API/SPI</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p><code>WeldInstance</code> has several improvements</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>It now allows you to <code>select()</code> beans based on <code>java.lang.reflect.Type</code> (<a href="https://issues.jboss.org/browse/WELD-2427" target="_blank" rel="noopener">WELD-2427</a>)</p>
+                  </li>
+                  <li>
+                  <p><code>WeldInstance.Handler</code> had become lazy which means you can now iterate/filter/sort <code>WeldInstance</code> without actually instantiating beans (<a href="https://issues.jboss.org/browse/WELD-2258" target="_blank" rel="noopener">WELD-2258</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>There is new interface in the API - <code>WeldEvent</code> - which can be used in place of well known <code>Event</code> but allows you narrow down event type by using <code>select()</code> with <code>java.lang.reflect.Type</code> (<a href="https://issues.jboss.org/browse/WELD-2427" target="_blank" rel="noopener">WELD-2427</a>)</p>
+                  </li>
+                  <li>
+                  <p>API now contains a <code>String</code> key used to obtain interceptors binding from <code>InvocationContext</code> (<a href="https://issues.jboss.org/browse/WELD-2436" target="_blank" rel="noopener">WELD-2436</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Other</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Probe now correctly recognizes beans which have <code>@Priority</code> but aren&#8217;t alternatives (<a href="https://issues.jboss.org/browse/WELD-2432" target="_blank" rel="noopener">WELD-2432</a>)</p>
+                  </li>
+                  <li>
+                  <p>Multiple documentation improvements regarding all things, old and new (<a href="https://issues.jboss.org/browse/WELD-2440" target="_blank" rel="noopener">WELD-2440</a>, <a href="https://issues.jboss.org/browse/WELD-2431" target="_blank" rel="noopener">WELD-2431</a>, <a href="https://issues.jboss.org/browse/WELD-2434" target="_blank" rel="noopener">WELD-2434</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_wildfly_patch">WildFly Patch</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>As usual, there is a <a href="http://download.jboss.org/weld/3.0.2.Final/wildfly-11.0.0.Final-weld-3.0.2.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly 11.0.0.Final</a> is available.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>If you’re not familiar with patching WildFly, check the <a href="/documentation/#12">FAQ</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="/download/">Download</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/3.0.2.Final/en-US/html/" target="_blank" rel="noopener">Documentation</a> &#93;
+                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12335442" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2017/09/11/weld-245Final/">Weld 2.4.5.Final</a>
@@ -688,256 +812,6 @@ <h2 id="_wildfly_patch">WildFly Patch</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2017/05/19/tour-around-weld-3/">Tour around Weld 3</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2017-5-19
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Matej Novotny
-                </div>
-                <p></p>
-                <div class="content">
-                  <div id="toc" class="toc">
-                  <div id="toctitle" class="title">Contents</div>
-                  <ul class="sectlevel1">
-                  <li><a href="#_async_events_and_notification_options">Async Events and Notification Options</a></li>
-                  <li><a href="#_configurators_api">Configurators API</a></li>
-                  <li><a href="#_se_bootstrap_api">SE Bootstrap API</a></li>
-                  <li><a href="#_on_demand_request_context_activation">On-demand Request Context Activation</a></li>
-                  <li><a href="#_observer_method_ordering">Observer Method Ordering</a></li>
-                  <li><a href="#_intercepting_produced_beans">Intercepting Produced Beans</a></li>
-                  <li><a href="#_trimmed_bean_archives">Trimmed Bean Archives</a></li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>This post briefly describes all the main CDI 2.0 features and elaborates on Weld-specific features we added on top of that.
-                  It is not intended as a deep-dive but rather to give you the overall idea of what is going on and what can the new release offer.
-                  So, enough talk, let&#8217;s get the show on the road!</p>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_async_events_and_notification_options">Async Events and Notification Options</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>Up until now, the only way to send events was to do so synchronously.
-                  That meant stopping the work of your current thread to instead occupy it with observer resolution and subsequent notification of observer methods.
-                  Once all that was done, the thread resumed it&#8217;s work.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>With CDI 2.0 there are asynchronous events - a 'fire &amp; forget' way of handling things.
-                  Here is how to fire such and event and how to observe it:</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>[ source, java ]</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre>// nothing new here, plain old Event is used&#x000A;    @Inject Event&lt;Payload&gt; event;&#x000A;    &#x000A;    public void sendAsyncEvent() {&#x000A;        // we use a new fireAsync method for asynchronous events&#x000A;        CompletionStage&lt;Payload&gt; eventResult = event.fireAsync(new Payload()).thenAccept(...);&#x000A;    }&#x000A;    &#x000A;    public void asyncObserver (@ObservesAsync Payload payload){ … }</pre>
-                  </div>
-                  </div>
-                  <div class="paragraph">
-                  <p>Few things to note here - first of all, the return value of <code>fireAsync</code> is <code>CompletionStage</code> allowing you to chain the work for when the event is done.
-                  You can follow-up with more tasks, react on exceptional return value and so on.
-                  Another noticeable detail is that observers which are to be notified have to have <code>@ObservesAsync</code> annotation.
-                  As you might have guessed, an observer can be notified of either synchronous (<code>@Observes</code>) or asynchronous (<code>@ObservesAsync</code>) events but never both!</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Apart from this very basic usage, async events allow you to specify <code>NotificationOptions</code> - an option allowing you to tweak the way notification works.
-                  From CDI perspective, there is currently only one standardized option and that enables usage of custom executors which will be used for notifications.
-                  But the API was designed in a generic way so that implementation can enrich it with its own options.
-                  Weld currently offers two more options - timeout and parallel execution - both of which are well described in <a href="http://docs.jboss.org/weld/reference/3.0.0.Final/en-US/html/events.html#_notification_options" target="_blank" rel="noopener">Weld docs</a>.
-                  And here is a snippet showing it in action:</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>[ source, java ]</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre>public void sendAsyncEventWithOptions() {&#x000A;        // we use a secondary version of fireAsync method with NotificationOptions parameter&#x000A;        event.fireAsync(new Payload(), NotificationOptions.of("weld.async.notification.timeout", 2000));&#x000A;    }</pre>
-                  </div>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_configurators_api">Configurators API</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>Another of the key features are <a href="http://docs.jboss.org/cdi/spec/2.0/cdi-spec.html#configurators" target="blank"><code>Configurators</code></a>.
-                  They are here to ease our work when doing small tweaks in extensions.
-                  Here is a snippet showing how easy it can be to register a new bean in <code>AfterBeanDiscovery</code> using configurator.
-                  You don&#8217;t have to create a new class implementing <code>Bean&lt;X&gt;</code> anymore:</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>[ source, java ]</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre>public void addABean(@Observes AfterBeanDiscovery event) {&#x000A;        // get an instance of BeanConfigurator&#x000A;        event.addBean()&#x000A;          // set the desired data&#x000A;          .types(Foo.class)&#x000A;          .scope(RequestScoped.class)&#x000A;          .addQualifier(Custom.CustomLiteral.INSTANCE);&#x000A;          //finally, add a callback to tell CDI how to instantiate this bean&#x000A;          .produceWith(obj -&gt; new Foo());&#x000A;    }</pre>
-                  </div>
-                  </div>
-                  <div class="paragraph">
-                  <p>Following configurators were added:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p><code>AnnotatedTypeConfigurator</code></p>
-                  </li>
-                  <li>
-                  <p><code>InjectionPointConfigurator</code></p>
-                  </li>
-                  <li>
-                  <p><code>BeanAttributesConfigurator</code></p>
-                  </li>
-                  <li>
-                  <p><code>BeanConfigurator</code></p>
-                  </li>
-                  <li>
-                  <p><code>ObserverMethodConfigurator</code></p>
-                  </li>
-                  <li>
-                  <p><code>ProducerConfigurator</code></p>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>On top of that, Weld adds one additional configurator - <a href="http://docs.jboss.org/weld/reference/latest/en-US/html_single/#_weld_enriched_container_lifecycle_events" target="_blank" rel="noopener"><code>InterceptorConfigurator</code></a>.
-                  This one allows you to observe <code>WeldAfterBeanDiscovery</code> and then use this configurator to create and register a custom interceptor from scratch.</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_se_bootstrap_api">SE Bootstrap API</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>A big change in CDI 2.0 is the SE support.
-                  Of course, Weld fans have had this for years now, but it has gone official, so that still counts, right?</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>The official CDI API is very similar to that of Weld, here is how it looks like:</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>[ source, java ]</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre>public void bootBasicContainer() {&#x000A;        SeContainerInitializer initializer = SeContainerInitializer.newInstance();&#x000A;        try (SeContainer container = initializer.initialize()) {&#x000A;            Assert.assertTrue(container.isRunning());&#x000A;        }&#x000A;    }</pre>
-                  </div>
-                  </div>
-                  <div class="paragraph">
-                  <p>This is the very basic way; you can also opt to use synthetic bean archive where you cherry-pick all the beans/interceptors/&#8230;&#8203; in your archive.
-                  <a href="http://docs.jboss.org/cdi/spec/2.0/cdi-spec.html#se_bootstrap" target="_blank" rel="noopener">CDI spec</a> describes this fairly well, so how about we instead shift our attention to what Weld SE offers on top of that?</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>A small reminder of how to boot SE container using pure Weld API:</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>[ source, java ]</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre>public void bootWeldSeContainer() {&#x000A;        Weld weld = new Weld();&#x000A;        try (WeldContainer container = weld.initialize()) {&#x000A;            container.select(FooBean.class).get();&#x000A;        }&#x000A;    }</pre>
-                  </div>
-                  </div>
-                  <div class="paragraph">
-                  <p>One of the things Weld makes easier, is when you want to create a quick extension, but don&#8217;t really want to write a whole new class which you then need to place in <code>META-INF/services</code> or register on bootstrap.
-                  You can easily create a 'synthetic extension' programatically:</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>[ source, java ]</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre>Extension testExtension = ContainerLifecycleObserver.extensionBuilder()&#x000A;        .add(afterBeanDiscovery((e) -&gt; System.out.println("Bean discovery completed!")))&#x000A;        .add(processAnnotatedType().notify((e) -&gt; {&#x000A;                if (e.getAnnotatedType().getJavaClass().getName().startsWith("com.foo")) {&#x000A;                    e.veto();&#x000A;                }&#x000A;            })).build();&#x000A;    &#x000A;    try (WeldContainer container = new Weld().addExtension(testExtension).initialize()) {&#x000A;        // Use the container...&#x000A;    }</pre>
-                  </div>
-                  </div>
-                  <div class="paragraph">
-                  <p>What we just did was to create an extension with two container lifecycle observer methods.
-                  It follows a familiar builder pattern and the body of the observer methods is specified as lambda expression.
-                  Before booting SE container, we register this extension as we would any other.
-                  For more information about this, don&#8217;t hesitate to check our older <a href="http://weld.cdi-spec.org/news/2016/02/08/weld-se-synth-lifecycle-events/">news post</a>.</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_on_demand_request_context_activation">On-demand Request Context Activation</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>Especially in SE (although not only there) you might want to activate a <code>RequestContext</code> manually for certain period of time.
-                  There are two ways to achieve that, first of which is an interceptor - <code>@ActivateRequestContext</code>.
-                  You can use that on either a method or a type (enabling it for all methods).
-                  As you might expect, it will activate the context before executing your method and shut it down afterwards.
-                  The other way is through means of built-in bean named <code>RequestContextController</code>.
-                  This bean can be injected as any other CDI bean and offers to self-explanatory methods: <code>activate</code> and <code>deactivate</code>.
-                  The obvious advantage of this approach is that you can enable the context for an extended period of time.</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_observer_method_ordering">Observer Method Ordering</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>A small but noteworthy improvement to observer methods.
-                  You can not leverage <code>@Priority</code> annotation in observer methods hence ordering them as you wish.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>[ source, java ]</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre>public void observeFirst (@Observes @Priority(1) EventPayload payload) {...}&#x000A;    &#x000A;    public void observeSecond (@Observes @Priority(2) EventPayload payload) {...}</pre>
-                  </div>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_intercepting_produced_beans">Intercepting Produced Beans</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>Up until now, anything you created using producers could not be easily intercepted.
-                  CDI 2.0 allows this for <code>@AroundInvoke</code> interceptors in two ways.
-                  There is a new method on <code>BeanManager</code> named <code>createInterceptionFactory</code> but most of the time you will rather use a built-in bean <code>InterceptionFactory</code> which can be injected as a producer method parameter.
-                  Here is a snippet:</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>[ source, java ]</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre>@Produces&#x000A;    @Dependent&#x000A;    public ProducedBean produceFoo(InterceptionFactory&lt;ProducedBean&gt; factory) {&#x000A;        factory.configure().add(Counter.Literal.INSTANCE);&#x000A;        return factory.createInterceptedInstance(new ProducedBean());&#x000A;    }</pre>
-                  </div>
-                  </div>
-                  <div class="paragraph">
-                  <p>To explain this a bit, we first inject the built-in bean with the type equal to the produced type we wish to intercept.
-                  Then we <code>configure()</code> it, which returns an <code>AnnotatedTypeConfigurator</code> allowing us to add interceptor binding.
-                  Finally, we invoke <code>InterceptionFactory.createInterceptedInstance()</code> which takes a the object we produce as a parameter.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>You can read more about this in <a href="http://docs.jboss.org/cdi/spec/2.0/cdi-spec.html#interception_factory" target="_blank" rel="noopener">this CDI spec chapter</a>.</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_trimmed_bean_archives">Trimmed Bean Archives</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>Last but not least feature we will mention are so called 'trimmed' bean archives.
-                  You can mark an explicit bean archive as trimmed in <code>beans.xml</code> by adding the <code>&lt;/trim&gt;</code> element.
-                  Such bean archive will perform an annotated type discovery as with <code>bean-discovery-mode="all"</code> but all types that don&#8217;t have a bean defining annotation or any scope annotation are then removed from the set of discovered types.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Even in this case, Weld allows you to go one step further and <a href="http://docs.jboss.org/weld/reference/latest/en-US/html/configure.html#veto-types-without-bean-defining-annotation">veto types based on regular expression</a>.
-                  It works on a similar principle but affects your whole application - it processess all types from all bean archives.
-                  Your archives will be scanned as they would be with bean discovery mode <code>all</code> and <code>ProcessAnnotatedType</code> will be fired for all found annotated types.
-                  Then, based on the regular expression you provide, annotated types which do not have a bean defining annotation and match the regular expression will be vetoed.</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 657e27ce..c3b8c268 100644
--- a/news/tags/release/index.html
+++ b/news/tags/release/index.html
@@ -141,6 +141,85 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2024/11/13/weld-600CR1/">Weld 6.0.0.CR1</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2024-11-13
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/release">release</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Matej Novotny
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>First version of the Jakarta EE TCKs has finally landed in Central and with that, we have re-enabled all remaining TCK tests and are confident enough to issue a candidate release for Weld 6!</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Note that both, Weld API and Weld Core artifacts have been released.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Here is the list of changes from last Beta:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Implement validation for unproxyability of sealed types (<a href="https://issues.redhat.com/browse/WELD-2799">WELD-2799</a>)</p>
+                  </li>
+                  <li>
+                  <p>Correct injection into <code>@Resource</code> fields of beans registered through extensions (<a href="https://issues.redhat.com/browse/WELD-2798">WELD-2798</a>)</p>
+                  </li>
+                  <li>
+                  <p>Improve the algorithm that determines <code>BeanManager</code> instance for synthetic beans coming from build compatible extensions (<a href="https://issues.redhat.com/browse/WELD-2794">WELD-2794</a>)</p>
+                  </li>
+                  <li>
+                  <p>Weld OSGi bundle now correctly exports <code>org.jboss.weld.util.reflection</code> (<a href="https://issues.redhat.com/browse/WELD-2793">WELD-2793</a>)</p>
+                  </li>
+                  <li>
+                  <p>Weld OSGi bundle now contains imports for built-in bean proxies (<a href="https://issues.redhat.com/browse/WELD-2796">WELD-2796</a>)</p>
+                  </li>
+                  <li>
+                  <p>Re-introduce Jakarta EE CDI TCK into continuous integration (<a href="https://issues.redhat.com/browse/WELD-2778">WELD-2778</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>The TCK artifact in Central is not yet final (it is <code>M1</code>) but it is enough to make sure Weld passes all related CDI tests with WildFly</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Fix possible file leak in <code>org.jboss.weld.util.ServiceLoader</code> (<a href="https://issues.redhat.com/browse/WELD-2800">WELD-2800</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>This was only reported during GlassFish testing and affected just Windows machines</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Resolve license conflict of <code>jboss-logging-processor</code> inside shaded Weld SE JAR (<a href="https://issues.redhat.com/browse/WELD-2795">WELD-2795</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>As per usual, please report any issues you discover with this release so that we can squash those bugs.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="/download/">Download</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/6.0.0.CR1/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=12429945" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2024/08/27/weld-513Final/">Weld 5.1.3.Final</a>
@@ -840,65 +919,6 @@ <h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2022/06/24/weld-501Final/">Weld 5.0.1.Final</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2022-6-24
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/release">release</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Matej Novotny
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>Weld Core 5.0.1.Final is now available and comes with Weld API 5.0.SP2.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Main highlights are as follows:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Updated all CDI related versions (API and TCKs) to their latest released variants and made sure we are passing</p>
-                  </li>
-                  <li>
-                  <p>Updated many other EE 10 APIs to their latest releases</p>
-                  </li>
-                  <li>
-                  <p>We are once again fully continuously testing against an EE container (nightly WildFly builds) which helped us polish more bumps in tests and code</p>
-                  </li>
-                  <li>
-                  <p>Tomcat 10.1 is available and supports EE 10, so we have upgraded to test against that and can therefore confirm our support for servlets is working well</p>
-                  </li>
-                  <li>
-                  <p>Jetty support is at the moment not verified as there is no public Jetty 12 release to test against</p>
-                  </li>
-                  <li>
-                  <p>Reviewed Servlet related parts of our documentation and updated them</p>
-                  </li>
-                  <li>
-                  <p>Reviewed Weld SE-Servlet cooperation and renewed continuous testing for it</p>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>As always, if you find further issues with Weld 5, let us know and we&#8217;ll try to help.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>&#91; <a href="/download/">Download</a> &#93;
-                  &#91; <a href="http://docs.jboss.org/weld/reference/5.0.1.Final/en-US/html_single/" target="_blank" rel="noopener">Documentation</a> &#93;
-                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12385166" 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 f82e11b0..5a5b64ca 100644
--- a/news/tags/release/page/2.html
+++ b/news/tags/release/page/2.html
@@ -141,6 +141,65 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2022/06/24/weld-501Final/">Weld 5.0.1.Final</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2022-6-24
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/release">release</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Matej Novotny
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>Weld Core 5.0.1.Final is now available and comes with Weld API 5.0.SP2.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Main highlights are as follows:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Updated all CDI related versions (API and TCKs) to their latest released variants and made sure we are passing</p>
+                  </li>
+                  <li>
+                  <p>Updated many other EE 10 APIs to their latest releases</p>
+                  </li>
+                  <li>
+                  <p>We are once again fully continuously testing against an EE container (nightly WildFly builds) which helped us polish more bumps in tests and code</p>
+                  </li>
+                  <li>
+                  <p>Tomcat 10.1 is available and supports EE 10, so we have upgraded to test against that and can therefore confirm our support for servlets is working well</p>
+                  </li>
+                  <li>
+                  <p>Jetty support is at the moment not verified as there is no public Jetty 12 release to test against</p>
+                  </li>
+                  <li>
+                  <p>Reviewed Servlet related parts of our documentation and updated them</p>
+                  </li>
+                  <li>
+                  <p>Reviewed Weld SE-Servlet cooperation and renewed continuous testing for it</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>As always, if you find further issues with Weld 5, let us know and we&#8217;ll try to help.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="/download/">Download</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/5.0.1.Final/en-US/html_single/" target="_blank" rel="noopener">Documentation</a> &#93;
+                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12385166" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2022/06/08/weld-500SP2/">Weld 5.0.0.SP2</a>
@@ -881,112 +940,6 @@ <h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2021/03/22/weld-401Final/">Weld 4.0.1.Final</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2021-3-22
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/release">release</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Matej Novotny
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>First maintainance release of Weld 4 is now available along with API version 4.0.SP1.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>The crux of this release is (much like 3.1.7.Final) a rework of Weld&#8217;s default class defining capabilities.
-                  With 4.0.1.Final you should no longer see illegal reflective access warning so long as you are on JDK 11 or newer.
-                  More details on this are below or in the respective <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/4.0.SP1/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/4.0.SP1/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>
-                  <li>
-                  <p><code>ProxyFactory</code> now creates determininistic proxy names (<a href="https://issues.jboss.org/browse/WELD-2618" target="_blank" rel="noopener">WELD-2618</a>)</p>
-                  </li>
-                  <li>
-                  <p>Decorators for interfaces with non-decorated default method now work properly (<a href="https://issues.jboss.org/browse/WELD-2647" target="_blank" rel="noopener">WELD-2647</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/4.0.1.Final/en-US/html_single/" target="_blank" rel="noopener">Documentation</a> &#93;
-                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12352776" 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 b4276a9e..3addd26b 100644
--- a/news/tags/release/page/3.html
+++ b/news/tags/release/page/3.html
@@ -141,6 +141,112 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2021/03/22/weld-401Final/">Weld 4.0.1.Final</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2021-3-22
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/release">release</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Matej Novotny
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>First maintainance release of Weld 4 is now available along with API version 4.0.SP1.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>The crux of this release is (much like 3.1.7.Final) a rework of Weld&#8217;s default class defining capabilities.
+                  With 4.0.1.Final you should no longer see illegal reflective access warning so long as you are on JDK 11 or newer.
+                  More details on this are below or in the respective <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/4.0.SP1/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/4.0.SP1/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>
+                  <li>
+                  <p><code>ProxyFactory</code> now creates determininistic proxy names (<a href="https://issues.jboss.org/browse/WELD-2618" target="_blank" rel="noopener">WELD-2618</a>)</p>
+                  </li>
+                  <li>
+                  <p>Decorators for interfaces with non-decorated default method now work properly (<a href="https://issues.jboss.org/browse/WELD-2647" target="_blank" rel="noopener">WELD-2647</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/4.0.1.Final/en-US/html_single/" target="_blank" rel="noopener">Documentation</a> &#93;
+                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12352776" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2021/03/18/weld-317Final/">Weld 3.1.7.Final</a>
@@ -1091,111 +1197,6 @@ <h2 id="_wildfly_patch">WildFly Patch</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2019/05/07/weld-311Final/">Weld 3.1.1.Final</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2019-5-7
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/release">release</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Matej Novotny
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>Weld 3.1.1.Final is out, it is a rather small nonetheless important maintenance release.
-                  There is bunch of fixes present here; notably one for context propagation API that could cause some headaches with context seemingly not propagating.
-                  Moving on, we also have some improvements to asynchronous events on default executors or ordering on <code>ProcessAnnotatedType</code> events.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Fixes and improvements:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Weld API/SPI</p>
-                  </li>
-                  <li>
-                  <p>Weld Core</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p><code>WeldAlterableContext#clearAndSet()</code> was incorrectly leaving some caches behind (<a href="https://issues.jboss.org/browse/WELD-2566" target="_blank" rel="noopener">WELD-2566</a>)</p>
-                  </li>
-                  <li>
-                  <p>Fix serializability issue with intercepted session beans having private methods (<a href="https://issues.jboss.org/browse/WELD-2574" target="_blank" rel="noopener">WELD-2574</a>)</p>
-                  </li>
-                  <li>
-                  <p>Asynchronous event notification on default executor should preserve TCCL (<a href="https://issues.jboss.org/browse/WELD-2573" target="_blank" rel="noopener">WELD-2573</a>)</p>
-                  </li>
-                  <li>
-                  <p>Fix ordering of <code>ProcessAnnotatedType</code> events via <code>@Priority</code> (<a href="https://issues.jboss.org/browse/WELD-2568" target="_blank" rel="noopener">WELD-2568</a>)</p>
-                  </li>
-                  <li>
-                  <p>Small optimization for distributed environment when bean index is empty (<a href="https://issues.jboss.org/browse/WELD-2577" target="_blank" rel="noopener">WELD-2577</a>)</p>
-                  </li>
-                  <li>
-                  <p>Custom <code>InjectionTarget</code> now invokes any present <code>dispose()</code> (<a href="https://issues.jboss.org/browse/WELD-2580" target="_blank" rel="noopener">WELD-2580</a>)</p>
-                  </li>
-                  <li>
-                  <p>Align behaviour of self-invocation of otherwise intercepted method from within private final observer method (<a href="https://issues.jboss.org/browse/WELD-2571" target="_blank" rel="noopener">WELD-2571</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Weld SE</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Allow to specify custom <code>DiscoveryStrategy</code> via service loader mechanism (<a href="https://issues.jboss.org/browse/WELD-2578" target="_blank" rel="noopener">WELD-2578</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Other</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Update tooling around documentation builds (<a href="https://issues.jboss.org/browse/WELD-2564" target="_blank" rel="noopener">WELD-2564</a>)</p>
-                  </li>
-                  <li>
-                  <p>Update JBoss classfilewriter to newer version working on JDK 12 (<a href="https://issues.jboss.org/browse/WELD-2572" target="_blank" rel="noopener">WELD-2572</a>)</p>
-                  </li>
-                  <li>
-                  <p>Fix Probe functional tests on latest Firefox (<a href="https://issues.jboss.org/browse/WELD-2579" target="_blank" rel="noopener">WELD-2579</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_wildfly_patch">WildFly Patch</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>This time around, the <a href="http://download.jboss.org/weld/3.1.1.Final/wildfly-16.0.0.Final-weld-3.1.1.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly 16.0.0.Final</a> is available.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>If you’re not familiar with patching WildFly, check the <a href="/documentation/#12">FAQ</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>&#91; <a href="/download/">Download</a> &#93;
-                  &#91; <a href="http://docs.jboss.org/weld/reference/3.1.1.Final/en-US/html/" target="_blank" rel="noopener">Documentation</a> &#93;
-                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12340657" 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 140b0834..df3f14d3 100644
--- a/news/tags/release/page/4.html
+++ b/news/tags/release/page/4.html
@@ -141,6 +141,111 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2019/05/07/weld-311Final/">Weld 3.1.1.Final</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2019-5-7
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/release">release</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Matej Novotny
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>Weld 3.1.1.Final is out, it is a rather small nonetheless important maintenance release.
+                  There is bunch of fixes present here; notably one for context propagation API that could cause some headaches with context seemingly not propagating.
+                  Moving on, we also have some improvements to asynchronous events on default executors or ordering on <code>ProcessAnnotatedType</code> events.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Fixes and improvements:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Weld API/SPI</p>
+                  </li>
+                  <li>
+                  <p>Weld Core</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p><code>WeldAlterableContext#clearAndSet()</code> was incorrectly leaving some caches behind (<a href="https://issues.jboss.org/browse/WELD-2566" target="_blank" rel="noopener">WELD-2566</a>)</p>
+                  </li>
+                  <li>
+                  <p>Fix serializability issue with intercepted session beans having private methods (<a href="https://issues.jboss.org/browse/WELD-2574" target="_blank" rel="noopener">WELD-2574</a>)</p>
+                  </li>
+                  <li>
+                  <p>Asynchronous event notification on default executor should preserve TCCL (<a href="https://issues.jboss.org/browse/WELD-2573" target="_blank" rel="noopener">WELD-2573</a>)</p>
+                  </li>
+                  <li>
+                  <p>Fix ordering of <code>ProcessAnnotatedType</code> events via <code>@Priority</code> (<a href="https://issues.jboss.org/browse/WELD-2568" target="_blank" rel="noopener">WELD-2568</a>)</p>
+                  </li>
+                  <li>
+                  <p>Small optimization for distributed environment when bean index is empty (<a href="https://issues.jboss.org/browse/WELD-2577" target="_blank" rel="noopener">WELD-2577</a>)</p>
+                  </li>
+                  <li>
+                  <p>Custom <code>InjectionTarget</code> now invokes any present <code>dispose()</code> (<a href="https://issues.jboss.org/browse/WELD-2580" target="_blank" rel="noopener">WELD-2580</a>)</p>
+                  </li>
+                  <li>
+                  <p>Align behaviour of self-invocation of otherwise intercepted method from within private final observer method (<a href="https://issues.jboss.org/browse/WELD-2571" target="_blank" rel="noopener">WELD-2571</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Weld SE</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Allow to specify custom <code>DiscoveryStrategy</code> via service loader mechanism (<a href="https://issues.jboss.org/browse/WELD-2578" target="_blank" rel="noopener">WELD-2578</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Other</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Update tooling around documentation builds (<a href="https://issues.jboss.org/browse/WELD-2564" target="_blank" rel="noopener">WELD-2564</a>)</p>
+                  </li>
+                  <li>
+                  <p>Update JBoss classfilewriter to newer version working on JDK 12 (<a href="https://issues.jboss.org/browse/WELD-2572" target="_blank" rel="noopener">WELD-2572</a>)</p>
+                  </li>
+                  <li>
+                  <p>Fix Probe functional tests on latest Firefox (<a href="https://issues.jboss.org/browse/WELD-2579" target="_blank" rel="noopener">WELD-2579</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_wildfly_patch">WildFly Patch</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>This time around, the <a href="http://download.jboss.org/weld/3.1.1.Final/wildfly-16.0.0.Final-weld-3.1.1.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly 16.0.0.Final</a> is available.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>If you’re not familiar with patching WildFly, check the <a href="/documentation/#12">FAQ</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="/download/">Download</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/3.1.1.Final/en-US/html/" target="_blank" rel="noopener">Documentation</a> &#93;
+                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12340657" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2019/02/06/weld-310Final/">Weld 3.1.0.Final</a>
@@ -1429,143 +1534,6 @@ <h2 id="_wildfly_patch">WildFly Patch</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2017/08/25/weld-301Final/">Weld 3.0.1.Final</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2017-8-25
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/release">release</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Matej Novotny
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>Weld 3.0.1.Final is out and it brings some bugfixes as well as new version of Weld API - 3.0.SP1.
-                  Among the new things you can find sweet stuff such as an expansion to CDI 2 <code>BeanConfigurator</code> API or the ability to detect that injected object is Weld proxy.
-                  Wait, not only detect - you can also use it do get <code>Metadata</code> or even retrieve the actual contextual instance hidden beneath.
-                  So let&#8217;s see the summary of fixes and improvements, shall we?</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Notable fixes and improvements:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Weld Core</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Revised support for Java 8 default methods (<a href="https://issues.jboss.org/browse/WELD-2407" target="_blank" rel="noopener">WELD-2407</a> and <a href="https://issues.jboss.org/browse/WELD-2405" target="_blank" rel="noopener">WELD-2405</a>)</p>
-                  </li>
-                  <li>
-                  <p>Corrected MIME types for all POMs in Weld core - Nexus 3 will love us now! (<a href="https://issues.jboss.org/browse/WELD-2417" target="_blank" rel="noopener">WELD-2417</a>)</p>
-                  </li>
-                  <li>
-                  <p>Fixed how proxies are created for signed packages (<a href="https://issues.jboss.org/browse/WELD-2402" target="_blank" rel="noopener">WELD-2402</a>)</p>
-                  </li>
-                  <li>
-                  <p>Portable extension events should now be fired in accordance with specification <a href="https://issues.jboss.org/browse/WELD-2393" target="_blank" rel="noopener">WELD-2393</a></p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Weld SE</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Synthetic bean archive can now have discovery mode <code>annotated</code> (<a href="https://issues.jboss.org/browse/WELD-2386" target="_blank" rel="noopener">WELD-2386</a>)</p>
-                  </li>
-                  <li>
-                  <p>Added a convenient static method <code>WeldContainer.current()</code> allowing you to quickly grab your running instance (<a href="https://issues.jboss.org/browse/WELD-2399" target="_blank" rel="noopener">WELD-2399</a>)</p>
-                  </li>
-                  <li>
-                  <p>Fixed a glitch when starting SE container and adding packages via <code>Weld.addPackages()</code> <a href="https://issues.jboss.org/browse/WELD-2395" target="_blank" rel="noopener">WELD-2395</a></p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Weld API/SPI</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Added a way to detect proxies and subclasses (<a href="https://issues.jboss.org/browse/WELD-2407" target="_blank" rel="noopener">WELD-2407</a>)</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Every Weld-enhanced object (subclass/proxy) will now implement <a href="https://github.com/weld/api/tree/3.0.SP1/weld/src/main/java/org/jboss/weld/proxy">new marker interface(s)</a> which grant access to additional data about the bean</p>
-                  </li>
-                  <li>
-                  <p>This also allows to retrieve the underlying contextual instance</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Added <code>WeldBeanConfigurator</code> to API - allows to select an <code>@Alternative</code> which was created using <code>BeanConfigurator</code> (<a href="https://issues.jboss.org/browse/WELD-2412" target="_blank" rel="noopener">WELD-2412</a>)</p>
-                  </li>
-                  <li>
-                  <p>We have enhanced the <code>Environment</code> in Weld SPI so that integrators define whether their bean archives are "EE module aware" or not (<a href="https://issues.jboss.org/browse/WELD-2398" target="_blank" rel="noopener">WELD-2398</a>)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Other</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>Under the <code>jboss-as</code> directory of Weld source code, you can now make use of new profiles to create WildFly patches yourself <a href="https://issues.jboss.org/browse/WELD-2397" target="_blank" rel="noopener">WELD-2397</a></p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>To learn more about this, please refer to the <a href="https://github.com/weld/core/blob/3.0.1.Final/README.md#creating-a-patch-file-for-wildfly"><code>README</code> file in our repository</a></p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Weld SE and Weld Servlet now explicitly depends on <code>jboss-classfilewriter</code> in version 1.2+ <a href="https://issues.jboss.org/browse/WELD-2406" target="_blank" rel="noopener">WELD-2406</a></p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_wildfly_patch">WildFly Patch</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>As usual, there is a <a href="http://download.jboss.org/weld/3.0.1.Final/wildfly-10.1.0.Final-weld-3.0.1.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly 10.1.0.Final</a> is available.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>But, for those of you who like to stay sharp, we have also created a <a href="http://download.jboss.org/weld/3.0.1.Final/wildfly-11.0.0.Beta1-weld-3.0.1.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly 11.0.0.Beta1</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Please note that there is currently a <a href="https://issues.jboss.org/browse/WFLY-9240">known issue</a> with security context propagation in Weld 3 for WildFly 11.
-                  Though this should only concern people who use the combination of Elytron subsystem and asynchronous CDI events.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>If you’re not familiar with patching WildFly, check the <a href="/documentation/#12">FAQ</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>&#91; <a href="/download/">Download</a> &#93;
-                  &#91; <a href="http://docs.jboss.org/weld/reference/3.0.1.Final/en-US/html/" target="_blank" rel="noopener">Documentation</a> &#93;
-                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12334698" target="_blank" rel="noopener">Release notes</a> &#93;</p>
-                  </div>
-                  </div>
-                  </div>
-                </div>
-                <hr>
-              </div>
               <div class="pagination-links"><a href="/news/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 2b912283..9cec49f3 100644
--- a/news/tags/release/page/5.html
+++ b/news/tags/release/page/5.html
@@ -141,6 +141,143 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2017/08/25/weld-301Final/">Weld 3.0.1.Final</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2017-8-25
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/release">release</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Matej Novotny
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>Weld 3.0.1.Final is out and it brings some bugfixes as well as new version of Weld API - 3.0.SP1.
+                  Among the new things you can find sweet stuff such as an expansion to CDI 2 <code>BeanConfigurator</code> API or the ability to detect that injected object is Weld proxy.
+                  Wait, not only detect - you can also use it do get <code>Metadata</code> or even retrieve the actual contextual instance hidden beneath.
+                  So let&#8217;s see the summary of fixes and improvements, shall we?</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Notable fixes and improvements:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Weld Core</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Revised support for Java 8 default methods (<a href="https://issues.jboss.org/browse/WELD-2407" target="_blank" rel="noopener">WELD-2407</a> and <a href="https://issues.jboss.org/browse/WELD-2405" target="_blank" rel="noopener">WELD-2405</a>)</p>
+                  </li>
+                  <li>
+                  <p>Corrected MIME types for all POMs in Weld core - Nexus 3 will love us now! (<a href="https://issues.jboss.org/browse/WELD-2417" target="_blank" rel="noopener">WELD-2417</a>)</p>
+                  </li>
+                  <li>
+                  <p>Fixed how proxies are created for signed packages (<a href="https://issues.jboss.org/browse/WELD-2402" target="_blank" rel="noopener">WELD-2402</a>)</p>
+                  </li>
+                  <li>
+                  <p>Portable extension events should now be fired in accordance with specification <a href="https://issues.jboss.org/browse/WELD-2393" target="_blank" rel="noopener">WELD-2393</a></p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Weld SE</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Synthetic bean archive can now have discovery mode <code>annotated</code> (<a href="https://issues.jboss.org/browse/WELD-2386" target="_blank" rel="noopener">WELD-2386</a>)</p>
+                  </li>
+                  <li>
+                  <p>Added a convenient static method <code>WeldContainer.current()</code> allowing you to quickly grab your running instance (<a href="https://issues.jboss.org/browse/WELD-2399" target="_blank" rel="noopener">WELD-2399</a>)</p>
+                  </li>
+                  <li>
+                  <p>Fixed a glitch when starting SE container and adding packages via <code>Weld.addPackages()</code> <a href="https://issues.jboss.org/browse/WELD-2395" target="_blank" rel="noopener">WELD-2395</a></p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Weld API/SPI</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Added a way to detect proxies and subclasses (<a href="https://issues.jboss.org/browse/WELD-2407" target="_blank" rel="noopener">WELD-2407</a>)</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Every Weld-enhanced object (subclass/proxy) will now implement <a href="https://github.com/weld/api/tree/3.0.SP1/weld/src/main/java/org/jboss/weld/proxy">new marker interface(s)</a> which grant access to additional data about the bean</p>
+                  </li>
+                  <li>
+                  <p>This also allows to retrieve the underlying contextual instance</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Added <code>WeldBeanConfigurator</code> to API - allows to select an <code>@Alternative</code> which was created using <code>BeanConfigurator</code> (<a href="https://issues.jboss.org/browse/WELD-2412" target="_blank" rel="noopener">WELD-2412</a>)</p>
+                  </li>
+                  <li>
+                  <p>We have enhanced the <code>Environment</code> in Weld SPI so that integrators define whether their bean archives are "EE module aware" or not (<a href="https://issues.jboss.org/browse/WELD-2398" target="_blank" rel="noopener">WELD-2398</a>)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Other</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>Under the <code>jboss-as</code> directory of Weld source code, you can now make use of new profiles to create WildFly patches yourself <a href="https://issues.jboss.org/browse/WELD-2397" target="_blank" rel="noopener">WELD-2397</a></p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>To learn more about this, please refer to the <a href="https://github.com/weld/core/blob/3.0.1.Final/README.md#creating-a-patch-file-for-wildfly"><code>README</code> file in our repository</a></p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Weld SE and Weld Servlet now explicitly depends on <code>jboss-classfilewriter</code> in version 1.2+ <a href="https://issues.jboss.org/browse/WELD-2406" target="_blank" rel="noopener">WELD-2406</a></p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_wildfly_patch">WildFly Patch</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>As usual, there is a <a href="http://download.jboss.org/weld/3.0.1.Final/wildfly-10.1.0.Final-weld-3.0.1.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly 10.1.0.Final</a> is available.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>But, for those of you who like to stay sharp, we have also created a <a href="http://download.jboss.org/weld/3.0.1.Final/wildfly-11.0.0.Beta1-weld-3.0.1.Final-patch.zip" target="_blank" rel="noopener">patch for WildFly 11.0.0.Beta1</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Please note that there is currently a <a href="https://issues.jboss.org/browse/WFLY-9240">known issue</a> with security context propagation in Weld 3 for WildFly 11.
+                  Though this should only concern people who use the combination of Elytron subsystem and asynchronous CDI events.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>If you’re not familiar with patching WildFly, check the <a href="/documentation/#12">FAQ</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="/download/">Download</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/3.0.1.Final/en-US/html/" target="_blank" rel="noopener">Documentation</a> &#93;
+                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12334698" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2017/06/14/weld-244Final/">Weld 2.4.4.Final</a>
@@ -1005,184 +1142,6 @@ <h2 id="_wildfly_patch">WildFly Patch</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2016/08/19/weld-240CR1/">First release candidate of Weld 2.4</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2016-8-19
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/release">release</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Martin Kouba
-                </div>
-                <p></p>
-                <div class="content">
-                  <div id="toc" class="toc">
-                  <div id="toctitle" class="title">Contents</div>
-                  <ul class="sectlevel1">
-                  <li><a href="#_removed_dependency_on_com_google_guavaguava">Removed dependency on <code>com.google.guava:guava</code></a></li>
-                  <li><a href="#_enhanced_version_of_javax_enterprise_inject_instance">Enhanced version of <code>javax.enterprise.inject.Instance</code></a></li>
-                  <li><a href="#_veto_annotatedtype_not_annotated_with_bean_defining_annotation">Veto <code>AnnotatedType</code> not annotated with bean defining annotation</a></li>
-                  <li><a href="#_activaterequestscope_moved_to_weld_api"><code>@ActivateRequestScope</code> moved to Weld API</a></li>
-                  <li><a href="#_improved_rolling_upgrades_support">Improved rolling upgrades support</a></li>
-                  <li><a href="#_events_reflect_the_output_of_cdi_494">Events - reflect the output of CDI-494</a></li>
-                  <li><a href="#_probe_allow_to_filter_unused_beans">Probe - allow to filter unused beans</a></li>
-                  <li><a href="#_cleanup">Cleanup</a></li>
-                  <li><a href="#_initial_java_9_support">Initial Java 9 support</a></li>
-                  <li><a href="#_bugs">Bugs</a></li>
-                  <li><a href="#_wildfly_patch">WildFly Patch</a></li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>I am pleased to announce the first release candidate of Weld 2.4 (CDI 1.2).
-                  See also <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12330683" target="_blank" rel="noopener">the release details</a>.
-                  Thanks to everyone involved in this release!</p>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_removed_dependency_on_com_google_guavaguava">Removed dependency on <code>com.google.guava:guava</code></h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>Weld does not depend on <code>com.google.guava:guava</code> anymore (actually, Weld 3 does not depend on guava since 3.0.0.Alpha2).
-                  This significantly reduces the footprint of both Weld SE and Weld Servlet.
-                  The dependency is also not bundled with shaded artifacts for Weld SE and Weld Servlet.</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_enhanced_version_of_javax_enterprise_inject_instance">Enhanced version of <code>javax.enterprise.inject.Instance</code></h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>Weld now provides <code>org.jboss.weld.inject.WeldInstance</code> - an enhanced version of <code>javax.enterprise.inject.Instance</code>.
-                  There are three additional methods - <code>getHandler()</code>, <code>handlers()</code> and <code>isResolvable()</code>.
-                  A handler allows to inspect the metadata of the relevant bean and to destroy the underlying contextual instance.
-                  <code>isResolvable()</code> is just a convenient method - a replacement for <code>!isUnsatisfied() &amp;&amp; !isAmbiguous()</code>.
-                  For more details see also <a href="http://docs.jboss.org/weld/reference/2.4.0.CR1/en-US/html/injection.html#_enhanced_version_of_literal_javax_enterprise_inject_instance_literal" target="_blank" rel="noopener">the reference guide</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p><code>WeldInstance</code> is automatically available in Weld SE and Weld Servlet where the Weld API is always on the class path.
-                  It is also available in Weld-powered EE containers. In this case, users would have to compile their application against the Weld API and exclude the Weld API artifact from the deployment (e.g. use provided scope in Maven).</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>This functionality is based on a new proposal for <a href="https://issues.jboss.org/browse/CDI-589" target="_blank" rel="noopener">CDI-589</a>.</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_veto_annotatedtype_not_annotated_with_bean_defining_annotation">Veto <code>AnnotatedType</code> not annotated with bean defining annotation</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>Sometimes it might be useful to process all types during bootstrap, i.e. fire/observe <code>ProcessAnnotatedType</code> event for each Java class discovered, but veto types which are <strong>not annotated with a bean defining annotation</strong>.
-                  The main reason is that not all classes that meet all of the necessary conditions are intended to become beans.
-                  And so vetoing such types helps to conserve memory used by the container.
-                  Note that if you use <code>bean-discovey-mode=annotated</code> (implicit bean archive) then no <code>ProcessAnnotatedType</code> will be fired for any such type because it’s not discovered at all.
-                  And there might be portable extensions which use <code>ProcessAnnotatedType</code> to extract some important information from classes which are not beans.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Therefore, Weld allows to use <code>bean-discovey-mode=all</code> (explicit bean archive) and veto types without a bean defining annotation whose <code>AnnotatedType#getJavaClass().getName()</code> matches a <a href="http://docs.jboss.org/weld/reference/2.4.0.CR1/en-US/html/configure.html#veto-types-without-bean-defining-annotation">regular expression</a>.
-                  In other words, a type is vetoed if its name matches a regular expression and at the same time is not annotated with a bean defining annotation.
-                  This functionality is implemented as a built-in portable extension processing all types from all bean archives (it was already doable using an extension but we believe it&#8217;s more convenient to have this functionality out of the box).</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>This is a workaround for problems of <code>bean-discovey-mode=annotated</code> mentioned in <a href="https://issues.jboss.org/browse/CDI-420" target="_blank" rel="noopener">CDI-420</a>.</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_activaterequestscope_moved_to_weld_api"><code>@ActivateRequestScope</code> moved to Weld API</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>This interceptor binding can be used to activate the request scope within a business method invocation.
-                  It was previously part of the Weld SE but we believe it might be useful in any environment.
-                  See also <a href="https://issues.jboss.org/browse/WELD-2150" target="_blank" rel="noopener">WELD-2150</a>.</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_improved_rolling_upgrades_support">Improved rolling upgrades support</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p><a href="https://issues.jboss.org/secure/ViewProfile.jspa?name=lprimak">Lenny Primak</a> (a Weld community member - thanks for the report again!) struggled with rolling upgrades on certain application servers (Payara, GlassFish).
-                  Therefore, a new configuration property was introduced.
-                  This property allows to specify a delimiter which is used to abbreviate a bean archive identifier (which is usually derived from the archive name) before used as a part of an identifier of an internal component (such as bean).
-                  See also <a href="http://docs.jboss.org/weld/reference/2.4.0.CR1/en-US/html/configure.html#_rolling_upgrades_id_delimiter" target="_blank" rel="noopener">the reference guide</a> and <a href="https://issues.jboss.org/browse/WELD-2064" target="_blank" rel="noopener">WELD-2064</a>.</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_events_reflect_the_output_of_cdi_494">Events - reflect the output of CDI-494</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>This change reflects the clarification around <code>Event</code> operations - <em>"A wildcard type is not considered an unresolvable type variable"</em>.
-                  See also <a href="https://issues.jboss.org/browse/WELD-2137" target="_blank" rel="noopener">WELD-2137</a> and <a href="https://issues.jboss.org/browse/CDI-494" target="_blank" rel="noopener">CDI-494</a>.
-                  Simply said, the snippet below and similar ones should now work:</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@Inject Event&lt;List&lt;?&gt;&gt; event;&#x000A;    &#x000A;    public void fireLists() {&#x000A;      List&lt;String&gt; stringList = new ArrayList&lt;&gt;();&#x000A;      event.fire(stringList);&#x000A;      List&lt;Integer&gt; intList = new ArrayList&lt;&gt;();&#x000A;      event.fire(intList);&#x000A;    }&#x000A;    &#x000A;    void observeAllLists(@Observes List&lt;?&gt; anyList) {&#x000A;      // Will be notified&#x000A;    }</code></pre>
-                  </div>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_probe_allow_to_filter_unused_beans">Probe - allow to filter unused beans</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>The Probe development tool now identifies beans which are most likely unused (a bean is considered unused if it has no direct dependents, does not declare any observer or producer methods, is not annotated with <code>@Named</code> and is not a built-in bean, extension, interceptor or decorator).
-                  This might be useful to identify types suitable for vetoing as mentioned in <a href="#_veto_code_annotatedtype_code_not_annotated_with_bean_defining_annotation">[_veto_code_annotatedtype_code_not_annotated_with_bean_defining_annotation]</a>.</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_cleanup">Cleanup</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>Weld has underwent an internal cleanup. A lot of deprecated and unused classes were removed.</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_initial_java_9_support">Initial Java 9 support</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>It&#8217;s now possible to build Weld with Java 9.
-                  Note that this does not mean that Weld is modularized in a <a href="http://openjdk.java.net/projects/jigsaw/" target="_blank" rel="noopener">Jigsaw way</a>.
-                  It&#8217;s just the first step on a long road ;-).</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_bugs">Bugs</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>Last but not least - a few bugs were killed.
-                  Weld SE - provided <code>ClassLoader</code> is also used to load extensions (<a href="https://issues.jboss.org/browse/WELD-2209" target="_blank" rel="noopener">WELD-2209</a>).
-                  <code>AnnotatedTypeValidator</code> does consider extended interfaces (<a href="https://issues.jboss.org/browse/WELD-2221" target="_blank" rel="noopener">WELD-2221</a>).
-                  Invocation of a JDK8 default method should be intercepted (this only works if using <code>jboss-classfilewriter</code> 1.2.0.Beta1+, <a href="https://issues.jboss.org/browse/WELD-2093" target="_blank" rel="noopener">WELD-2093</a>).</p>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_wildfly_patch">WildFly Patch</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>As usual, a <a href="http://download.jboss.org/weld/2.4.0.CR1/wildfly-10.0.0.Final-weld-2.4.0.CR1-patch.zip" target="_blank" rel="noopener">patch for WildFly</a> is available. This time the target platform is <strong>WildFly 10.0.0.Final</strong>.  If you’re not familiar with patching WildFly, check <a href="http://blog.eisele.net/2015/02/playing-with-weld-probe-see-all-of-your.html" target="_blank" rel="noopener">Markus&#8217;s tutorial</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>&#91; <a href="http://docs.jboss.org/cdi/api/1.2/" target="_blank" rel="noopener">CDI 1.2 API</a> &#93;
-                  &#91; <a href="/download/">Download</a> &#93;
-                  &#91; <a href="http://docs.jboss.org/weld/reference/2.4.0.CR1/en-US/html/" target="_blank" rel="noopener">Documentation</a> &#93;
-                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12330683" target="_blank" rel="noopener">Release notes</a> &#93;</p>
-                  </div>
-                  </div>
-                  </div>
-                </div>
-                <hr>
-              </div>
               <div class="pagination-links"><a href="/news/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 1be39dbb..4df51e01 100644
--- a/news/tags/release/page/6.html
+++ b/news/tags/release/page/6.html
@@ -141,6 +141,184 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2016/08/19/weld-240CR1/">First release candidate of Weld 2.4</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2016-8-19
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/release">release</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Martin Kouba
+                </div>
+                <p></p>
+                <div class="content">
+                  <div id="toc" class="toc">
+                  <div id="toctitle" class="title">Contents</div>
+                  <ul class="sectlevel1">
+                  <li><a href="#_removed_dependency_on_com_google_guavaguava">Removed dependency on <code>com.google.guava:guava</code></a></li>
+                  <li><a href="#_enhanced_version_of_javax_enterprise_inject_instance">Enhanced version of <code>javax.enterprise.inject.Instance</code></a></li>
+                  <li><a href="#_veto_annotatedtype_not_annotated_with_bean_defining_annotation">Veto <code>AnnotatedType</code> not annotated with bean defining annotation</a></li>
+                  <li><a href="#_activaterequestscope_moved_to_weld_api"><code>@ActivateRequestScope</code> moved to Weld API</a></li>
+                  <li><a href="#_improved_rolling_upgrades_support">Improved rolling upgrades support</a></li>
+                  <li><a href="#_events_reflect_the_output_of_cdi_494">Events - reflect the output of CDI-494</a></li>
+                  <li><a href="#_probe_allow_to_filter_unused_beans">Probe - allow to filter unused beans</a></li>
+                  <li><a href="#_cleanup">Cleanup</a></li>
+                  <li><a href="#_initial_java_9_support">Initial Java 9 support</a></li>
+                  <li><a href="#_bugs">Bugs</a></li>
+                  <li><a href="#_wildfly_patch">WildFly Patch</a></li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>I am pleased to announce the first release candidate of Weld 2.4 (CDI 1.2).
+                  See also <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12330683" target="_blank" rel="noopener">the release details</a>.
+                  Thanks to everyone involved in this release!</p>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_removed_dependency_on_com_google_guavaguava">Removed dependency on <code>com.google.guava:guava</code></h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>Weld does not depend on <code>com.google.guava:guava</code> anymore (actually, Weld 3 does not depend on guava since 3.0.0.Alpha2).
+                  This significantly reduces the footprint of both Weld SE and Weld Servlet.
+                  The dependency is also not bundled with shaded artifacts for Weld SE and Weld Servlet.</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_enhanced_version_of_javax_enterprise_inject_instance">Enhanced version of <code>javax.enterprise.inject.Instance</code></h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>Weld now provides <code>org.jboss.weld.inject.WeldInstance</code> - an enhanced version of <code>javax.enterprise.inject.Instance</code>.
+                  There are three additional methods - <code>getHandler()</code>, <code>handlers()</code> and <code>isResolvable()</code>.
+                  A handler allows to inspect the metadata of the relevant bean and to destroy the underlying contextual instance.
+                  <code>isResolvable()</code> is just a convenient method - a replacement for <code>!isUnsatisfied() &amp;&amp; !isAmbiguous()</code>.
+                  For more details see also <a href="http://docs.jboss.org/weld/reference/2.4.0.CR1/en-US/html/injection.html#_enhanced_version_of_literal_javax_enterprise_inject_instance_literal" target="_blank" rel="noopener">the reference guide</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p><code>WeldInstance</code> is automatically available in Weld SE and Weld Servlet where the Weld API is always on the class path.
+                  It is also available in Weld-powered EE containers. In this case, users would have to compile their application against the Weld API and exclude the Weld API artifact from the deployment (e.g. use provided scope in Maven).</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>This functionality is based on a new proposal for <a href="https://issues.jboss.org/browse/CDI-589" target="_blank" rel="noopener">CDI-589</a>.</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_veto_annotatedtype_not_annotated_with_bean_defining_annotation">Veto <code>AnnotatedType</code> not annotated with bean defining annotation</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>Sometimes it might be useful to process all types during bootstrap, i.e. fire/observe <code>ProcessAnnotatedType</code> event for each Java class discovered, but veto types which are <strong>not annotated with a bean defining annotation</strong>.
+                  The main reason is that not all classes that meet all of the necessary conditions are intended to become beans.
+                  And so vetoing such types helps to conserve memory used by the container.
+                  Note that if you use <code>bean-discovey-mode=annotated</code> (implicit bean archive) then no <code>ProcessAnnotatedType</code> will be fired for any such type because it’s not discovered at all.
+                  And there might be portable extensions which use <code>ProcessAnnotatedType</code> to extract some important information from classes which are not beans.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Therefore, Weld allows to use <code>bean-discovey-mode=all</code> (explicit bean archive) and veto types without a bean defining annotation whose <code>AnnotatedType#getJavaClass().getName()</code> matches a <a href="http://docs.jboss.org/weld/reference/2.4.0.CR1/en-US/html/configure.html#veto-types-without-bean-defining-annotation">regular expression</a>.
+                  In other words, a type is vetoed if its name matches a regular expression and at the same time is not annotated with a bean defining annotation.
+                  This functionality is implemented as a built-in portable extension processing all types from all bean archives (it was already doable using an extension but we believe it&#8217;s more convenient to have this functionality out of the box).</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>This is a workaround for problems of <code>bean-discovey-mode=annotated</code> mentioned in <a href="https://issues.jboss.org/browse/CDI-420" target="_blank" rel="noopener">CDI-420</a>.</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_activaterequestscope_moved_to_weld_api"><code>@ActivateRequestScope</code> moved to Weld API</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>This interceptor binding can be used to activate the request scope within a business method invocation.
+                  It was previously part of the Weld SE but we believe it might be useful in any environment.
+                  See also <a href="https://issues.jboss.org/browse/WELD-2150" target="_blank" rel="noopener">WELD-2150</a>.</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_improved_rolling_upgrades_support">Improved rolling upgrades support</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p><a href="https://issues.jboss.org/secure/ViewProfile.jspa?name=lprimak">Lenny Primak</a> (a Weld community member - thanks for the report again!) struggled with rolling upgrades on certain application servers (Payara, GlassFish).
+                  Therefore, a new configuration property was introduced.
+                  This property allows to specify a delimiter which is used to abbreviate a bean archive identifier (which is usually derived from the archive name) before used as a part of an identifier of an internal component (such as bean).
+                  See also <a href="http://docs.jboss.org/weld/reference/2.4.0.CR1/en-US/html/configure.html#_rolling_upgrades_id_delimiter" target="_blank" rel="noopener">the reference guide</a> and <a href="https://issues.jboss.org/browse/WELD-2064" target="_blank" rel="noopener">WELD-2064</a>.</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_events_reflect_the_output_of_cdi_494">Events - reflect the output of CDI-494</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>This change reflects the clarification around <code>Event</code> operations - <em>"A wildcard type is not considered an unresolvable type variable"</em>.
+                  See also <a href="https://issues.jboss.org/browse/WELD-2137" target="_blank" rel="noopener">WELD-2137</a> and <a href="https://issues.jboss.org/browse/CDI-494" target="_blank" rel="noopener">CDI-494</a>.
+                  Simply said, the snippet below and similar ones should now work:</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">@Inject Event&lt;List&lt;?&gt;&gt; event;&#x000A;    &#x000A;    public void fireLists() {&#x000A;      List&lt;String&gt; stringList = new ArrayList&lt;&gt;();&#x000A;      event.fire(stringList);&#x000A;      List&lt;Integer&gt; intList = new ArrayList&lt;&gt;();&#x000A;      event.fire(intList);&#x000A;    }&#x000A;    &#x000A;    void observeAllLists(@Observes List&lt;?&gt; anyList) {&#x000A;      // Will be notified&#x000A;    }</code></pre>
+                  </div>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_probe_allow_to_filter_unused_beans">Probe - allow to filter unused beans</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>The Probe development tool now identifies beans which are most likely unused (a bean is considered unused if it has no direct dependents, does not declare any observer or producer methods, is not annotated with <code>@Named</code> and is not a built-in bean, extension, interceptor or decorator).
+                  This might be useful to identify types suitable for vetoing as mentioned in <a href="#_veto_code_annotatedtype_code_not_annotated_with_bean_defining_annotation">[_veto_code_annotatedtype_code_not_annotated_with_bean_defining_annotation]</a>.</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_cleanup">Cleanup</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>Weld has underwent an internal cleanup. A lot of deprecated and unused classes were removed.</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_initial_java_9_support">Initial Java 9 support</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>It&#8217;s now possible to build Weld with Java 9.
+                  Note that this does not mean that Weld is modularized in a <a href="http://openjdk.java.net/projects/jigsaw/" target="_blank" rel="noopener">Jigsaw way</a>.
+                  It&#8217;s just the first step on a long road ;-).</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_bugs">Bugs</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>Last but not least - a few bugs were killed.
+                  Weld SE - provided <code>ClassLoader</code> is also used to load extensions (<a href="https://issues.jboss.org/browse/WELD-2209" target="_blank" rel="noopener">WELD-2209</a>).
+                  <code>AnnotatedTypeValidator</code> does consider extended interfaces (<a href="https://issues.jboss.org/browse/WELD-2221" target="_blank" rel="noopener">WELD-2221</a>).
+                  Invocation of a JDK8 default method should be intercepted (this only works if using <code>jboss-classfilewriter</code> 1.2.0.Beta1+, <a href="https://issues.jboss.org/browse/WELD-2093" target="_blank" rel="noopener">WELD-2093</a>).</p>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_wildfly_patch">WildFly Patch</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>As usual, a <a href="http://download.jboss.org/weld/2.4.0.CR1/wildfly-10.0.0.Final-weld-2.4.0.CR1-patch.zip" target="_blank" rel="noopener">patch for WildFly</a> is available. This time the target platform is <strong>WildFly 10.0.0.Final</strong>.  If you’re not familiar with patching WildFly, check <a href="http://blog.eisele.net/2015/02/playing-with-weld-probe-see-all-of-your.html" target="_blank" rel="noopener">Markus&#8217;s tutorial</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="http://docs.jboss.org/cdi/api/1.2/" target="_blank" rel="noopener">CDI 1.2 API</a> &#93;
+                  &#91; <a href="/download/">Download</a> &#93;
+                  &#91; <a href="http://docs.jboss.org/weld/reference/2.4.0.CR1/en-US/html/" target="_blank" rel="noopener">Documentation</a> &#93;
+                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12330683" target="_blank" rel="noopener">Release notes</a> &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2016/07/01/weld-235Final/">Weld 2.3.5.Final</a>
@@ -890,189 +1068,6 @@ <h2 id="_weld_2_2_16_sp1">Weld 2.2.16.SP1</h2>
                 </div>
                 <hr>
               </div>
-              <div class="post">
-                <h2>
-                  <a href="/news/2015/08/05/weld-300Alpha12/">Weld 3.0.0.Alpha12 - CDI 2.0 EDR1 Reference Implementation!</a>
-                </h2>
-                <div class="news-date news-boxed">
-                  2015-8-5
-                  &nbsp;
-                  <span class="tags">
-                    <i class="fa fa-tags"></i>
-                    <a href="/news/tags/release">release</a>
-                    ,
-                    <a href="/news/tags/cdi2">cdi2</a>
-                  </span>
-                  &nbsp;
-                  <i class="fa fa-pencil"></i>
-                  Martin Kouba
-                </div>
-                <p></p>
-                <div class="content">
-                  <div class="paragraph">
-                  <p>Weld 3.0.0.Alpha12 has been released. Compared to previous alpha releases this is an important milestone - it&#8217;s a reference implementation of <a href="http://docs.jboss.org/cdi/spec/2.0.EDR1/cdi-spec.html">CDI 2.0 Early Draft</a> (EDR1). You can read more about CDI 2.0 EDR1 on the official blog: <a href="http://www.cdi-spec.org/news/2015/07/03/CDI-2_0-EDR1-released/">CDI 2.0 Early Draft Review 1 released</a>.</p>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_bootstrapping_a_cdi_container_in_java_se">Bootstrapping a CDI container in Java SE</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>Starting a CDI container is now really that easy:</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">public static void main(String... args) {&#x000A;        try(CDI&lt;Object&gt; cdi = CDI.getCDIProvider().initialize()) {&#x000A;            ComputingService service = cdi.select(ComputingService.class).get();&#x000A;            service.compute();&#x000A;        }&#x000A;    }</code></pre>
-                  </div>
-                  </div>
-                  <div class="paragraph">
-                  <p><code>javax.enterprise.inject.spi.CDI</code> now implements <code>AutoCloseable</code> and can therefore be used in a <code>try-with-resources</code> block.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Note that the specification of the bean discovery process in Java SE is not finished yet. Therefore, bean archives which don&#8217;t contain a beans.xml file are not supported. The main reason is that we don&#8217;t want to implement a feature which is being discussed and will likely undergo some important changes. Nevertheless, the feature will be implemented in one of the next alpha versions.</p>
-                  </div>
-                  <div class="sect2">
-                  <h3 id="_weld_se_bootstrap_api">Weld SE bootstrap API</h3>
-                  <div class="paragraph">
-                  <p>How does it compare to Weld SE bootstrap API? Weld has provided support for the Java SE environment for a long time. Recently, the <code>org.jboss.weld.environment.se.Weld</code> class was turned into a powerful builder which allows to configure the Weld container before it is initialized.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Typical usage of the Weld SE API looks like this:</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">try (WeldContainer container = new Weld().initialize()) {&#x000A;        ComputingService service = container.select(ComputingService.class).get();&#x000A;        service.compute();&#x000A;    }</code></pre>
-                  </div>
-                  </div>
-                  <div class="paragraph">
-                  <p>This looks very similar to CDI SE, right? However, there are several advanced feratures available:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>automatic scanning can be disabled, classes or packages can be selected explicitly</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p><code>WeldContainer container = new Weld().disableDiscovery().beanClasses(Foo.class, Bar.class).alternatives(Bar.class).interceptors(FooInterceptor.class).initialize();</code></p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>WeldContainer allows to fire events easily</p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p><code>container.event().select(Bar.class).fire(new Bar());</code></p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>Weld-specific <a href="http://docs.jboss.org/weld/reference/latest/en-US/html/configure.html#_weld_configuration">configuration options</a> can be specified using the builder</p>
-                  </li>
-                  <li>
-                  <p>it is possible to start multiple independent Weld instances (specification does not require this)</p>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>See also <a href="http://weld.cdi-spec.org/news/2015/04/21/weld-300Alpha8/">Weld 3.0.0.Alpha8 announcement</a> for more information.</p>
-                  </div>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_asynchronous_events">Asynchronous Events</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>An experimental support of asynchronous events is implemented in Weld since 3.0.0.Alpha3. However, in this release the API was aligned with CDI 2.0 EDR1:</p>
-                  </div>
-                  <div class="listingblock">
-                  <div class="content">
-                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">class OrderProcessor {&#x000A;    &#x000A;        @Inject Event&lt;Order&gt; orderEvent;&#x000A;    &#x000A;        public void process(Order order) {&#x000A;            orderEvent.fireAsync(order).thenAccept((o)-&gt;System.out.println("Asynchronous processing finished: " + o.getId()));&#x000A;        }&#x000A;    &#x000A;        public void processingOrder(@Observes Order event) {&#x000A;            // This observer is notified synchronously, before the fireAsync() method returns&#x000A;        }&#x000A;    &#x000A;        public void asyncProcessingOrder(@ObservesAsync Order event) {&#x000A;            // This observer is notified asynchronously, in a different thread&#x000A;        }&#x000A;    }</code></pre>
-                  </div>
-                  </div>
-                  <div class="paragraph">
-                  <p>There are few important things to notice:</p>
-                  </div>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>the event was triggered with <code>fireAsync()</code></p>
-                  </li>
-                  <li>
-                  <p>the asynchronous observer is defined by <code>@ObservesAsync</code></p>
-                  <div class="ulist">
-                  <ul>
-                  <li>
-                  <p>this is required because of backward compatibilty with previous versions of CDI, see also <a href="http://www.cdi-spec.org/news/2015/07/03/CDI-2_0-EDR1-released/#_why_this_double_activation_is_needed">Why this double activation is needed?</a></p>
-                  </li>
-                  </ul>
-                  </div>
-                  </li>
-                  <li>
-                  <p>synchronous observers defined by <code>@Observes</code> are also notified!</p>
-                  </li>
-                  </ul>
-                  </div>
-                  <div class="paragraph">
-                  <p>To sum it up:</p>
-                  </div>
-                  <table class="tableblock frame-all grid-all stretch">
-                  <colgroup>
-                  <col style="width: 33.3333%;">
-                  <col style="width: 33.3333%;">
-                  <col style="width: 33.3334%;">
-                  </colgroup>
-                  <thead>
-                  <tr>
-                  <th class="tableblock halign-left valign-top">Event method</th>
-                  <th class="tableblock halign-left valign-top"><code>@Observes</code> notified</th>
-                  <th class="tableblock halign-left valign-top"><code>@ObservesAsync</code> notified</th>
-                  </tr>
-                  </thead>
-                  <tbody>
-                  <tr>
-                  <td class="tableblock halign-left valign-top"><p class="tableblock"><code>fire()</code></p></td>
-                  <td class="tableblock halign-left valign-top"><p class="tableblock">yes, in the same thread</p></td>
-                  <td class="tableblock halign-left valign-top"><p class="tableblock">no</p></td>
-                  </tr>
-                  <tr>
-                  <td class="tableblock halign-left valign-top"><p class="tableblock"><code>fireAsync()</code></p></td>
-                  <td class="tableblock halign-left valign-top"><p class="tableblock">yes, in the same thread</p></td>
-                  <td class="tableblock halign-left valign-top"><p class="tableblock">yes, in a different thread</p></td>
-                  </tr>
-                  </tbody>
-                  </table>
-                  <div class="sect2">
-                  <h3 id="_observers_spi_changes">Observers SPI Changes</h3>
-                  <div class="paragraph">
-                  <p><code>javax.enterprise.inject.spi.ObserverMethod</code> now extends <code>javax.enterprise.inject.spi.Prioritized</code> and overrides the <code>ObserverMethod.getPriority()</code> method which is used to determine the notification order in which the event observer methods are invoked. <code>Prioritized</code> interface is currently only used for observers. However, the Weld team is working on a prototype where <code>Prioritized</code> can be used to globally select/enable custom alternative beans, interceptors and decorators, see also <a href="https://issues.jboss.org/browse/WELD-2000">WELD-2000</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>Furthermore, <code>ObserverMethod.isAsync()</code> method was added to determine whether an observer method is asynchronous or not.</p>
-                  </div>
-                  </div>
-                  </div>
-                  </div>
-                  <div class="sect1">
-                  <h2 id="_wildfly_patch">WildFly Patch</h2>
-                  <div class="sectionbody">
-                  <div class="paragraph">
-                  <p>As usual, a <a href="http://download.jboss.org/weld/3.0.0.Alpha12/wildfly-10.0.0.Alpha6-weld-3.0.0.Alpha12-patch.zip">patch for WildFly</a> is available. This patch not only upgrades Weld within an existing WildFly instance but also upgrades CDI API to 2.0 EDR1. This time the target platform is <strong>WildFly 10.0.0.Alpha6</strong>.  If you’re not familiar with patching WildFly, check <a href="http://blog.eisele.net/2015/02/playing-with-weld-probe-see-all-of-your.html">Markus&#8217;s tutorial</a>.</p>
-                  </div>
-                  <div class="paragraph">
-                  <p>&#91; <a href="http://docs.jboss.org/weld/javadoc/3.0/weld-api/org/jboss/weld/experimental/package-frame.html">Experimental API documentation</a> &#93;
-                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12327471">Release notes</a> &#93;
-                  &#91; <a href="http://download.jboss.org/weld/3.0.0.Alpha12/weld-3.0.0.Alpha12.zip">Distribution</a> &#93;
-                  &#91; <a href="http://download.jboss.org/weld/3.0.0.Alpha12/wildfly-10.0.0.Alpha6-weld-3.0.0.Alpha12-patch.zip">Patch for Wildfly 10 Alpha</a>
-                  &#93;</p>
-                  </div>
-                  </div>
-                  </div>
-                </div>
-                <hr>
-              </div>
               <div class="pagination-links"><a href="/news/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 4a79f6f0..f6013968 100644
--- a/news/tags/release/page/7.html
+++ b/news/tags/release/page/7.html
@@ -141,6 +141,189 @@ <h1>
                   <i class="fa fa-rss"></i>
                 </a>
               </h1>
+              <div class="post">
+                <h2>
+                  <a href="/news/2015/08/05/weld-300Alpha12/">Weld 3.0.0.Alpha12 - CDI 2.0 EDR1 Reference Implementation!</a>
+                </h2>
+                <div class="news-date news-boxed">
+                  2015-8-5
+                  &nbsp;
+                  <span class="tags">
+                    <i class="fa fa-tags"></i>
+                    <a href="/news/tags/release">release</a>
+                    ,
+                    <a href="/news/tags/cdi2">cdi2</a>
+                  </span>
+                  &nbsp;
+                  <i class="fa fa-pencil"></i>
+                  Martin Kouba
+                </div>
+                <p></p>
+                <div class="content">
+                  <div class="paragraph">
+                  <p>Weld 3.0.0.Alpha12 has been released. Compared to previous alpha releases this is an important milestone - it&#8217;s a reference implementation of <a href="http://docs.jboss.org/cdi/spec/2.0.EDR1/cdi-spec.html">CDI 2.0 Early Draft</a> (EDR1). You can read more about CDI 2.0 EDR1 on the official blog: <a href="http://www.cdi-spec.org/news/2015/07/03/CDI-2_0-EDR1-released/">CDI 2.0 Early Draft Review 1 released</a>.</p>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_bootstrapping_a_cdi_container_in_java_se">Bootstrapping a CDI container in Java SE</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>Starting a CDI container is now really that easy:</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">public static void main(String... args) {&#x000A;        try(CDI&lt;Object&gt; cdi = CDI.getCDIProvider().initialize()) {&#x000A;            ComputingService service = cdi.select(ComputingService.class).get();&#x000A;            service.compute();&#x000A;        }&#x000A;    }</code></pre>
+                  </div>
+                  </div>
+                  <div class="paragraph">
+                  <p><code>javax.enterprise.inject.spi.CDI</code> now implements <code>AutoCloseable</code> and can therefore be used in a <code>try-with-resources</code> block.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Note that the specification of the bean discovery process in Java SE is not finished yet. Therefore, bean archives which don&#8217;t contain a beans.xml file are not supported. The main reason is that we don&#8217;t want to implement a feature which is being discussed and will likely undergo some important changes. Nevertheless, the feature will be implemented in one of the next alpha versions.</p>
+                  </div>
+                  <div class="sect2">
+                  <h3 id="_weld_se_bootstrap_api">Weld SE bootstrap API</h3>
+                  <div class="paragraph">
+                  <p>How does it compare to Weld SE bootstrap API? Weld has provided support for the Java SE environment for a long time. Recently, the <code>org.jboss.weld.environment.se.Weld</code> class was turned into a powerful builder which allows to configure the Weld container before it is initialized.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Typical usage of the Weld SE API looks like this:</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">try (WeldContainer container = new Weld().initialize()) {&#x000A;        ComputingService service = container.select(ComputingService.class).get();&#x000A;        service.compute();&#x000A;    }</code></pre>
+                  </div>
+                  </div>
+                  <div class="paragraph">
+                  <p>This looks very similar to CDI SE, right? However, there are several advanced feratures available:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>automatic scanning can be disabled, classes or packages can be selected explicitly</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p><code>WeldContainer container = new Weld().disableDiscovery().beanClasses(Foo.class, Bar.class).alternatives(Bar.class).interceptors(FooInterceptor.class).initialize();</code></p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>WeldContainer allows to fire events easily</p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p><code>container.event().select(Bar.class).fire(new Bar());</code></p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>Weld-specific <a href="http://docs.jboss.org/weld/reference/latest/en-US/html/configure.html#_weld_configuration">configuration options</a> can be specified using the builder</p>
+                  </li>
+                  <li>
+                  <p>it is possible to start multiple independent Weld instances (specification does not require this)</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>See also <a href="http://weld.cdi-spec.org/news/2015/04/21/weld-300Alpha8/">Weld 3.0.0.Alpha8 announcement</a> for more information.</p>
+                  </div>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_asynchronous_events">Asynchronous Events</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>An experimental support of asynchronous events is implemented in Weld since 3.0.0.Alpha3. However, in this release the API was aligned with CDI 2.0 EDR1:</p>
+                  </div>
+                  <div class="listingblock">
+                  <div class="content">
+                  <pre class="highlightjs highlight"><code class="language-java hljs" data-lang="java">class OrderProcessor {&#x000A;    &#x000A;        @Inject Event&lt;Order&gt; orderEvent;&#x000A;    &#x000A;        public void process(Order order) {&#x000A;            orderEvent.fireAsync(order).thenAccept((o)-&gt;System.out.println("Asynchronous processing finished: " + o.getId()));&#x000A;        }&#x000A;    &#x000A;        public void processingOrder(@Observes Order event) {&#x000A;            // This observer is notified synchronously, before the fireAsync() method returns&#x000A;        }&#x000A;    &#x000A;        public void asyncProcessingOrder(@ObservesAsync Order event) {&#x000A;            // This observer is notified asynchronously, in a different thread&#x000A;        }&#x000A;    }</code></pre>
+                  </div>
+                  </div>
+                  <div class="paragraph">
+                  <p>There are few important things to notice:</p>
+                  </div>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>the event was triggered with <code>fireAsync()</code></p>
+                  </li>
+                  <li>
+                  <p>the asynchronous observer is defined by <code>@ObservesAsync</code></p>
+                  <div class="ulist">
+                  <ul>
+                  <li>
+                  <p>this is required because of backward compatibilty with previous versions of CDI, see also <a href="http://www.cdi-spec.org/news/2015/07/03/CDI-2_0-EDR1-released/#_why_this_double_activation_is_needed">Why this double activation is needed?</a></p>
+                  </li>
+                  </ul>
+                  </div>
+                  </li>
+                  <li>
+                  <p>synchronous observers defined by <code>@Observes</code> are also notified!</p>
+                  </li>
+                  </ul>
+                  </div>
+                  <div class="paragraph">
+                  <p>To sum it up:</p>
+                  </div>
+                  <table class="tableblock frame-all grid-all stretch">
+                  <colgroup>
+                  <col style="width: 33.3333%;">
+                  <col style="width: 33.3333%;">
+                  <col style="width: 33.3334%;">
+                  </colgroup>
+                  <thead>
+                  <tr>
+                  <th class="tableblock halign-left valign-top">Event method</th>
+                  <th class="tableblock halign-left valign-top"><code>@Observes</code> notified</th>
+                  <th class="tableblock halign-left valign-top"><code>@ObservesAsync</code> notified</th>
+                  </tr>
+                  </thead>
+                  <tbody>
+                  <tr>
+                  <td class="tableblock halign-left valign-top"><p class="tableblock"><code>fire()</code></p></td>
+                  <td class="tableblock halign-left valign-top"><p class="tableblock">yes, in the same thread</p></td>
+                  <td class="tableblock halign-left valign-top"><p class="tableblock">no</p></td>
+                  </tr>
+                  <tr>
+                  <td class="tableblock halign-left valign-top"><p class="tableblock"><code>fireAsync()</code></p></td>
+                  <td class="tableblock halign-left valign-top"><p class="tableblock">yes, in the same thread</p></td>
+                  <td class="tableblock halign-left valign-top"><p class="tableblock">yes, in a different thread</p></td>
+                  </tr>
+                  </tbody>
+                  </table>
+                  <div class="sect2">
+                  <h3 id="_observers_spi_changes">Observers SPI Changes</h3>
+                  <div class="paragraph">
+                  <p><code>javax.enterprise.inject.spi.ObserverMethod</code> now extends <code>javax.enterprise.inject.spi.Prioritized</code> and overrides the <code>ObserverMethod.getPriority()</code> method which is used to determine the notification order in which the event observer methods are invoked. <code>Prioritized</code> interface is currently only used for observers. However, the Weld team is working on a prototype where <code>Prioritized</code> can be used to globally select/enable custom alternative beans, interceptors and decorators, see also <a href="https://issues.jboss.org/browse/WELD-2000">WELD-2000</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>Furthermore, <code>ObserverMethod.isAsync()</code> method was added to determine whether an observer method is asynchronous or not.</p>
+                  </div>
+                  </div>
+                  </div>
+                  </div>
+                  <div class="sect1">
+                  <h2 id="_wildfly_patch">WildFly Patch</h2>
+                  <div class="sectionbody">
+                  <div class="paragraph">
+                  <p>As usual, a <a href="http://download.jboss.org/weld/3.0.0.Alpha12/wildfly-10.0.0.Alpha6-weld-3.0.0.Alpha12-patch.zip">patch for WildFly</a> is available. This patch not only upgrades Weld within an existing WildFly instance but also upgrades CDI API to 2.0 EDR1. This time the target platform is <strong>WildFly 10.0.0.Alpha6</strong>.  If you’re not familiar with patching WildFly, check <a href="http://blog.eisele.net/2015/02/playing-with-weld-probe-see-all-of-your.html">Markus&#8217;s tutorial</a>.</p>
+                  </div>
+                  <div class="paragraph">
+                  <p>&#91; <a href="http://docs.jboss.org/weld/javadoc/3.0/weld-api/org/jboss/weld/experimental/package-frame.html">Experimental API documentation</a> &#93;
+                  &#91; <a href="https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310891&amp;version=12327471">Release notes</a> &#93;
+                  &#91; <a href="http://download.jboss.org/weld/3.0.0.Alpha12/weld-3.0.0.Alpha12.zip">Distribution</a> &#93;
+                  &#91; <a href="http://download.jboss.org/weld/3.0.0.Alpha12/wildfly-10.0.0.Alpha6-weld-3.0.0.Alpha12-patch.zip">Patch for Wildfly 10 Alpha</a>
+                  &#93;</p>
+                  </div>
+                  </div>
+                  </div>
+                </div>
+                <hr>
+              </div>
               <div class="post">
                 <h2>
                   <a href="/news/2015/04/21/weld-300Alpha8/">Weld 3.0.0.Alpha8</a>
diff --git a/sitemap.xml b/sitemap.xml
index 1354663a..47e5809c 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-08-27</lastmod>
+    <lastmod>2024-11-13</lastmod>
     <priority>0.5</priority>
     <changefreq>weekly</changefreq>
   </url>
   <url>
     <loc>https://weld.cdi-spec.org/community/</loc>
-    <lastmod>2024-08-27</lastmod>
+    <lastmod>2024-11-13</lastmod>
     <priority>0.5</priority>
     <changefreq>weekly</changefreq>
   </url>
   <url>
     <loc>https://weld.cdi-spec.org/dist/</loc>
-    <lastmod>2024-08-27</lastmod>
+    <lastmod>2024-11-13</lastmod>
     <priority>1</priority>
     <changefreq>daily</changefreq>
   </url>
   <url>
     <loc>https://weld.cdi-spec.org/documentation/</loc>
-    <lastmod>2024-08-27</lastmod>
+    <lastmod>2024-11-13</lastmod>
     <priority>0.5</priority>
     <changefreq>weekly</changefreq>
   </url>
   <url>
     <loc>https://weld.cdi-spec.org/download/</loc>
-    <lastmod>2024-08-27</lastmod>
+    <lastmod>2024-11-13</lastmod>
     <priority>0.5</priority>
     <changefreq>weekly</changefreq>
   </url>
   <url>
     <loc>https://weld.cdi-spec.org/</loc>
-    <lastmod>2024-08-27</lastmod>
+    <lastmod>2024-11-13</lastmod>
     <priority>0.5</priority>
     <changefreq>weekly</changefreq>
   </url>
@@ -588,9 +588,15 @@
     <priority>1</priority>
     <changefreq>weekly</changefreq>
   </url>
+  <url>
+    <loc>https://weld.cdi-spec.org/news/2024/11/13/weld-600CR1/</loc>
+    <lastmod>2024-11-13</lastmod>
+    <priority>1</priority>
+    <changefreq>weekly</changefreq>
+  </url>
   <url>
     <loc>https://weld.cdi-spec.org/news/</loc>
-    <lastmod>2024-08-27</lastmod>
+    <lastmod>2024-11-13</lastmod>
     <priority>1</priority>
     <changefreq>daily</changefreq>
   </url>