Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / b6bc4b74a51274491fc62d7107a15c98994e97f1
commitb6bc4b74a51274491fc62d7107a15c98994e97f1[log] [tgz]
authorGurpreet Singh <gurpreetgs@google.com>Wed Mar 02 16:34:58 2022 +0000
committerGurpreet Singh <gurpreetgs@google.com>Thu Mar 03 13:12:39 2022 +0000
treedc247a46e4b8babe3f4284994743bf5cf11354bf
parentad786e72e5af3259c9b6e46c3f9f60a61566383d [diff]
Adding apex_defaults to provide common parameters for Q, R, S and T.

This CL is adding the apex_defaults modules to provide common
parameters for the releases corresponding to Q, R, S and T.

These defaults servers as a common place to add properties which should
affect all mainline modules.

Bug: 172589606
Test: USE_RBE=true m
Since there are no runtime changes, successful code build is enough for
testing.

Change-Id: Ib7aeff510712b047df44bc1d16570c5a48d24e11
1 file changed
tree: dc247a46e4b8babe3f4284994743bf5cf11354bf
  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.