Remove misleading documentation about 'transitive-deps' target
This target is not actually generated by generate_workspace.
Change-Id: Idcaa138bf56021b281138d60a06befa8c9579b1d
PiperOrigin-RevId: 160295136
diff --git a/site/docs/external.md b/site/docs/external.md
index 5211eea..b997191 100644
--- a/site/docs/external.md
+++ b/site/docs/external.md
@@ -158,10 +158,7 @@
```
The `WORKSPACE` file will contain the transitive dependencies of the given
-projects and artifacts. The `BUILD` file will contain a single target,
-`transitive-deps`, that contains all of the dependencies. You can copy these
-files to your project and add `transitive-deps` as a dependency of your `java_`
-targets in `BUILD` files.
+projects and artifacts.
If you specify multiple Bazel projects, Maven projects, or artifacts, they will
all be combined into one `WORKSPACE` file (e.g., if the Bazel project depends on
@@ -193,10 +190,6 @@
version 1.1 and three of them wanted 1.0.2. The `WORKSPACE` file is using
version 1.1, but that might not be the right version to use.
-You may also want to break `transitive-deps` into smaller targets, as it is
-unlikely that all of your targets depend on the transitive closure of your
-maven jars.
-
## Caching of external dependencies
Bazel caches external dependencies and re-downloads or updates them when
