Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 3892f652fb2941181f20f7bbc6e62519b71cd8c7
commit3892f652fb2941181f20f7bbc6e62519b71cd8c7[log] [tgz]
authorAnton Hansson <hansson@google.com>Mon Oct 23 14:38:19 2023 +0000
committerAnton Hansson <hansson@google.com>Fri Oct 27 12:22:41 2023 +0000
tree470a96112311c3c1cffc8bc9f7d733b507950048
parent5f422239a820a9e93f9ba0ee3a071e7b5f02f602 [diff]
Inline droiddoc options

Bug: 306806877
Test: presubmit
Change-Id: Ifcc25c449ee39e53ce42b2772b4b65823626ab38
1 file changed
tree: 470a96112311c3c1cffc8bc9f7d733b507950048
  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.