Keep all fields and methods of classes extends SystemServer

Before the change, the keep rule only keeps the class that extends
SystemServer, but if the methods/fields in the class are not used by
other entries, then the methods/fields will be removed. It will cause
issue for some service are not only used by calling the public methods
inherited from SystemServer. This change will keep all methods, and
fields in the class that extends SystemServer.

Bug: 233746531
Test: Build modules using this configuration locally, and check all
neseccary methods are kept.

Change-Id: Ia938fe8726ac8d4c1f2066f1ebca318b624e30de
1 file changed
tree: a159351d652b13efceed37c7b9713e43f903796a
  1. build/
  2. java/
  3. proguard/
  4. proto/
  5. sdk/
  6. tools/
  7. Android.bp
  8. MODULES_OWNERS
  9. OWNERS
  10. PREBUILTS_MODULE_OWNERS
  11. PREUPLOAD.cfg
  12. README.md
README.md

packages/modules/common

This project includes mainline build and other utility code. Any library code intended for use by modules should go in frameworks/libs/modules-utils instead.

java code

This project uses a single source path for java code. All java code should go in the java directory with subdirectories corresponding to the java package. Android.bp files should go alongside the java source files, and should only include java source for a single java package to encourage good code hygiene.

Tests for java code should go in the javatests directory and follow the same structure.