Add STANDALONE_SYSTEMSERVER_JARS to classpath.proto.

This is an environment variable that lists the jars that system server
loads dynamically using separate classloaders. The list is derived from
PRODUCT_STANDALONE_SYSTEM_SERVER_JARS and
PRODUCT_APEX_PRODUCT_STANDALONE_SYSTEM_SERVER_JARS in Makefile. It will
be comsumed by odrefresh to determine what jars to preopt on early boot.

Note that the variable should not end with "CLASSPATH" because the list
is not used by runtime as a classpath. It is just a colon-separated list
of jars. System server loads the jars separately with paths hardcoded in
the code.

Bug: 203198541
Test: manual - 1. Build an image.
  2. Flash the image to a device.
  3. adb shell echo \$STANDALONE_SYSTEMSERVER_JARS
  4. See the correct list of jars.
Change-Id: I5a9653c606969aaa8083e8c8daa9d48b99663790
1 file changed
tree: a9b81fda4a4b009587abcb5b32e468276200d8a6
  1. build/
  2. java/
  3. proguard/
  4. proto/
  5. sdk/
  6. tools/
  7. Android.bp
  8. generate_ml_bundle.sh
  9. MODULES_OWNERS
  10. OWNERS
  11. PREBUILTS_MODULE_OWNERS
  12. PREUPLOAD.cfg
  13. 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.