From d61f5f7dc19576d2ccb0da8cedbd91d3ee6edeac Mon Sep 17 00:00:00 2001 From: Lorenzo Colitti Date: Wed, 20 May 2020 20:04:11 +0900 Subject: [PATCH] Suppress deprecation warnings in LegacyTypeTrackerTest. This saves dozens of warnings every time FrameworkNetTests is compiled. There is nothing we can do about those warnings because LegacyTypeTracker's reason for existence is to power deprecated APIs. Test: m FrameworksNetTests Change-Id: I4d65b0aade493e12b56a94247efbf9d1ad7bb4b9 --- tests/net/java/com/android/server/LegacyTypeTrackerTest.kt | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/tests/net/java/com/android/server/LegacyTypeTrackerTest.kt b/tests/net/java/com/android/server/LegacyTypeTrackerTest.kt index 42d4cf3c382b2..a10a3c81bc865 100644 --- a/tests/net/java/com/android/server/LegacyTypeTrackerTest.kt +++ b/tests/net/java/com/android/server/LegacyTypeTrackerTest.kt @@ -14,6 +14,11 @@ * limitations under the License. */ +// Don't warn about deprecated types anywhere in this test, because LegacyTypeTracker's very reason +// for existence is to power deprecated APIs. The annotation has to apply to the whole file because +// otherwise warnings will be generated by the imports of deprecated constants like TYPE_xxx. +@file:Suppress("DEPRECATION") + package com.android.server import android.net.ConnectivityManager.TYPE_ETHERNET