diff options
| author |  Jingwen Chen <jin@crypt.sg> | 2018-01-22 11:47:29 -0800 |
|---|---|---|
| committer |  Copybara-Service <copybara-piper@google.com> | 2018-01-22 11:49:07 -0800 |
| commit | ec41eaea04b3ee39f0457a51a05eabf4d84431fd (patch) | |
| tree | fd6a7e95d0ee8d436c99b8766a36f696a2a4b407 /site | |
| parent | 2f80e5895fbcc4fc4102e57660cd631eba731b04 (diff) | |
Fixed docs: `bazel fetch` is not a required manual step before `bazel build`
Closes #4490.
PiperOrigin-RevId: 182812418
Diffstat (limited to 'site')
| -rw-r--r-- | site/docs/user-manual.html | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/site/docs/user-manual.html b/site/docs/user-manual.html index 34db84b3b6..33dfcdbcdc 100644 --- a/site/docs/user-manual.html +++ b/site/docs/user-manual.html @@ -649,8 +649,8 @@ $ bazel fetch //... <p> You do not need to run bazel fetch at all if you have all of the tools you are using (from library jars to the JDK itself) under your workspace root. - However, if you're using anything outside of the workspace directory then you - will need to run <code>bazel fetch</code> before running + However, if you're using anything outside of the workspace directory then Bazel + will automatically run <code>bazel fetch</code> before running <code>bazel build</code>. </p> |