Remove duplicate documentation about Target Pattern syntax
The documentation appeared in both:
https://docs.bazel.build/versions/master/guide.html#target-patterns
and:
https://docs.bazel.build/versions/master/command-line-reference.html#target-pattern-syntax
I've taken mostly the section from command-line-reference, and moved it to the User Guide.
RELNOTES: None.
PiperOrigin-RevId: 217785381
diff --git a/site/command-line-reference-prefix.html b/site/command-line-reference-prefix.html
index 38e1460..59f2b79 100644
--- a/site/command-line-reference-prefix.html
+++ b/site/command-line-reference-prefix.html
@@ -14,6 +14,9 @@
bazel [<startup options>] <command> [<args>] -- [<target patterns>]
</pre>
+See the <a href="guide.html#target-patterns">User's Guide</a> for the
+target patterns syntax.
+
<h2>Option Syntax</h2>
<p>
@@ -56,126 +59,3 @@
--<option>=[false|no|0]
</pre>
</p>
-
-<h2>Target Pattern Syntax</h2>
-
-<p>
-A target pattern refers to a single or more targets, which are source files,
-output files, or rules specified in BUILD files. In addition to plain labels,
-Bazel also supports working-directory-relative labels, recursive patterns, and
-target subtraction.
-</p>
-
-<p>
-All target patterns starting with '//' are resolved relative to the current
-workspace.
-<table>
-<tr>
- <td><code>//foo/bar:wiz</code></td>
- <td>Just the single target '//foo/bar:wiz'.</td>
-</tr>
-<tr>
- <td><code>//foo/bar</code></td>
- <td>Equivalent to '//foo/bar:bar'.</td>
-</tr>
-<tr>
- <td><code>//foo/bar:all</code></td>
- <td>All rules in the package 'foo/bar'.</td>
-</tr>
-<tr>
- <td><code>//foo/...</code></td>
- <td>All rules in all packages beneath the directory 'foo'.</td>
-</tr>
-<tr>
- <td><code>//foo/...:all</code></td>
- <td>All rules in all packages beneath the directory 'foo'.</td>
-</tr>
-<tr>
- <td><code>//foo/...:*</code></td>
- <td>All targets (rules and files) in all packages beneath the directory 'foo'.</td>
-</tr>
-<tr>
- <td><code>//foo/...:all-targets</code></td>
- <td>All targets (rules and files) in all packages beneath the directory 'foo'.</td>
-</tr>
-</table>
-</p>
-
-<p>
-Targets with <code>tags=["manual"]</code> are not included in wildcard
-target patterns (<code>...</code>, <code>:*</code>, <code>:all</code>, etc).
-Specify such test targets with explicit labels on the command line if
-you want Bazel to build/test them.
-</p>
-
-<p>
-Target patterns which do not begin with '//' are resolved relative to the
-current <em>working directory</em>. These examples assume a working directory of
-'foo':
-<table>
-<tr>
- <td><code>:foo</code></td>
- <td>Equivalent to '//foo:foo'.</td>
-</tr>
-<tr>
- <td><code>bar:wiz</code></td>
- <td>Equivalent to '//foo/bar:wiz'.</td>
-</tr>
-<tr>
- <td><code>bar/wiz</code></td>
- <td>Equivalent to:
- '//foo/bar/wiz:wiz' if foo/bar/wiz is a package,
- '//foo/bar:wiz' if foo/bar is a package,
- '//foo:bar/wiz' otherwise.
- </td>
-</tr>
-<tr>
- <td><code>bar:all</code></td>
- <td>Equivalent to '//foo/bar:all'.</td>
-</tr>
-<tr>
- <td><code>:all</code></td>
- <td>Equivalent to '//foo:all'.</td>
-</tr>
-<tr>
- <td><code>...:all</code></td>
- <td>Equivalent to '//foo/...:all'.</td>
-</tr>
-<tr>
- <td><code>...</code></td>
- <td>Equivalent to '//foo/...:all'.</td>
-</tr>
-<tr>
- <td><code>bar/...:all</code></td>
- <td>Equivalent to '//foo/bar/...:all'.</td>
-</tr>
-</table>
-</p>
-
-<p>
-By default, directory symlinks are followed for recursive target patterns,
-except those that point to under the output base, such as the convenience
-symlinks that are created in the root directory of the workspace.
-</p>
-
-<p>
-In addition, Bazel does not follow symlinks when evaluating recursive target
-patterns in any directory that contains a file named as follows:
-<pre>
-DONT_FOLLOW_SYMLINKS_WHEN_TRAVERSING_THIS_DIRECTORY_VIA_A_RECURSIVE_TARGET_PATTERN
-</pre>
-</p>
-
-<p>
-Target patterns may be preceded by a single dash ('<code>-</code>'), in which
-case Bazel subtracts them from the set of targets accumulated by preceding
-patterns. Note that this means <em>order matters</em>. In order to pass negative
-target patterns, you need to use '--' as an argument to prevent Bazel from
-interpreting it as an option, e.g.:
-<pre>
-bazel build -- foo/... -foo/contrib/...
-</pre>
-Note that Bazel may still build targets matched by a negative target pattern due
-to dependencies, and may also load the corresponding BUILD files, even if the
-targets are never built.
-</p>
