Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 9e865a2f34726fe86b90fc08ca82251c89218275
commit9e865a2f34726fe86b90fc08ca82251c89218275[log] [tgz]
authorAnton Hansson <hansson@google.com>Mon Oct 23 14:36:51 2023 +0000
committerAnton Hansson <hansson@google.com>Mon Oct 23 14:36:51 2023 +0000
tree5e7ffc6ddf1205905bfb486c5ddbcb5ffb47c9a0
parentea470a65b9f7554f996ac926681ae2f447b4ed9d [diff]
Delete old defaults

Dead code.

Test: presubmit
Change-Id: I2185ade875341ed4532931311b94e403f9770bfe
1 file changed
tree: 5e7ffc6ddf1205905bfb486c5ddbcb5ffb47c9a0
  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.