PiperOrigin-RevId: 219174684
GitOrigin-RevId: 5bb467f9122872ca67aa3e28205c14166578e33b
(cherry picked from commit 29ef947d)

Apparently 0.16.x causes some issue with JDK 9. Using bazel 0.15.2 works fine.

Relevant CL: cr/208638300. It needs more work but once fixed we can revert this CL.

PiperOrigin-RevId: 209490913
GitOrigin-RevId: 9661ca621f0a58f85bcc71e139c4dc0167b677da

Do not run Bazel with a custom JAVA_HOME, because Bazel now comes with an embedded JDK9 for running itself and the host tools.

PiperOrigin-RevId: 206848312
GitOrigin-RevId: 7858df73f14c76e16d4b7444b346ebc737f5c341

PiperOrigin-RevId: 206051640
GitOrigin-RevId: c48ddf5fbdd7152044e20a21820849578980d60c

Performing the checks in both release.sh (to fail early) and run_test.sh (where they're actually required).

Also, quoting cleanup in run_test.sh.

PiperOrigin-RevId: 206040628
GitOrigin-RevId: da6dc3b744001940260512cfbfd76b1943ffdb71

Using the latest rules_apple release fixes the previous continuous integration build failure. This is due to the inclusion of the following commit:
https://github.com/bazelbuild/rules_apple/commit/d24f9791e62ba3edcad69114fe4944e063681b39

Which is required due to a change in bazel 0.15.0. From https://github.com/bazelbuild/bazel/releases/tag/0.15.0:

"non_propagated_deps has been removed from objc_library and apple_binary."

PiperOrigin-RevId: 203977097
GitOrigin-RevId: 791887c15d86d72d8e21fcf3bc82ac14378f8084

I don't actually know how Maven works, but the error message indicates that we actually need Gauva.

Also I added a test to prevent this bug from happening, but I forgot to make it run =).

PiperOrigin-RevId: 196337621
GitOrigin-RevId: 3cdbc775903204bf11762c80a296c1876a9bda3f

PiperOrigin-RevId: 193553145
GitOrigin-RevId: 137ef485e98928f3bbae67feb777896b3ef0a7e5

Also, enabled the iOS tests.

PiperOrigin-RevId: 192352304
GitOrigin-RevId: e8ea4a22cac9b90861e6561c8c5f657253a85bb7

PiperOrigin-RevId: 190277149
GitOrigin-RevId: f098896cbbba5d1caf64c88b3edc2f38883d7b4d

PiperOrigin-RevId: 190145488
GitOrigin-RevId: c7fa32c67bfd64cb0ab0d5aebe41ba31102cd4f4

PiperOrigin-RevId: 190137127
GitOrigin-RevId: cecaa3b03ef39d8d48b5d64c16826ca1bb9b3a6c

This makes migrating changes between GitHub and GoB easier.

The copybara script is being moved to Piper, and nobody is actually
using the other script.

Change-Id: I876e0ff90995e7d49fa97d57b86aee5d2e66b14a
ORIGINAL_AUTHOR=Thai Duong <thaidn@google.com>
GitOrigin-RevId: e8463a41307fa0e81a8334cad4708dcc5316ed80

We no longer need to maintain Maven as a separate build and test system.
This would save us a lot of time, as Maven is not exactly nice to deal
with.

This also allows us to simplify the poms, especially the dependencies.
For example, to use Tink for Android users no longer have to set
$ANDROID_HOME.

Change-Id: I925b37409f8ed5e32f228d8de0f0845ea38bc427
ORIGINAL_AUTHOR=Google Engineers <noreply@google.com>
GitOrigin-RevId: 49470c492c6bc1d28960c243b671208863ccdf6b

Change-Id: I5b7e32a11a40ef1bb6236cc0a5c1b7f030f201e1
ORIGINAL_AUTHOR=Google Engineers <noreply@google.com>
GitOrigin-RevId: 1dc2f9b232006e087d30052fc98df76baf604d21

Change-Id: Ifa509daa77d8994663dd3c3faca7ef6126ed8971
ORIGINAL_AUTHOR=Thai Duong <thaidn@google.com>
GitOrigin-RevId: 72ffad31af12c4bb50a555a52e6192fdf90c661e

Change-Id: Iab0e95bfe1b434e47146443ba4a6963c06c6f63d
ORIGINAL_AUTHOR=Haris Andrianakis <candrian@google.com>
GitOrigin-RevId: d27fdd8c3eb34775beae370b1d65d25b91136d61

Change-Id: Iab1084bf72c8888d71bb1ca0e2ee1bafacddc98c
ORIGINAL_AUTHOR=Thai Duong <thaidn@google.com>
GitOrigin-RevId: 963cfe6f9abf0492473fb94f446d89ef0110da0b

The build is failing probably because Kokoro upgraded its Ubuntu image.

This image doesn't have the unlimited Java policy, thus tests with
256-bit keys failed. These tests are skipped now. I also temporarily
remove tests with 256-bit keys from AEAD cross-language tests. These
tests will be reinstalled after b/35928521 is fixed.

The Go compiler on Kokoro, which is at version go1.9 linux/amd64, refuses
to compile our Go code because it found a cycle dependency. This is somehow
not a problem with the version of Go on my workstation. Fortunately, the
cycle dependency is in a test, so I temporarily removed it. I'm working on
a better fix which moves the test to a different package.

I also upgrade Bazel to 0.9.0 and use rules-apple at
a2b620070d373e4f265194b69f65e9e5c17fbcb8, instead of master, which is known
to work well with Bazel 0.9.0.

Change-Id: I97229342065f12d0eec6ff31b54922161267943a
ORIGINAL_AUTHOR=Thai Duong <thaidn@google.com>
GitOrigin-RevId: 0e96efbd943ddc3c97a2b7d573f7e20b78781a5d

Change-Id: I4fd5d11d4f6c47ca73f9fb537d42ea42e22f7376
ORIGINAL_AUTHOR=Thai Duong <thaidn@google.com>
GitOrigin-RevId: 2ebf79fbfd3759a6cdd8be8298f1ae6047aec028

Change-Id: Ia428e1f4134925a7f9e32d55565481ace06a620d
ORIGINAL_AUTHOR=Thai Duong <thaidn@google.com>
GitOrigin-RevId: d6bdd242940dc59a2d4882d577b0d23deb81492a

Change-Id: Id1e074f85425d54b008230f961837e21c6d13134
ORIGINAL_AUTHOR=Thai Duong <thaidn@google.com>
GitOrigin-RevId: 5e5740a97a2161ca5c8b580d38820ebaab21802b

run_all_tests.sh will execute all Bazel tests including manual ones.

Change-Id: I531f8e0f88f9ac4ab5c2cfff0c70174aece2f401
ORIGINAL_AUTHOR=Thai Duong <thaidn@google.com>
GitOrigin-RevId: 55d2c718bfcde76fcb1d2fdc4825fc2466db682a

This hopefully reduces compilation time which is accounting
for more than 70% of running time of presubmit tests on Kokoro.

Change-Id: I3e6e0505c247f71589ceba009b38e17bf03acb39
ORIGINAL_AUTHOR=Thai Duong <thaidn@google.com>
GitOrigin-RevId: dc2cb661d02b1fe045b6785bb6e62182d1d04b5e

This is a temporary workaround until Kokoro upgrades its copy.

Change-Id: I018f04ef495f7135fd0b235aed0b8195e6f2e562
ORIGINAL_AUTHOR=Thai Duong <thaidn@google.com>
GitOrigin-RevId: d8be177e1e9b982d4e2f73566fbb280465af31bb

Change-Id: I224c3b48973c56ab6d0689e74588fa951af1ad30
ORIGINAL_AUTHOR=Thai Duong <thaidn@google.com>
GitOrigin-RevId: a68bbb90236ddf5c32e0dc927cb12dca01aa1221

Change-Id: I6721400f739407cfb63129cb025407ba048bc171
ORIGINAL_AUTHOR=Thai Duong <thaidn@google.com>
GitOrigin-RevId: 45f520c5495272a28aa1f6366d4d30c96b840a4f

This reverts commit 64e6515028ad5ef44b02548b4b82c9d5d81e2829.

Change-Id: Ib18226363a3d92b5c792f5009eff773450b9c689
ORIGINAL_AUTHOR=Thai Duong <thaidn@google.com>
GitOrigin-RevId: 0bd867e5f701094e12683f65fff4aabb3600e430

Change-Id: I2044360f158cc17fe8bd8f22c015e69dbe971378
ORIGINAL_AUTHOR=Thai Duong <thaidn@google.com>
GitOrigin-RevId: 64e6515028ad5ef44b02548b4b82c9d5d81e2829

Maven is already run with continuous builds whose results
are sent to ise-crypto-build@. Also it's okay if it's broken
because we only need Maven when we want to release something.

Bug: 67016805

Change-Id: I6284835f7753d64089f58eb4274bb09059f94af6
ORIGINAL_AUTHOR=Thai Duong <thaidn@google.com>
GitOrigin-RevId: e0588be9056eae3eb18e3f4709f2748cfc5e9d21

Change-Id: I973297704c45534590d98752f95dd50cb9b3f115
ORIGINAL_AUTHOR=Thai Duong <thaidn@google.com>
GitOrigin-RevId: 5ee0f0e6eb0cc1d66ad8a49265062f078f01cda6

Change-Id: I862c1f90580f32d99d9cf4c44430f749801a0574
ORIGINAL_AUTHOR=Thai Duong <thaidn@google.com>
GitOrigin-RevId: afd20aad283aaae1741e368d7f19208f2291eca7

Also fixing Javadoc issues in XyzConfig classes and temporarily
removing registry/config logging.

Change-Id: I1032d7c3e9409ab2bbcb126fc2d99e1651e0959d
ORIGINAL_AUTHOR=Thai Duong <thaidn@google.com>
GitOrigin-RevId: f50e21a56939e97b8ce1d87029386a8d02ed7c73

Change-Id: Id21248b58980281e215d89c41d5cac5bb8054aa9
ORIGINAL_AUTHOR=Haris Andrianakis <candrian@google.com>
GitOrigin-RevId: 0766c349904b00f32db19a6dfb4978cbdef02772

Change-Id: I7d5c19b8ba195516f305ecc7a9c96366f98e4c89
ORIGINAL_AUTHOR=Haris Andrianakis <candrian@google.com>
GitOrigin-RevId: a9cd65c470ac24270bd4e865ba83637a15209887

Change-Id: I5f4542ee79236cada3cf8232c835cf0493238b73
ORIGINAL_AUTHOR=Thai Duong <thaidn@google.com>
GitOrigin-RevId: a881f8f3c71a35dfef3bfa6bc69f5392671ced9e

Because Tinkey depends on full protos, Tink for Java had provided two
flavors for every target that depends on protos. Since this new setting
allows users to dynamically select which protos they want to build Tink
with, Tink will default to lite protos and users that need full protos
(e.g., to build Tinkey) can build Tink with:

bazel build ... --define use_java_proto_full=true

Change-Id: I42c9589d96269e969f671ecc20e6578c73bda7ce
ORIGINAL_AUTHOR=Thai Duong <thaidn@google.com>
GitOrigin-RevId: 1404cfdeb3fe9c4e1c120eb5c9e57532c1c0cfa1

Change-Id: I9b5e49c2e2c84647959db87f1f34ad35c27568ca
ORIGINAL_AUTHOR=Thai Duong <thaidn@google.com>
GitOrigin-RevId: 79a576ef14b5803f7004301b79af9a0320ab0cb3

Also test with random tmp files because some tests might fail if
the files they want to write to already exist.

Change-Id: Ia8be496ced6585e4914997975f04760cad5a1012
ORIGINAL_AUTHOR=Thai Duong <thaidn@google.com>
GitOrigin-RevId: dc0215517fc44451e8fc86f08157ae97eb0d9e39

Change-Id: I2da597e99bdd7376bd4c9f8c326eb218d8888043
ORIGINAL_AUTHOR=Bartosz Przydatek <przydatek@google.com>
GitOrigin-RevId: 643ccd77799a9603b6b8e269d538f6aaa02239a5