Introduce the blaze cquery command as the new ui for configurable query.

before: blaze build --nobuild //foo --experimental_post_build_query="deps(//foo)"
after: blaze cquery "deps(//foo)"

pros of ui change:
- more concise
- assumes query expression targets == targets to be built (but allows for flexibility through --top_level_targets flag)
- separate from build command
- cquery command recognizes query options, build options, and its own unique set of options

cons of ui change:
- adds another command to blaze
- recognizes options that don't actually work yet -> requires more option validation

RELNOTES: None
PiperOrigin-RevId: 181816980

1 files changed, 12 insertions, 0 deletions

diff --git a/src/main/java/com/google/devtools/build/lib/query2/BUILD b/src/main/java/com/google/devtools/build/lib/query2/BUILD
index 8f143033ba..8a0d01f136 100644
--- a/src/main/java/com/google/devtools/build/lib/query2/BUILD
+++ b/src/main/java/com/google/devtools/build/lib/query2/BUILD
@@ -43,6 +43,7 @@ java_library(
     srcs = glob(["output/*.java"]),
     deps = [
         ":abstract-blaze-query-env",
+        ":common-query-options",
         ":fake-load-target",
         ":query-engine",
         "//src/main/java/com/google/devtools/build/lib:events",
@@ -74,6 +75,17 @@ java_library(
 )
 
 java_library(
+    name = "common-query-options",
+    srcs = [
+        "CommonQueryOptions.java",
+    ],
+    deps = [
+        ":query-engine",
+        "//src/main/java/com/google/devtools/common/options",
+    ],
+)
+
+java_library(
     name = "fake-load-target",
     srcs = [
         "FakeLoadTarget.java",