Remove unused api
dependencies or move them to lower scope
#3169
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation:
Dependency-analysis plugin detected that some
api
dependencies are unused and can be either removed or downgraded toimplementation
/testImplementation
scopes.Modifications:
api
dependencies.implementation
/testImplementation
scopes.Result:
No more warnings from dependency-analysis plugin.
Risk for users:
Minimal. They can be broken only if they use some dependency at compile time without explicitly declaring it in their build, which is their mistake.
Highlights:
servicetalk-*
dependencies, users likely have them anyway via other modules.opentelemetry-api
fromopentelemetry-asynccontext
module because in Explicitly declare transitive dependencies that we use directly #3164 we addedopentelemetry-context
.proto-google-common-protos
should not be an issue because it's already anapi
dependency forgrpc-api
module.