Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 55d405fb6acd7314a13a5b0252a562c777f3cd24
commit55d405fb6acd7314a13a5b0252a562c777f3cd24[log] [tgz]
authorHenri Chataing <henrichataing@google.com>Tue Oct 31 17:44:00 2023 +0000
committerHenri Chataing <henrichataing@google.com>Tue Oct 31 23:07:34 2023 +0000
treed3f75064658890461ec909657512fb864ab996f3
parent2f9229ac85c886052c2a739f50d62f64067a92a5 [diff]
Add pdl-runtime to allowed_deps.txt

Apex-Size-Increase: 0B
Previous-Platform-Support: yes
Aosp-First: yes
Test-Info: unit tests
Bug: 306901204
Test: TreeHugger
Change-Id: I3e59d5656cd98c6a7d61d6391cda404edd1d242a
1 file changed
tree: d3f75064658890461ec909657512fb864ab996f3
  1. build/
  2. java/
  3. javatests/
  4. proguard/
  5. proto/
  6. sdk/
  7. tools/
  8. Android.bp
  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.