You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This bug causes a huge amount of pain for the engineers I work with at Zalando. We make heavy use of integration tests in our multi-module Quarkus applications, and the DI fails because of this often with the very cryptic error message:
io.smallrye.config.SmallRyeConfigFactory: io.quarkus.runtime.configuration.QuarkusConfigFactory not a subtype
This results in engineers changing things from ApplicationScoped to Singleton, moving factories around, and engaging in all sorts of other toil to fix the issue. When the issue presents, it is incredibly time-consuming to diagnose and fix, and the workarounds leaves the code base in a worse state than before.
Describe the bug
When a new source set is created, for example, for integration tests, quarkus is not building the class path correctly.
Quarkus only builds the class path for implementation and testImplementation configurations.
Originally posted here https://stackoverflow.com/questions/70700501/serviceconfigurationerror-when-running-a-quarkustest-using-gradle-kts
The text was updated successfully, but these errors were encountered: