Skip to content

Classloading blog updates #2308

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
May 15, 2025
Merged

Classloading blog updates #2308

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d0dfeb1
Add update on newly diagnosed problem
holly-cummins May 15, 2025
78b5f39
Change heading with proper name
holly-cummins May 15, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions _posts/2025-04-30-test-classloading-rewrite.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 sources*. 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.

Expand Down
Loading