diff --git a/_posts/2025-04-30-test-classloading-rewrite.adoc b/_posts/2025-04-30-test-classloading-rewrite.adoc
index 5a5ba4f374..8a5156458a 100644
--- a/_posts/2025-04-30-test-classloading-rewrite.adoc
+++ b/_posts/2025-04-30-test-classloading-rewrite.adoc
@@ -46,6 +46,7 @@ In practice, there have been a few hiccups and we've also discovered some edge c
 - *Config access from JUnit conditions*. Using a `ConfigProvider` from a custom JUnit condition will https://github.com/quarkusio/quarkus/issues/47081[trigger a `ServiceConfigurationError`]. The workaround is to set the thread context classloader to `this.getClass().getClassLoader()` before reading config, and then set it back afterwards. This is fixed in 3.23.
 - *Nested test issues*. If nested `@QuarkusTest` tests are mixed in the same project with plain tests, the plain tests https://github.com/quarkusio/quarkus/issues/47657[will not be able to access Quarkus config], 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 https://github.com/quarkusio/quarkus/issues/47671[have problems in dev mode]. These issues are fixed in 3.23.
 - *junit-platform.properties* Including a `junit-platform.properties` in a Gradle project https://github.com/quarkusio/quarkus/issues/47646[causes problems] for `@QuarkusTest`s.
+- *Gradle source sets*. In some cases classes in one gradle source set https://github.com/quarkusio/quarkus/issues/47760[cannot access package-private fields and classes in a different source set]. This causes an `IllegalAccessError`. The workaround is to switch from package-private to public.
 - *Eclipse support*. Running `QuarkusTest` tests from the Eclipse IDE is https://github.com/quarkusio/quarkus/issues/47656[more challenging]. Right-clicking and running individual test methods works, and running a whole package also works. But running at the class level gives an error.
 - *Increased memory footprint running tests.* For suites using multiple profiles and resources, more heap or metaspace may be needed.