Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / a4ca84b51979a2922adbe713c7c11c03a5d7a820
commita4ca84b51979a2922adbe713c7c11c03a5d7a820[log] [tgz]
authorAnvesh Renikindi <renikindi@google.com>Tue Jun 20 16:16:28 2023 +0000
committerAnvesh Renikindi <renikindi@google.com>Tue Jun 20 16:31:04 2023 +0000
tree8eb44a1bb2bf84f31dee1bc324d3f84a4f620e09
parent4eb075a142185f8ed1baad84e6f759e07e89b6f9 [diff]
dependency version updated

Change-Id: Id251eda67ca2a9b3f7e38111ad348d95f4abc2f5
Test: Treehugger
Aosp-First: No
Apex-Size-Increase:
Previous-Platform-Support: No
Test-Info:Android JUnit Test
ignore-AOSP-First: Merge conflict resolution
1 file changed
tree: 8eb44a1bb2bf84f31dee1bc324d3f84a4f620e09
  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.