4.7 of 5: Remove serialization of transitive dependencies.

Serializer no longer serializes transitive resources. That turned out to be a performance issue with large trees. Instead,it relies on the build tool to indicate the direct and transitive resources. This reduces the number of keys that get pulled from diamond dependencies and stays much, much leaner.

--
MOS_MIGRATED_REVID=121382705

1 files changed, 2 insertions, 7 deletions

diff --git a/src/tools/android/java/com/google/devtools/build/android/proto/serialize_format.proto b/src/tools/android/java/com/google/devtools/build/android/proto/serialize_format.proto
index 039f0ff25b..2c97642bd6 100644
--- a/src/tools/android/java/com/google/devtools/build/android/proto/serialize_format.proto
+++ b/src/tools/android/java/com/google/devtools/build/android/proto/serialize_format.proto
@@ -23,13 +23,8 @@ option java_package = "com.google.devtools.build.android.proto";
 // See com.google.devtools.build.android.AndroidDataSerializer for details on
 // how these messages are used.
 message Header {
-  // The number of primary entries stored a serialized buffer.
-  optional int32 primary_entries = 1;
-  // The number of transitive entries stored a serialized buffer.
-  optional int32 transitive_entries = 2;
-  // The source information for the manifest associated with these resources.
-  // Required
-  optional ProtoSource manifest_path = 3;
+  // The number of entries stored in a serialized buffer.
+  optional int32 entry_count = 1;
 }
 
 // The serialized format for a DataKey.