Quarkus 3.23.2 tests fail with `java.lang.RuntimeException: Failed to locate <class> among the application dependencies`

[LarsSven]

Describe the bug

We're not sure what happened, but as of 3.23.2 (3.23.0 still worked perfectly fine), our tests started failing with the following:

java.lang.RuntimeException: Failed to locate nl/rug/digitallab/themis/assignments/AssignmentsResourceTest.class among the application dependencies
java.lang.RuntimeException: java.lang.RuntimeException: Failed to locate nl/rug/digitallab/themis/assignments/AssignmentsResourceTest.class among the application dependencies
	at io.quarkus.test.junit.QuarkusTestExtension.throwBootFailureException(QuarkusTestExtension.java:667)
	at io.quarkus.test.junit.QuarkusTestExtension.interceptTestClassConstructor(QuarkusTestExtension.java:762)
	at java.base/java.util.Optional.orElseGet(Optional.java:364)
	at java.base/java.util.ArrayList.forEach(ArrayList.java:1596)
	at java.base/java.util.ArrayList.forEach(ArrayList.java:1596)
Caused by: java.lang.RuntimeException: Failed to locate nl/rug/digitallab/themis/assignments/AssignmentsResourceTest.class among the application dependencies
	at io.quarkus.test.common.PathTestHelper.getTestClassesLocation(PathTestHelper.java:188)
	at io.quarkus.test.common.PathTestHelper.getTestClassesLocation(PathTestHelper.java:229)
	at io.quarkus.test.junit.QuarkusTestExtension.doJavaStart(QuarkusTestExtension.java:204)
	at io.quarkus.test.junit.QuarkusTestExtension.ensureStarted(QuarkusTestExtension.java:641)
	at io.quarkus.test.junit.QuarkusTestExtension.beforeAll(QuarkusTestExtension.java:686)
	... 1 more

Expected behavior

Our tests should all pass without any failures

Actual behavior

We get a class location exception as of 3.23.2

How to Reproduce?

1. Clone https://gitlab.com/rug-digitallab/products/themis/themis-core.git
2. Switch branch to renovate/digitallabgradlepluginversion (which includes the Quarkus upgrade)
3. Try to run ./gradlew test
4. Observe the exception

Output of uname -a or ver

Ubuntu 25.04 Linux 6.14.0-15-generic

Output of java -version

openjdk version "21.0.7" 2025-04-15

Quarkus version or git rev

3.23.2

Build tool (ie. output of mvnw --version or gradlew --version)

Gradle 8.14.1

Additional information

No response

[mschorsch]

We see the same issue. All tests in all our Quarkus applications fail since Quarkus 3.23.2. Quarkus 3.23.0 works.

cc @gsmet

[geoand]

cc @aloubyansky

[drmaniac]

Facing the same issue with Quarkus 3.23.2 and 3.23.1.
We use gradle as build system.
If I am running the Unit test from IDE (vscode) the test runs successfully without throwing exceptions.

[aloubyansky]

Some relevant logs running the reproducer

Failed to index org.apiguardian.api.API: Class does not exist in ClassLoader QuarkusClassLoader:Deployment Class Loader: TEST for JUnitQuarkusTest-no-profile (QuarkusTest)@1534bdc6
Failed to index org.osgi.annotation.versioning.Version: Class does not exist in ClassLoader QuarkusClassLoader:Deployment Class Loader: TEST for JUnitQuarkusTest-no-profile (QuarkusTest)@1534bdc6
Failed to index org.jboss.logging.annotations.Message: Class does not exist in ClassLoader QuarkusClassLoader:Deployment Class Loader: TEST for JUnitQuarkusTest-no-profile (QuarkusTest)@1534bdc6
Failed to index org.jboss.logging.annotations.MessageBundle: Class does not exist in ClassLoader QuarkusClassLoader:Deployment Class Loader: TEST for JUnitQuarkusTest-no-profile (QuarkusTest)@1534bdc6
Failed to index org.jboss.logging.annotations.LogMessage: Class does not exist in ClassLoader QuarkusClassLoader:Deployment Class Loader: TEST for JUnitQuarkusTest-no-profile (QuarkusTest)@1534bdc6
Failed to index org.jboss.logging.annotations.MessageLogger: Class does not exist in ClassLoader QuarkusClassLoader:Deployment Class Loader: TEST for JUnitQuarkusTest-no-profile (QuarkusTest)@1534bdc6
Failed to index org.jboss.logging.annotations.Cause: Class does not exist in ClassLoader QuarkusClassLoader:Deployment Class Loader: TEST for JUnitQuarkusTest-no-profile (QuarkusTest)@1534bdc6
Failed to index org.eclipse.microprofile.metrics.annotation.RegistryType: Class does not exist in ClassLoader QuarkusClassLoader:Deployment Class Loader: TEST for JUnitQuarkusTest-no-profile (QuarkusTest)@1534bdc6
Failed to index org.jboss.logging.annotations.Once: Class does not exist in ClassLoader QuarkusClassLoader:Deployment Class Loader: TEST for JUnitQuarkusTest-no-profile (QuarkusTest)@1534bdc6
Failed to index com.fasterxml.jackson.dataformat.csv.CsvMapper: Class does not exist in ClassLoader QuarkusClassLoader:Deployment Class Loader: TEST for JUnitQuarkusTest-no-profile (QuarkusTest)@1534bdc6

> Task :assignments:test

AssignmentsResourceTest > Getting an assignment config for a non-existent profile should return a 404 error() FAILED
    java.lang.RuntimeException at QuarkusTestExtension.java:667
        Caused by: java.lang.RuntimeException at PathTestHelper.java:188

Also @holly-cummins fyi

[aloubyansky]

@LarsSven how could I change the version of Quarkus in your reproducer?
@drmaniac is there a simple reproducer for the issue you are facing?
Thank you both!

[LarsSven]

@aloubyansky admittedly that's a bit complex with our setup.
If you set digitalLabGradlePluginVersion in gradle.properties to 0.3.19 you will be on Quarkus 3.22.3, whereas setting it to 0.3.20 will put you on Quarkus 3.23.2.

We still need to add a way to be able to change the Quarkus version independently of the our internal plugin version 😓

[aloubyansky]

We'd also want to test somehow a custom build of Quarkus to see the effects of changes we apply on your project.

[LarsSven]

The way you can do that is clone https://gitlab.com/rug-digitallab/resources/digital-lab-gradle-plugin, change the quarkusVersion in gradle.properties, publish it to mavenLocal, and then include the locally published plugin version in our project.

Sorry about the complexity of this. Normally I create a reproducer that does not use our plugin to avoid this, but I assumed that was unnecessary here.

[LarsSven]

You can use ./gradlew publishToMavenLocal and the version can be set in the root VERSION file.

[aloubyansky]

Thanks for the extra details @LarsSven

Typically, if you report an issue, we are missing a test for that use-case. A simple reproducer is always appreciated, since it's a good base for adding a test to our testsuite. I often add such reproducers with minimal adjustments to our testsuite.