Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 83b67d14c54aa261cccadb0ed86d603539dae494
commit83b67d14c54aa261cccadb0ed86d603539dae494[log] [tgz]
authorHarshit Mahajan <harshitmahajan@google.com>Wed Aug 16 13:15:07 2023 +0000
committerHarshit Mahajan <harshitmahajan@google.com>Wed Aug 16 13:15:07 2023 +0000
tree37706fe3b0304779312038edbbb5d9617f111829
parent5640e3c63a0dc9fc7b10a976206668fe728d6282 [diff]
Add v-launched-apex-module defaults for mainline modules

Bug: b/296206477
Test: presubmit

Change-Id: I032a6c92c8c1193b42d4cc888e401b8b58e4e273
1 file changed
tree: 37706fe3b0304779312038edbbb5d9617f111829
  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.