Build databinding annotation processor in host configuration.

Also, add a fake databinding processor target.

Bazel users will need to do something like this:

# WORKSPACE
local_repository(
    name = "databinding",
    path = "./databinding",
)
bind(
    name = "databinding_annotation_processor",
    actual = "@databinding//:annotation_processor",
)

# databinding/BUILD
java_plugin(
    name = "annotation_processor",
    ...
)
...

https://github.com/bazelbuild/bazel/issues/2694

RELNOTES: None
PiperOrigin-RevId: 175975110

1 files changed, 7 insertions, 0 deletions

diff --git a/src/test/java/com/google/devtools/build/lib/rules/android/AndroidDataBindingTest.java b/src/test/java/com/google/devtools/build/lib/rules/android/AndroidDataBindingTest.java
index e39ac4ddee..e8c4115f85 100644
--- a/src/test/java/com/google/devtools/build/lib/rules/android/AndroidDataBindingTest.java
+++ b/src/test/java/com/google/devtools/build/lib/rules/android/AndroidDataBindingTest.java
@@ -284,4 +284,11 @@ public class AndroidDataBindingTest extends AndroidBuildViewTestCase {
         "package android.binary; public class MyApp {};");
     assertThat(getConfiguredTarget("//java/android/binary:app")).isNotNull();
   }
+
+  @Test
+  public void testNoJvmFragment() throws Exception {
+    writeDataBindingFiles();
+    useConfiguration("--experimental_disable_jvm");
+    assertThat(getConfiguredTarget("//java/android/binary:app")).isNotNull();
+  }
 }