Make bazel build fully hermetic

We no longer reference @bazel_tools//third_party. All of our transitive
dependencies are now specified explicitly in our WORKSPACE file.

I also fixed the way that jar dependencies are exported, so we don't
break strict dependency checking.
-------------
Created by MOE: https://github.com/google/moe
MOE_MIGRATED_REVID=116421176
This commit is contained in:
jart 2016-03-04 17:56:25 -08:00 committed by Justine Tunney
parent ab26b288c1
commit a063508b5b
33 changed files with 124 additions and 70 deletions

View file

@ -31,7 +31,7 @@ java_plugin(
visibility = ["//visibility:private"],
deps = [
"@auto_factory//jar",
"@bazel_tools//third_party:guava",
"@guava//jar",
"@javawriter//jar",
":auto_common",
],
@ -43,7 +43,7 @@ java_plugin(
visibility = ["//visibility:private"],
deps = [
"@auto_service//jar",
"@bazel_tools//third_party:guava",
"@guava//jar",
":auto_common",
],
)
@ -54,8 +54,8 @@ java_plugin(
visibility = ["//visibility:private"],
deps = [
"@auto_value//jar",
"@bazel_tools//third_party:guava",
"@bazel_tools//third_party:jsr305",
"@guava//jar",
":auto_common",
"//third_party/java/jsr305_annotations",
],
)