deploy: 46bf465

Author: maxandersen

blog/test-classloading-rewrite/index.html

@@ -250,7 +250,7 @@ <h3 id="known-regressions"><a class="anchor" href="#known-regressions"></a>Known
 <p><strong>Config access from JUnit conditions</strong>. Using a <code>ConfigProvider</code> from a custom JUnit condition will <a href="https://github.com/quarkusio/quarkus/issues/47081">trigger a <code>ServiceConfigurationError</code></a>. The workaround is to set the thread context classloader to <code>this.getClass().getClassLoader()</code> before reading config, and then set it back afterwards. This is fixed in 3.23.</p>
 </li>
 <li>
-<p><strong>Nested test issues</strong>. If nested <code>@QuarkusTest</code> tests are mixed in the same project with plain tests, the plain tests <a href="https://github.com/quarkusio/quarkus/issues/47657">will not be able to access Quarkus config</a>, because the thread context classloader does not get correctly reset. As a workaround, you can manually set the thread context classloader to the system classloader in the plain tests. The nested tests also <a href="https://github.com/quarkusio/quarkus/issues/47671">have problems in dev mode</a>. These issues are fixed in 3.23.</p>
+<p><strong>Nested test issues</strong>. If nested <code>@QuarkusTest</code> tests are mixed in the same project with plain tests, the plain tests <a href="https://github.com/quarkusio/quarkus/issues/47657">will not be able to access Quarkus config</a>, because the thread context classloader does not get correctly reset. As a workaround, you can manually set the thread context classloader to the system classloader in the plain tests. The nested tests also <a href="https://github.com/quarkusio/quarkus/issues/47671">have problems in dev mode</a>. Most of these issues are fixed in 3.23.</p>
 </li>
 <li>
 <p><strong>junit-platform.properties</strong> Including a <code>junit-platform.properties</code> in a Gradle project <a href="https://github.com/quarkusio/quarkus/issues/47646">causes problems</a> for `@QuarkusTest`s.</p>
@@ -259,7 +259,7 @@ <h3 id="known-regressions"><a class="anchor" href="#known-regressions"></a>Known
 <p><strong>Gradle source sets</strong>. In some cases classes in one gradle source set <a href="https://github.com/quarkusio/quarkus/issues/47760">cannot access package-private fields and classes in a different source set</a>. This causes an <code>IllegalAccessError</code>. The workaround is to switch from package-private to public.</p>
 </li>
 <li>
-<p><strong>Eclipse support</strong>. Running <code>QuarkusTest</code> tests from the Eclipse IDE is <a href="https://github.com/quarkusio/quarkus/issues/47656">more challenging</a>. Right-clicking and running individual test methods works, and running a whole package also works. But running at the class level gives an error.</p>
+<p><strong>IDE support</strong>. Running <code>QuarkusTest</code> tests from the Eclipse IDE is <a href="https://github.com/quarkusio/quarkus/issues/47656">more challenging</a>. Right-clicking and running individual test methods works, and running a whole package also works. But running at the class level gives an error. Similar, in Visual Studio Code, running all tests in a class or package <a href="https://github.com/quarkusio/quarkus/issues/48014">will fail</a>, but running individual test methods will work.</p>
 </li>
 <li>
 <p><strong>Increased memory footprint running tests.</strong> For suites using multiple profiles and resources, more heap or metaspace may be needed.</p>

feed.xml

@@ -5,7 +5,7 @@
         <title>Quarkus</title>
         <link>https://quarkus.io</link>
         <description>Quarkus: Supersonic Subatomic Java</description>
-        <lastBuildDate>Thu, 22 May 2025 03:23:12 +0000</lastBuildDate>
+        <lastBuildDate>Fri, 23 May 2025 00:05:01 +0000</lastBuildDate>
 
 
         <item>
@@ -1346,7 +1346,7 @@ In practice, there have been a few hiccups and we&amp;#8217;ve also discovered s
 &lt;p&gt;&lt;strong&gt;Config access from JUnit conditions&lt;/strong&gt;. Using a &lt;code&gt;ConfigProvider&lt;/code&gt; from a custom JUnit condition will &lt;a href=&quot;https://github.com/quarkusio/quarkus/issues/47081&quot;&gt;trigger a &lt;code&gt;ServiceConfigurationError&lt;/code&gt;&lt;/a&gt;. The workaround is to set the thread context classloader to &lt;code&gt;this.getClass().getClassLoader()&lt;/code&gt; before reading config, and then set it back afterwards. This is fixed in 3.23.&lt;/p&gt;
 &lt;/li&gt;
 &lt;li&gt;
-&lt;p&gt;&lt;strong&gt;Nested test issues&lt;/strong&gt;. If nested &lt;code&gt;@QuarkusTest&lt;/code&gt; tests are mixed in the same project with plain tests, the plain tests &lt;a href=&quot;https://github.com/quarkusio/quarkus/issues/47657&quot;&gt;will not be able to access Quarkus config&lt;/a&gt;, because the thread context classloader does not get correctly reset. As a workaround, you can manually set the thread context classloader to the system classloader in the plain tests. The nested tests also &lt;a href=&quot;https://github.com/quarkusio/quarkus/issues/47671&quot;&gt;have problems in dev mode&lt;/a&gt;. These issues are fixed in 3.23.&lt;/p&gt;
+&lt;p&gt;&lt;strong&gt;Nested test issues&lt;/strong&gt;. If nested &lt;code&gt;@QuarkusTest&lt;/code&gt; tests are mixed in the same project with plain tests, the plain tests &lt;a href=&quot;https://github.com/quarkusio/quarkus/issues/47657&quot;&gt;will not be able to access Quarkus config&lt;/a&gt;, because the thread context classloader does not get correctly reset. As a workaround, you can manually set the thread context classloader to the system classloader in the plain tests. The nested tests also &lt;a href=&quot;https://github.com/quarkusio/quarkus/issues/47671&quot;&gt;have problems in dev mode&lt;/a&gt;. Most of these issues are fixed in 3.23.&lt;/p&gt;
 &lt;/li&gt;
 &lt;li&gt;
 &lt;p&gt;&lt;strong&gt;junit-platform.properties&lt;/strong&gt; Including a &lt;code&gt;junit-platform.properties&lt;/code&gt; in a Gradle project &lt;a href=&quot;https://github.com/quarkusio/quarkus/issues/47646&quot;&gt;causes problems&lt;/a&gt; for `@QuarkusTest`s.&lt;/p&gt;
@@ -1355,7 +1355,7 @@ In practice, there have been a few hiccups and we&amp;#8217;ve also discovered s
 &lt;p&gt;&lt;strong&gt;Gradle source sets&lt;/strong&gt;. In some cases classes in one gradle source set &lt;a href=&quot;https://github.com/quarkusio/quarkus/issues/47760&quot;&gt;cannot access package-private fields and classes in a different source set&lt;/a&gt;. This causes an &lt;code&gt;IllegalAccessError&lt;/code&gt;. The workaround is to switch from package-private to public.&lt;/p&gt;
 &lt;/li&gt;
 &lt;li&gt;
-&lt;p&gt;&lt;strong&gt;Eclipse support&lt;/strong&gt;. Running &lt;code&gt;QuarkusTest&lt;/code&gt; tests from the Eclipse IDE is &lt;a href=&quot;https://github.com/quarkusio/quarkus/issues/47656&quot;&gt;more challenging&lt;/a&gt;. Right-clicking and running individual test methods works, and running a whole package also works. But running at the class level gives an error.&lt;/p&gt;
+&lt;p&gt;&lt;strong&gt;IDE support&lt;/strong&gt;. Running &lt;code&gt;QuarkusTest&lt;/code&gt; tests from the Eclipse IDE is &lt;a href=&quot;https://github.com/quarkusio/quarkus/issues/47656&quot;&gt;more challenging&lt;/a&gt;. Right-clicking and running individual test methods works, and running a whole package also works. But running at the class level gives an error. Similar, in Visual Studio Code, running all tests in a class or package &lt;a href=&quot;https://github.com/quarkusio/quarkus/issues/48014&quot;&gt;will fail&lt;/a&gt;, but running individual test methods will work.&lt;/p&gt;
 &lt;/li&gt;
 &lt;li&gt;
 &lt;p&gt;&lt;strong&gt;Increased memory footprint running tests.&lt;/strong&gt; For suites using multiple profiles and resources, more heap or metaspace may be needed.&lt;/p&gt;

working-groups/index.html

@@ -200,31 +200,31 @@ <h2>Active working groups</h2>
 
     <div class="card">
         <div class="card-header">
-            <p class="card-title">Gizmo 2</p>
+            <p class="card-title">Test classloading</p>
         </div>
         <div class="card-body">
             <p class="card-text"><span class="key">Status:</span>&nbsp;<span
                     class="status on-track">on track</span></p>
-            <p class="card-text"><span class="key">Description:</span>&nbsp;<span class="short-description">Gizmo 2 related tasks
+            <p class="card-text"><span class="key">Description:</span>&nbsp;<span class="short-description">The goal of this working group is to rewrite Quarkus's test classloading, so that tests are run in the same classloader as the application under tests, and Quarkus extensions can do "Quarkus-y" manipulations of test classes.
 </span>
             </p>
-            <p class="card-text"><span class="key">Last Activity:</span>&nbsp;<span class="last-activity">May 21, 2025 </span>
+            <p class="card-text"><span class="key">Last Activity:</span>&nbsp;<span class="last-activity">May 22, 2025 </span>
             </p>
 
-            <p class="card-text"><span class="key">Point of Contact:</span>&nbsp;<span class="point-of-contact">@mkouba (@<strong>Martin Kouba</strong>  on Zulip)</span>
+            <p class="card-text"><span class="key">Point of Contact:</span>&nbsp;<span class="point-of-contact">@holly-cummins (@<strong>Holly Cummins</strong>  on Zulip)</span>
             </p>
 
         </div>
         <div class="card-footer">
             <div class="icons">
 
-                <a href="https://github.com/quarkusio/quarkus/discussions/46627" title="See the working group proposal"><i
+                <a href="https://github.com/quarkusio/quarkus/discussions/41867" title="See the working group proposal"><i
                         class="icon fa-regular fa-file-lines"></i></a>&nbsp;
 
-                <a href="https://github.com/orgs/quarkusio/projects/43" title="View the working group board"><i
+                <a href="https://github.com/orgs/quarkusio/projects/30" title="View the working group board"><i
                         class="icon fa-brands fa-square-github"></i></a>&nbsp;
 
-                <a href="https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/Gizmo.202.2Ex.20WG.20chat" title="Discuss about the working group"><i
+                <a href="https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/WG.20.2330.20Test.20Classloading.20chatter/" title="Discuss about the working group"><i
                         class="icon fa-solid fa-comments"></i></a>&nbsp;
 
             </div>
@@ -243,7 +243,7 @@ <h2>Active working groups</h2>
             <p class="card-text"><span class="key">Description:</span>&nbsp;<span class="short-description">This working group will define and implement a consistent and configurable lifecycle model for Dev Services. It will shift the startup to the correct phase, enable optional reuse across dev and test modes, and clarify teardown and sharing behavior. The goal is to improve the developer experience.
 </span>
             </p>
-            <p class="card-text"><span class="key">Last Activity:</span>&nbsp;<span class="last-activity">May 20, 2025 </span>
+            <p class="card-text"><span class="key">Last Activity:</span>&nbsp;<span class="last-activity">May 22, 2025 </span>
             </p>
 
             <p class="card-text"><span class="key">Point of Contact:</span>&nbsp;<span class="point-of-contact">@holly-cummins (@<strong>Holly Cummins</strong>  on Zulip), @ozangunalp (@<strong>Ozan Günalp</strong> on Zulip )</span>
@@ -270,31 +270,31 @@ <h2>Active working groups</h2>
 
     <div class="card">
         <div class="card-header">
-            <p class="card-title">Test classloading</p>
+            <p class="card-title">Gizmo 2</p>
         </div>
         <div class="card-body">
             <p class="card-text"><span class="key">Status:</span>&nbsp;<span
                     class="status on-track">on track</span></p>
-            <p class="card-text"><span class="key">Description:</span>&nbsp;<span class="short-description">The goal of this working group is to rewrite Quarkus's test classloading, so that tests are run in the same classloader as the application under tests, and Quarkus extensions can do "Quarkus-y" manipulations of test classes.
+            <p class="card-text"><span class="key">Description:</span>&nbsp;<span class="short-description">Gizmo 2 related tasks
 </span>
             </p>
-            <p class="card-text"><span class="key">Last Activity:</span>&nbsp;<span class="last-activity">May 20, 2025 </span>
+            <p class="card-text"><span class="key">Last Activity:</span>&nbsp;<span class="last-activity">May 22, 2025 </span>
             </p>
 
-            <p class="card-text"><span class="key">Point of Contact:</span>&nbsp;<span class="point-of-contact">@holly-cummins (@<strong>Holly Cummins</strong>  on Zulip)</span>
+            <p class="card-text"><span class="key">Point of Contact:</span>&nbsp;<span class="point-of-contact">@mkouba (@<strong>Martin Kouba</strong>  on Zulip)</span>
             </p>
 
         </div>
         <div class="card-footer">
             <div class="icons">
 
-                <a href="https://github.com/quarkusio/quarkus/discussions/41867" title="See the working group proposal"><i
+                <a href="https://github.com/quarkusio/quarkus/discussions/46627" title="See the working group proposal"><i
                         class="icon fa-regular fa-file-lines"></i></a>&nbsp;
 
-                <a href="https://github.com/orgs/quarkusio/projects/30" title="View the working group board"><i
+                <a href="https://github.com/orgs/quarkusio/projects/43" title="View the working group board"><i
                         class="icon fa-brands fa-square-github"></i></a>&nbsp;
 
-                <a href="https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/WG.20.2330.20Test.20Classloading.20chatter/" title="Discuss about the working group"><i
+                <a href="https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/Gizmo.202.2Ex.20WG.20chat" title="Discuss about the working group"><i
                         class="icon fa-solid fa-comments"></i></a>&nbsp;
 
             </div>