Since version 0.10.0rc1 Bazel started to include version in release
candidate and this broke version check in Bazel Gerrit CI: [1].
bazel-skylib is a project from the Bazel community that exposes utility
rules. Consume working Bazel minimum version check from this repository.
This version parsing machinery was adapted to work with release
candidate version, by omiting rcx part during parsing. See this issue
for more details: [2].
This change also bumps required bazel version to 0.7.0.
[1] https://ci.bazel.build/blue/organizations/jenkins/Global%2Fgerrit/detail/gerrit/345/pipeline
[2] https://github.com/bazelbuild/bazel/issues/4425
Change-Id: Ie3e17ea327c556daa234aeebbc2919be51109e91
If bazel is too old fail build early with a precise error message.
Idea taken from [1].
[1] 6c2aaacb5b
Change-Id: I5dafd1ab7b88caa19707b68d4a07c3b9ab9005cf
I've said before that I don't expect there to be a 2.16, and 3.0 will be
the next version. I still believe that, but here I'm hedging.
Change-Id: I0722d582cfec4d5c08dffc83c24efc34613a345e
Reformat the Bazel build files with the buildifier tool [1].
The style is different for Bazel files. Most notably, indentation level
is 4 spaces instead of 2, and " is used instead of '.
[1] https://github.com/bazelbuild/buildifier
Change-Id: I95c0c6f11b6d76572797853b4ebb5cee5ebd3c98
Currently too big files are published, because some unwanted transitive
dependencies are included in the final artifacts. That will be fixed in
follow-up change by using neverlink option in java_library rule or using
provided_deps attribute that will be addded in future releases of Bazel:
[1].
TEST PLAN:
$ VERBOSE=1 tools/maven/api.sh install bazel
$ VERBOSE=1 tools/maven/api.sh install buck
* [1] https://github.com/bazelbuild/bazel/issues/1402
Change-Id: Ie73d4ae34d96be7f97f6329c4c30c814f54688d5
