Apps making calls into the system server may end up persisting internal state or making security decisions based on the perceived success or failure of a call, or any default values returned. For this reason, we want to strongly throw when there was trouble with the transaction. The rethrowFromSystemServer() method is the best-practice way of doing this correctly, so that we don't clutter logs with misleading stack traces, and this checker verifies that best-practice is used. Disable this check on managers that we know are hosted outside the system process. Bug: 155703208 Test: ./build/soong/soong_ui.bash --make-mode framework-minus-apex services RUN_ERROR_PRONE=true Exempt-From-Owner-Approval: trivial annotations Change-Id: I04b4daf7c92251a14bcc3ebb1e18cd00f6a7f283
24 lines
436 B
Plaintext
24 lines
436 B
Plaintext
|
|
java_plugin {
|
|
name: "error_prone_android_framework",
|
|
|
|
static_libs: [
|
|
"error_prone_android_framework_lib",
|
|
],
|
|
}
|
|
|
|
java_library_host {
|
|
name: "error_prone_android_framework_lib",
|
|
|
|
srcs: ["java/**/*.java"],
|
|
|
|
static_libs: [
|
|
"//external/error_prone:error_prone_core",
|
|
"//external/dagger2:dagger2-auto-service",
|
|
],
|
|
|
|
plugins: [
|
|
"//external/dagger2:dagger2-auto-service",
|
|
],
|
|
}
|