Express existing okhttp dependency manipulation at project wide scope #9
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.
okhttp version is now consistent across all its modules
when in jdk mode, the only okhttp3 dependency is a test one, on the mockwebserver. (There's a compile time dependency on mockwebserver (org.apache.flink.kubernetes.operator.TestUtils), so we can't make that dependency's inclusion based on the profile).
I gave the unit tests a spin locally both with and without
depend-on-okhttp4
. All is green for me.