PiperOrigin-RevId: 270278753

Change-Id: I3d960c326c913aa9f39cd92753a4c48bcfcea023

There are many ways to manage Java deps in Bazel [2], but rules_jvm_external is the only option that is officially maintained by the Bazel team. What we were using is unsupported and complicated. It also leads to dependency conflicts as described in https://github.com/google/tink/issues/189.

The new version of rules_closure and the migration to rules_jvm_external together resolve https://github.com/google/tink/issues/189, and make it possible to build a binary for Tink Javascript.

[1] https://github.com/bazelbuild/rules_jvm_external
[2] https://blog.bazel.build/2019/03/31/rules-jvm-external-maven.html

PiperOrigin-RevId: 267552697

'java' provider is deprecated and is going to be removed from bazel soon.

Also simplifying and fixing the code. Note that the "if hasattr(td, "java"):" branch was incorrect and was never accessed previously. Starlark didn't complain about it because one can call hasattr on any object. When trying to use the new provider it ended up in build errors (see rollback change cl/266444465) because the "in" operator is more restrictive and caught the bug.

PiperOrigin-RevId: 266745143

PiperOrigin-RevId: 266444465

'java' provider is deprecated and is going to be removed from blaze soon.

PiperOrigin-RevId: 266361895

PiperOrigin-RevId: 264116863

PiperOrigin-RevId: 263106297

PiperOrigin-RevId: 261633704

PiperOrigin-RevId: 260535454

PiperOrigin-RevId: 260140481

PiperOrigin-RevId: 259405335

PiperOrigin-RevId: 258324064

PiperOrigin-RevId: 258118187

To replicate:
find -name BUILD.bazel -exec sed -Ei 's/\s+# Apache 2.0$//' {} \;
find -name BUILD.bazel -exec sed -Ei 's/\s+# Apache 2.0 # keep$/  # keep/' {} \;

PiperOrigin-RevId: 257604221

PiperOrigin-RevId: 257594353

PiperOrigin-RevId: 257584807

PiperOrigin-RevId: 257574467

PiperOrigin-RevId: 257567646

PiperOrigin-RevId: 257399186

PiperOrigin-RevId: 255577505

PiperOrigin-RevId: 254284696

Add the bazel_toolchains repository to the WORKSPACE and the latest bazelrc that contains the configure options (--config=remote) needed for Remote Build Execution.

The bazelrc is for bazel version 0.27.

PiperOrigin-RevId: 254239689

PiperOrigin-RevId: 250844998

PiperOrigin-RevId: 249747173

PiperOrigin-RevId: 247685444

PiperOrigin-RevId: 245326095

The issue was with grpc: https://github.com/bazelbuild/bazel/issues/4341

PiperOrigin-RevId: 245104328

PiperOrigin-RevId: 245326095
GitOrigin-RevId: 9c16a4cc3258dfe30f5fc14f31eae45d507fbe81

NOKEYCHECK=True
PiperOrigin-RevId: 244120137
GitOrigin-RevId: a3e69d36c4c98100bd2a08011c1c54afdb215dd7

PiperOrigin-RevId: 242909760
GitOrigin-RevId: 64152d44c3bd6c54b72e41923b1bf4fc3d54a7d5

NOKEYCHECK=True
PiperOrigin-RevId: 241739854
GitOrigin-RevId: d180a24e7fa9df2e93c4e8e9d86a2981e8dea6c9

PiperOrigin-RevId: 240530095
GitOrigin-RevId: 6e89528023c88df16e7742fee44b57050c683aff

PiperOrigin-RevId: 239697009
GitOrigin-RevId: 8233b02ce1bfa30962f3f924c6ff3f9a531c777b

PiperOrigin-RevId: 239443698
GitOrigin-RevId: 5bbcd4ba5919286eb1701622f1e651d1202cdaa9

PiperOrigin-RevId: 238974764
GitOrigin-RevId: dbe2104f09e2ef7c9dc8ea504f6b84af2c0c7a2c

PiperOrigin-RevId: 238677875
GitOrigin-RevId: 094484e5ede84ab8400612d93fc2626675cb8840

PiperOrigin-RevId: 237905999
GitOrigin-RevId: 4e87e33c2a64ed7257160f033a9b241fae9519f7

PiperOrigin-RevId: 237137717
GitOrigin-RevId: 5e1303b2ad44755043a5198594fd9fa02220d8e6

PiperOrigin-RevId: 237128661
GitOrigin-RevId: cf76e75a6101ab2fd0decb0d97c671a95768546e