Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / bec910c429123615dc0c2918d9f54320726f1886
commitbec910c429123615dc0c2918d9f54320726f1886[log] [tgz]
authorCorina <corinac@google.com>Wed Mar 30 13:36:01 2022 +0100
committerCorina Grigoras <corinac@google.com>Thu Mar 31 17:17:00 2022 +0000
tree83f90790f4ad870c97ef6853720121333a73a039
parentcbd1120d484243e967b3a603e4ea411e758f8665 [diff]
Add allowed dep

Bug: 218862369
Test: atest
Aosp-First: Pending CPs
Test-Info: atest
Previous-Platform-Support: ?
Apex-Size-Increase: minimal

Change-Id: I3809f5987f737d963ddf7024633552c3557333b4
Merged-In: I3809f5987f737d963ddf7024633552c3557333b4
1 file changed
tree: 83f90790f4ad870c97ef6853720121333a73a039
  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.