Regenerate API signature files to correct annotation order
This does not change the API in anyway other than to enforce a
consistent, sorted order for all annotations; sorted by qualified
name of the annotation.
A simple bug in metalava meant that annotations were not sorted on an
API item that had exactly two annotations in the source. Fixing the
bug forced the regeneration of the signature files.
Bug: 143556317
Test: m checkbuild
(cherry picked from commit c4080f3561a82b3b7f8bb734214b1a8d7c33872d)
Change-Id: Ib1e75895eecf37347582207be9bace94b335a08b
Merged-In: I349f653eb4c3c9727974b3ba8164474c0123a905
1 file changed