deploy: 9edcd82

Author: holly-cummins

blog/test-classloading-rewrite/index.html

@@ -253,7 +253,7 @@ <h3 id="known-regressions"><a class="anchor" href="#known-regressions"></a>Known
 <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>
+<p><strong>junit-platform.properties</strong> Including a <code>junit-platform.properties</code> in a project <a href="https://github.com/quarkusio/quarkus/issues/47646">causes problems</a> for tests using <code>@QuarkusTest</code>.</p>
 </li>
 <li>
 <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>

feed.xml

@@ -5,7 +5,7 @@
         <title>Quarkus</title>
         <link>https://quarkus.io</link>
         <description>Quarkus: Supersonic Subatomic Java</description>
-        <lastBuildDate>Fri, 23 May 2025 03:22:48 +0000</lastBuildDate>
+        <lastBuildDate>Fri, 23 May 2025 08:40:36 +0000</lastBuildDate>
 
 
         <item>
@@ -1349,7 +1349,7 @@ In practice, there have been a few hiccups and we&amp;#8217;ve also discovered s
 &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;
+&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 project &lt;a href=&quot;https://github.com/quarkusio/quarkus/issues/47646&quot;&gt;causes problems&lt;/a&gt; for tests using &lt;code&gt;@QuarkusTest&lt;/code&gt;.&lt;/p&gt;
 &lt;/li&gt;
 &lt;li&gt;
 &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;