build(core): add direct guava test dependency #663
Merged
Conversation
This file contains hidden or 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
Signed-off-by: Niels Pardon <[email protected]>
nielspardon
requested review from
andrew-coleman,
benbellick,
bestbeforetoday and
vbarua
andrew-coleman
approved these changes
Jan 7, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This unblocks the protobuf upgrade PR: #658
We are using the
Resourcesfrom guava inTestBaseincore.protobuf-java-util v4 has dropped the dependency on guava which means guava is no longer on the classpath when upgrading to v4. By declaring a direct test dependency on guava we make it clear that we are using guava during testing and can ensure the code still compiles when we upgrade to protobuf v4.