diff options
author | juliexxia <juliexxia@google.com> | 2017-10-04 21:42:01 +0200 |
---|---|---|
committer | Klaus Aehlig <aehlig@google.com> | 2017-10-06 19:44:54 +0200 |
commit | 7de7ea0113d73427d2ee45b4728732eeb0ee3b0a (patch) | |
tree | 44e72aa973cebf39d708525a6263c7ea7c065063 | |
parent | f531ac9db81b0556b640a4a60d01a2256013b3bc (diff) |
Could be missing something but I don't think this line of documentation is true anymore. Looks like now each build command instantiates its own BuildTool to work with instead of BlazeRuntime holding a single instance that gets re-used.
PiperOrigin-RevId: 171047696
-rw-r--r-- | src/main/java/com/google/devtools/build/lib/buildtool/BuildTool.java | 4 |
1 files changed, 0 insertions, 4 deletions
diff --git a/src/main/java/com/google/devtools/build/lib/buildtool/BuildTool.java b/src/main/java/com/google/devtools/build/lib/buildtool/BuildTool.java index 6f0d2fbb0e..e8649a55ed 100644 --- a/src/main/java/com/google/devtools/build/lib/buildtool/BuildTool.java +++ b/src/main/java/com/google/devtools/build/lib/buildtool/BuildTool.java @@ -85,10 +85,6 @@ import java.util.regex.Pattern; * * <p>The main entry point is {@link #buildTargets}. * - * <p>This class is always instantiated and managed as a singleton, being constructed and held by - * {@link BlazeRuntime}. This is so multiple kinds of build commands can share this single - * instance. - * * <p>Most of analysis is handled in {@link BuildView}, and execution in {@link ExecutionTool}. */ public final class BuildTool { |