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

Exclude okhttp dependency from grpc-okhttp tests #3678

Closed

Conversation

anuraaga
Copy link
Contributor

grpc-okhttp actually bundles in okhttp - they also have a few API knobs that use real okhttp classes, but we don't actually use these knobs. The tests passing with this change seem to confirm that we don't need to actually bring in the ancient okhttp version into downstream builds.

For reference:
grpc/grpc-java#6119

@anuraaga anuraaga requested a review from a user September 29, 2021 05:19
@anuraaga anuraaga changed the title Exclude okhttp dependency from grpc-okhttp Exclude okhttp dependency from grpc-okhttp tests Sep 29, 2021
@jack-berg
Copy link
Member

Are there any downstream builds which have a dependency on a test source set?

Also, is it worth excluding this dependency from the compile only dependencies? I.e. compileOnly("io.grpc:grpc-okhttp")

@anuraaga
Copy link
Contributor Author

@jack-berg Yeah I was mostly trying to confirm it could be safe downstream to do the same as what we do here. But I realized that because we have setChannel, it's relatively easy for a user to configure the client in a way that would still break. Ideally we didn't have setChannel / gRPC exposed into the public API but perhaps in 2.x.

@anuraaga anuraaga closed this Sep 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants