Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / ec62d6521e76544cb14cc1fa2d5fe5e4fb509dc7
commitec62d6521e76544cb14cc1fa2d5fe5e4fb509dc7[log] [tgz]
authorSaeid Farivar Asanjan <farivar@google.com>Mon Dec 19 19:06:09 2022 +0000
committerSaeid Farivar Asanjan <farivar@google.com>Wed Jan 11 22:18:55 2023 +0000
tree5cee4939285dc696b9401d912e0bf5aabbc7ff64
parent342ecef2f999a5082dfd797d68ff00c3555bf20b [diff]
Ignore-AOSP-First: merge conflict. see aosp/2364085

Adding a new target to car-ui-lib that doesn't include overlayable.xml

Test-Info: N/A
Previous-Platform-Support: Yes
Aosp-First: Yes
Apex-Size-Increase: No

Bug: 239735198
Test: N/A
Change-Id: I48c8e25bdb0f5613388be9c86ea5eb8b866a81a0
Merged-In: I48c8e25bdb0f5613388be9c86ea5eb8b866a81a0
Merged-In: I7406d638fef78074bac641a04c90fa214da33a76
1 file changed
tree: 5cee4939285dc696b9401d912e0bf5aabbc7ff64
  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.