Expose aar_import data processing methods to Skylark

Because of the special nature of aar_import, I don't think it makes much sense
to split up the different parts - you always get everything out of the AAR.

RELNOTES: none
PiperOrigin-RevId: 196152640

1 files changed, 0 insertions, 6 deletions

diff --git a/src/main/java/com/google/devtools/build/lib/rules/android/ParsedAndroidAssets.java b/src/main/java/com/google/devtools/build/lib/rules/android/ParsedAndroidAssets.java
index 696643328f..ac5c19df2a 100644
--- a/src/main/java/com/google/devtools/build/lib/rules/android/ParsedAndroidAssets.java
+++ b/src/main/java/com/google/devtools/build/lib/rules/android/ParsedAndroidAssets.java
@@ -45,12 +45,6 @@ public class ParsedAndroidAssets extends AndroidAssets implements MergableAndroi
   }
 
   /** Merges these assets with assets from dependencies. */
-  public MergedAndroidAssets merge(RuleContext ruleContext, boolean neverlink)
-      throws InterruptedException {
-    return MergedAndroidAssets.mergeFrom(
-        ruleContext, this, AssetDependencies.fromRuleDeps(ruleContext, neverlink));
-  }
-
   MergedAndroidAssets merge(RuleContext ruleContext, AssetDependencies assetDeps)
       throws InterruptedException {
     return MergedAndroidAssets.mergeFrom(ruleContext, this, assetDeps);