Skip to content
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.

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

Deployment class path not built for custom source sets in Gradle #22982

Open
AmsterdamFilho opened this issue Jan 18, 2022 · 2 comments
Open
Labels
area/gradle Gradle kind/bug Something isn't working

Comments

@AmsterdamFilho
Copy link

AmsterdamFilho commented Jan 18, 2022

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

@AmsterdamFilho AmsterdamFilho added the kind/bug Something isn't working label Jan 18, 2022
@quarkus-bot quarkus-bot bot added the area/gradle Gradle label Jan 18, 2022
@quarkus-bot
Copy link

quarkus-bot bot commented Jan 18, 2022

/cc @glefloch, @quarkusio/devtools

@cjbooms
Copy link

cjbooms commented May 20, 2023

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/gradle Gradle kind/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants