Extract proguard rules found in imported JAR archives

In Android Studio R8 is able to use bundled proguard
rules found both in AAR archives (under /proguard.txt)
and JAR archives (under /META-INF/proguard/*)

Soong currently only handles the _easier_ AAR format
and ignores the possibility to have rules in JAR archives.

To support those rules we use the newly introduced
ExtractR8Rules cli tool in R8 to extract all the embedded
rules in the imported JAR for later propagation.

Bug: 377144587
Test: m, including okhttp-4.12.0.jar now doesn't create R8 warnings.
Change-Id: I10f9bbf76bc8daec1ec470fb493e399d1beffc8a

1 files changed, 17 insertions, 0 deletions

diff --git a/java/java.go b/java/java.go
index a975ca61c..0ab344066 100644
--- a/java/java.go
+++ b/java/java.go
@@ -2827,6 +2827,23 @@ func (j *Import) GenerateAndroidBuildActions(ctx android.ModuleContext) {
 		outputFile = combinedJar
 	}
 
+	proguardFlags := android.PathForModuleOut(ctx, "proguard_flags")
+	TransformJarToR8Rules(ctx, proguardFlags, outputFile)
+
+	transitiveProguardFlags, transitiveUnconditionalExportedFlags := collectDepProguardSpecInfo(ctx)
+	android.SetProvider(ctx, ProguardSpecInfoProvider, ProguardSpecInfo{
+		ProguardFlagsFiles: depset.New[android.Path](
+			depset.POSTORDER,
+			android.Paths{proguardFlags},
+			transitiveProguardFlags,
+		),
+		UnconditionallyExportedProguardFlags: depset.New[android.Path](
+			depset.POSTORDER,
+			nil,
+			transitiveUnconditionalExportedFlags,
+		),
+	})
+
 	// Save the output file with no relative path so that it doesn't end up in a subdirectory when used as a resource.
 	// Also strip the relative path from the header output file so that the reuseImplementationJarAsHeaderJar check
 	// in a module that depends on this module considers them equal.