This repository has been archived by the owner on Sep 26, 2023. It is now read-only.
feat: add google-c2p dependence to DirectPath #1521
Merged
Merged
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
119b6d1
feat: add google-c2p dependence to DirectPath
mohanli-ml ce1227a
feat: add google-c2p dependence to DirectPath
mohanli-ml d8188d3
feat: add google-c2p dependence to DirectPath
mohanli-ml 8bfcd10
feat: add google-c2p dependence to DirectPath
mohanli-ml 77e81d7
feat: add google-c2p dependence to DirectPath
mohanli-ml 70f3af2
Merge branch 'main' into add-google-c2p
mohanli-ml 90ed61e
Merge branch 'main' into add-google-c2p
chanseokoh baaff18
Simplify code
chanseokoh db57e67
Simplify
chanseokoh 1c288e0
feat: add google-c2p dependence to DirectPath
mohanli-ml c863608
feat: add google-c2p dependence to DirectPath
mohanli-ml File filter
Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just noticed that this should be added to
dependencies.properties
, not here, so that both Bazel and Gradle resolve and use the dependency.However, the Bazel build didn't break, meaning that this is unnecessary. I also just compiled the project with Gradle manually without this, and it compiled successfully. In fact, I don't see any new class being used in the code below. Obviously, this dependency is not required for compilation. Should we remove it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you give me an example about how to add the dependency to
dependencies.properties
? And should I also remove change in bothgax-grpc/build.gradle
?Compilation can succeed because as you said, no new class is added. However, this dependency is actually registering
google-c2p
resolver to the build binary, otherwise gRPC can not recognize thegoogle-c2p:///
URI scheme and we will get error likeJava.lang.IllegalArgumentException: cannot find a NameResolver for google-c2p:///localhost
. So we should keep the dependency.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see. What you are saying sounds like the dependency is required to exist in the runtime classpath of the user consuming the gax-java library.
Since it's not required for compiling the project, let's have this as a Gradle-only dependency. I'm pretty new to this repo, so I don't know whether the Bazel build will also need this for something. However, gax-java libraries are released from Gradle, at least they will be okay. If there comes an issue on the Bazel side later, we'll take care of it later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, thanks!