Google Git
Sign in
apache / beam / refs/tags/v2.27.0 / . / vendor
tree: bf2c0af27f774c8fd30b2ce5ce68d67cf0667140 [path history] [tgz]
  1. bytebuddy-1_10_8/
  2. calcite-1_20_0/
  3. grpc-1_26_0/
  4. guava-26_0-jre/
  5. sdks-java-extensions-protobuf/
  6. README.md
vendor/README.md

Vendored Dependencies Release

The upgrading of the vendored dependencies should be performed in two steps:

  • Firstly, we need to perform a formal release of the vendored dependency. The release process of the vendored dependency is separate from the release of Apache Beam.
  • When the release of the vendored dependency is out, we can migrate Apache Beam to use the newly released vendored dependency.

How to validate the vendored dependencies

The linkage tool is useful for the vendored dependency upgrades. It reports the linkage errors across multiple Apache Beam artifact ids.

For example, when we upgrade the version of gRPC to 1.26.0 and the version of the vendored gRPC is 0.1-SNAPSHOT, we could run the linkage tool as following:

./gradlew -PvendoredDependenciesOnly -Ppublishing -PjavaLinkageArtifactIds=beam-vendor-grpc-1_26_0:0.1-SNAPSHOT :checkJavaLinkage