Resource processing pipeline uses interface instead of ResourceContainer

This allows us to use either the new AndroidResources object and its children (which are fully decoupled from asset processing) or the old ResourceContainer. We'll actually turn on decoupled asset and resource processing in an upcoming change.

We still need to create an asset-only pipeline and handle the binary case.

RELNOTES: none
PiperOrigin-RevId: 193047924

1 files changed, 4 insertions, 0 deletions

diff --git a/src/main/java/com/google/devtools/build/lib/rules/android/MergedAndroidResources.java b/src/main/java/com/google/devtools/build/lib/rules/android/MergedAndroidResources.java
index 8b7fc72481..be896110ff 100644
--- a/src/main/java/com/google/devtools/build/lib/rules/android/MergedAndroidResources.java
+++ b/src/main/java/com/google/devtools/build/lib/rules/android/MergedAndroidResources.java
@@ -121,6 +121,10 @@ public class MergedAndroidResources extends ParsedAndroidResources {
     return dataBindingInfoZip;
   }
 
+  public Artifact getJavaClassJar() {
+    return classJar;
+  }
+
   @Override
   public ProcessedAndroidManifest getStampedManifest() {
     return manifest;