joy/android_packages_modules_Connectivity
Watch
1
0
Fork
You've already forked android_packages_modules_Connectivity
 0
Code Issues Pull requests Projects Releases Wiki Activity
android_packages_modules_Co.../Tethering/common/TetheringLib/api/system-lint-baseline.txt

25 lines
1.9 KiB
Text
Raw Normal View History

Switch framework-tethering to use java_sdk_library The names of the individual modules do not quite follow the pattern that java_sdk_library uses so this temporarily sets the following: naming_scheme: "frameworks-modules" That causes java_sdk_library to use a naming scheme that matches the one used by the individual modules of this. It will be cleaned up later. Part of the purpose of the java_sdk_library is to hide the implementation code and force users of the library to depend on stubs for a well defined API. Ideally, it would allow access to the implementation in those cases where it is safe, e.g. from within the same APEX, or from tests for the implementation. Unfortunately, due to limitations in the build it does not yet have enough information to make that decision correctly which means that any code that needs to compile against the implementation is broken which would prevent us from converting the module to java_sdk_library. However, the only way to provide the additional information to allow the implementation to be correctly exposed is to convert the modules to java_sdk_library; a cycle. In order to break that cycle the java_sdk_library creates a special <module>.impl target which is used directly by tests and any other code that needs it. Once all the modules have been converted to a java_sdk_library then we can resolve the limitations in the build and remove the direct references to <module>.impl. Test: m update-api Bug: 155164730 Merged-In: If5c115f482751f9f4b5f047e9e401a18e36799ef Merged-In: Id1c2e848430c49a2da7402244814cd084f5da77c Change-Id: Id1c2e848430c49a2da7402244814cd084f5da77c
2020-05-13 12:28:49 +01:00
// Baseline format: 1.0
ActionValue: android.net.TetheringManager#ACTION_TETHER_STATE_CHANGED:
Inconsistent action value; expected `android.net.action.TETHER_STATE_CHANGED`, was `android.net.conn.TETHER_STATE_CHANGED`
ActionValue: android.net.TetheringManager#EXTRA_ACTIVE_TETHER:
Inconsistent extra value; expected `android.net.extra.ACTIVE_TETHER`, was `tetherArray`
ActionValue: android.net.TetheringManager#EXTRA_AVAILABLE_TETHER:
Inconsistent extra value; expected `android.net.extra.AVAILABLE_TETHER`, was `availableArray`
ActionValue: android.net.TetheringManager#EXTRA_ERRORED_TETHER:
Inconsistent extra value; expected `android.net.extra.ERRORED_TETHER`, was `erroredArray`
CallbackInterface: android.net.TetheringManager.StartTetheringCallback:
Callbacks must be abstract class instead of interface to enable extension in future API levels: StartTetheringCallback
CallbackInterface: android.net.TetheringManager.TetheringEventCallback:
Callbacks must be abstract class instead of interface to enable extension in future API levels: TetheringEventCallback
MissingGetterMatchingBuilder: android.net.TetheringManager.TetheringRequest.Builder#setShouldShowEntitlementUi(boolean):
android.net.TetheringManager.TetheringRequest does not declare a `shouldShowEntitlementUi()` method matching method android.net.TetheringManager.TetheringRequest.Builder.setShouldShowEntitlementUi(boolean)
MissingGetterMatchingBuilder: android.net.TetheringManager.TetheringRequest.Builder#setStaticIpv4Addresses(android.net.LinkAddress, android.net.LinkAddress):
android.net.TetheringManager.TetheringRequest does not declare a `getStaticIpv4Addresses()` method matching method android.net.TetheringManager.TetheringRequest.Builder.setStaticIpv4Addresses(android.net.LinkAddress,android.net.LinkAddress)
StaticFinalBuilder: android.net.TetheringManager.TetheringRequest.Builder:
Builder must be final: android.net.TetheringManager.TetheringRequest.Builder
Reference in a new issue Copy permalink