diff options
| author | Lorenzo Colitti <lorenzo@google.com> | 2015-07-29 11:41:21 +0900 |
|---|---|---|
| committer | Lorenzo Colitti <lorenzo@google.com> | 2015-07-31 11:08:27 +0900 |
| commit | ffc42b0b7be29ee4118e0515d5ab024927bcb8ca (patch) | |
| tree | 2101af35baee3797ce8542187ff87114f1265c72 /tools/aapt2/java/JavaClassGenerator_test.cpp | |
| parent | 5db4cc8fee8b919b5f62f222af92a4e995ca6a70 (diff) | |
Stop supporting legacy ConnectivityManager routing methods in M.
The methods startUsingNetworkFeature, stopUsingNetworkFeature and
requestRouteToHost were @removed in all the M preview builds, but
internal and external developers have noted that this imposes
additional burden for applications that need to work across
multiple platform versions because it causes compile-time errors.
We switched from @removed back to @deprecated to avoid these
problems. In order to effectively deprecate these methods, which
are error-prone and insecure, make them throw
UnsupportedOperationException if the app's target SDK is M or
above.
Because there are still one or two places in system code that use
these APIs, exempt Process.SYSTEM_UID and the OMA-DM client from
the check for now.
Bug: 22728205
Change-Id: I790bd32f3aa8067cbb625962a209bb9232f4b58c
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions