aboutsummaryrefslogtreecommitdiffhomepage
path: root/site/docs/tutorial
diff options
context:
space:
mode:
authorGravatar Peter Laird <laird_peter@yahoo.com>2017-10-12 16:44:19 +0200
committerGravatar Marcel Hlopko <hlopko@google.com>2017-10-13 13:51:53 +0200
commit4b16e02aabf08b154cb2258930e76a59a741206f (patch)
tree1f55b6494ab3a6faad7f7620561dba6fb8e17c62 /site/docs/tutorial
parentfaf2db22277bd0b074a0a8c5cd4533a735eff31a (diff)
Clarify the direction of visibility in the tutorial
The original text makes it sound like greeter target needs visibility to the runner target. It is the other way around. Closes #3866. PiperOrigin-RevId: 171958509
Diffstat (limited to 'site/docs/tutorial')
-rw-r--r--site/docs/tutorial/java.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/site/docs/tutorial/java.md b/site/docs/tutorial/java.md
index 0c5cafb5e8..e273776316 100644
--- a/site/docs/tutorial/java.md
+++ b/site/docs/tutorial/java.md
@@ -279,8 +279,8 @@ Take a look at the dependency graph:
![Dependency graph of the target 'runner'](/assets/tutorial_java_03.svg)
-However, for the build to succeed, you must make the `runner` target in
-`//src/main/java/com/example/cmdline/BUILD` explicitly visible to targets in
+However, for the build to succeed, you must explicitly give the `runner` target in
+`//src/main/java/com/example/cmdline/BUILD` visibility to targets in
`//BUILD` using the `visibility` attribute. This is because by default targets
are only visible to other targets in the same `BUILD` file. (Bazel uses target
visibility to prevent issues such as libraries containing implementation details