[BEAM-9444] Use GCP BOM to set package versions

[kileys]

Use GCP libraries bom to set versions for GCP related libraries

Updated version of #11156

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

• Choose reviewer(s) and mention them in a comment (R: @username).
• Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
• Update CHANGES.md with noteworthy changes.
• If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

Post-Commit Tests Status (on master branch)

Lang	SDK	Dataflow	Flink	Samza	Spark	Twister2
Go		---		---		---
Java
Python				---		---
XLang		---		---		---

Pre-Commit Tests Status (on master branch)

---	Java	Python	Go	Website	Whitespace	Typescript
Non-portable
Portable	---		---	---	---	---

See .test-infra/jenkins/README for trigger phrase, status and link of all Jenkins jobs.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

[kileys]

Run Java examples on Dataflow Java 11

[kileys]

Run Dataflow ValidatesRunner Java 11

[kileys]

Run Dataflow ValidatesRunner

[kileys]

Run Java PostCommit

[github-actions]

The Build Workflow run is cancelling this PR. It in earlier duplicate of 2173354 run.

[kennknowles]

Run Spotless PreCommit

[kennknowles]

I don't see any reason for that strange error in spotless.

[kileys]

Run Python PreCommit

[kileys]

Run Python_PVR_Flink PreCommit

[kileys]

Run Spark ValidatesRunner

[kileys]

Run Dataflow ValidatesRunner

[kileys]

@suztomo are there other tests I should run to verify this? Linkage checker runs without any new errors

[kileys]

R: @kennknowles, @suztomo, @lukecwik

[kileys]

The Dataflow validates runner tests are also failing on master

[suztomo]

are there other tests I should run to verify this?

Not that I know of.

[lukecwik]

Also, it seems as though existing modules that don't add a platform level dep to the GCP libraries bom will get some version of the dep since we have cleared the version.

[kennknowles]

LGTM

[kileys]

Run Java PreCommit

[kileys]

Run Python PreCommit

[kileys]

Run Java_Examples_Dataflow PreCommit

[kennknowles]

It does seem that if a module had any of these deps but forgot the enforcedPlatform line then it would go back to getting the arbitrary latest version. I understand fixing that is in a follow-up.

Here's what I did to view the dep changes:

# gcp is GNU cp here
mkdir ~/tmp/deps-before
git checkout github/master
./gradlew dependencyReport
find . -name dependencies.txt -exec gcp --parents \{\} ~/tmp/deps-before/ \;

mkdir ~/tmp/deps-after
git checkout github/pr/13075
./gradlew dependencyReport
find . -name dependencies.txt -exec gcp --parents \{\} ~/tmp/deps-after/ \;

diff --brief --recursive ~/tmp/deps-before ~/tmp/deps-after

diff --unified=0 --recursive ~/tmp/deps-before ~/tmp/deps-after

[kennknowles]

I do not have the capacity to manually determine the possible consequences of the dep changes, which do affect modules not listed (for example autovalue annotations are downgraded a couple patch versions).

I was checking just for modules that were accidentally "upgraded" to the latest by not having a version or that were accidentally downgraded because the BOM reduced versions they depended on that had nothing to do with GCP. I did not find any problems, but it is too much content to be certain. Still, it is surely an improvement.