summaryrefslogtreecommitdiff
path: root/tools/aapt2/java/JavaClassGenerator_test.cpp
diff options
context:
space:
mode:
authorJiyong Park <jiyong@google.com>2019-05-11 00:00:35 +0900
committerJiyong Park <jiyong@google.com>2019-05-11 12:40:50 +0900
commit6651eb21425fd7b7032f733ebad3d0d0961f097c (patch)
treeb33ee62a0e6c8138cabef5bf13ce416e02297763 /tools/aapt2/java/JavaClassGenerator_test.cpp
parent60d2586b2caa32a712019f4d026b6183cf9203c2 (diff)
Add workaround for b/124210145
Problem description: Metalava emits signature of a method under a class, even when the method is not defined in the class when the method is inherited from a hidden ancestor and the method is part of the public interface that the class is expected to implement. To be specific, inside the api signature, MmbmsDownloadServiceBase has asBinder() and onTransact(). The methods are not defined in the class but inherited from the auto-generated hidden class IMbmsDownloadService.Stub. However, since the methods are also declared in the public ancestors of the class, e.g., Binder and IInterface, the methods are force-included in the class. Omitting the methods will cause problem when building the stub version of the class. This inclusion of the inherited method is breaking SystemApiAnnotationTest. That's because the test ensures that a symbol listed in the API signature file for the System API is actually annotated with @SystemApi. Solution: To workaround the issue, actually implement the auto-generated methods inside the class and annotate them. Bug: 124210145 Test: atest CtsSystemApiAnnotationTestCases Change-Id: I6760f6e4068239361c495ae7c0de3e25f91d38e1
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions