Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / a45a8d27a73430624c5dda25fd5fc76a124d9258
commita45a8d27a73430624c5dda25fd5fc76a124d9258[log] [tgz]
authorAnvesh Renikindi <renikindi@google.com>Thu Mar 30 19:49:11 2023 +0000
committerAnvesh Renikindi <renikindi@google.com>Fri Mar 31 22:18:48 2023 +0000
tree41ce214fa30aac4b8ade87ac638b7f81ec6bee3f
parent8ad95c878f47260c80d9579531bb3a2da6414bb6 [diff]
Added deps


Bug: 275397900
Change-Id: I41dbcbfa53bfd9cc5b63c988c01053638774ecc8
Merged-In: I41dbcbfa53bfd9cc5b63c988c01053638774ecc8
Test: None
Aosp-First: No(Internal )
Apex-Size-Increase:6.91kb
Previous-Platform-Support:Yes
Test-Info: Android JUnit Test
1 file changed
tree: 41ce214fa30aac4b8ade87ac638b7f81ec6bee3f
  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.