Prepare for keeping concrete overrides of abstract methods
Currently, metalava will discard concrete overrides of abstract methods
from the API signature files which causes problems when attempting to
generate stubs from those files and also discards information that may
be important in API reviews. This change is the first step in the
process of changing that behavior.
This change hard codes the current behavior for discarding the concrete
overrides (`add-additional-overrides=no`) into those signature files
that will (or are likely) to be affected by the change in behavior.
That allows the default behavior to be changed for all the other files
without affecting these.
Follow up changes will remove the hard coding from the signature files
and will update the contents which will include the concrete overrides
of the abstract methods.
More information and the background for this change is available at
go/add-overriding-one-pager.
Test: m checkapi
Bug: 299366704
Change-Id: Iaa665f1a678c37123e0fe1bda1a675282e733e05
diff --git a/car-lib/api/current.txt b/car-lib/api/current.txt
index aca2ed7..d348de4 100644
--- a/car-lib/api/current.txt
+++ b/car-lib/api/current.txt
@@ -1,4 +1,6 @@
// Signature format: 2.0
+// - add-additional-overrides=no
+// - migrating=Migration in progress see b/299366704
package android.car {
public abstract class ApiVersion<T extends android.car.ApiVersion<?>> {
diff --git a/car-lib/api/removed.txt b/car-lib/api/removed.txt
index b14f0a6..7677e45 100644
--- a/car-lib/api/removed.txt
+++ b/car-lib/api/removed.txt
@@ -1,4 +1,6 @@
// Signature format: 2.0
+// - add-additional-overrides=no
+// - migrating=Migration in progress see b/299366704
package android.car {
public final class Car {
