Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 478c28bbc8aef1f5c621b79f28ff0ddb9557e317
commit478c28bbc8aef1f5c621b79f28ff0ddb9557e317[log] [tgz]
authorJane Ha <hatrang@google.com>Tue Apr 18 14:49:31 2023 -0700
committerJane Ha <hatrang@google.com>Tue Apr 18 14:49:31 2023 -0700
treea3763c3695fd1adf69d2cbe0009378f88b2dfb39
parentdd5df65858b569a81de3945004c5c550576aa053 [diff]
Ignore-AOSP-First: merge conflict. see aosp/2545210

adding the following targets to apex allowlist
car-rotary-lib-no-overlayable
car-rotary-lib-overlayable-resources

Test-Info: atest CarUILibUnitTest
Previous-Platform-Support: Yes
Aosp-First: Yes
Apex-Size-Increase: No

Bug: 266871187
Test: m car-rotary-lib-no-overlayable
Change-Id: Iccfac35e78219d499506ac0886f1872a7d70f846
1 file changed
tree: a3763c3695fd1adf69d2cbe0009378f88b2dfb39
  1. build/
  2. java/
  3. javatests/
  4. proguard/
  5. proto/
  6. sdk/
  7. tools/
  8. Android.bp
  9. generate_ml_bundle.sh
  10. MODULES_OWNERS
  11. OWNERS
  12. PREBUILTS_MODULE_OWNERS
  13. PREUPLOAD.cfg
  14. 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.