-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Broken dependency when using OpenTelemetry + REST Client on main #18125
Comments
@jsmrcka , stupid question but: are you sure the artifact is in the remote repository? CC @aloubyansky |
From which repository is it expected to be downloaded and how is that repository configured in your environment? |
@michalszynkiewicz I am sure the artifact is there. We use an internal repository for daily Quarkus snapshots.
As a workaround, one can add the I believe it has something to do with the
|
Describe the bug
When combining
quarkus-opentelemetry-exporter-otlp
andrest-client
extensions, Maven is unable to resolve theio.quarkus:quarkus-opentelemetry-rest-client-deployment
dependency unless it is locally cached.Expected behavior
Build success
Actual behavior
To Reproduce
Make sure you do not have
io.quarkus:quarkus-opentelemetry-rest-client-deployment:jar:999-SNAPSHOT
in local Maven repo and a remote repo with Quarkus999-SNAPSHOT
is available.See also https://github.com/quarkusio/quarkus-quickstarts/tree/development/opentelemetry-quickstart, which fails in the same manner when using a remote repository.
Environment:
The text was updated successfully, but these errors were encountered: