DO NOT MERGE: Empty commit unique to tm-mainline-prod

Changes to packages/modules/common in AOSP/master automatically merge
into tm-mainline-prod and down through the normal merge path to
git_master. Sometimes, however it is necessary to exclude changes from
merging into tm-mainline-prod, e.g. adding modules that are new to
UDC. This change is being added to create a Change-Id that can be added
into Merged-In to prevent that. It sets DO NOT MERGE so that this
change is not merged into git_master.

Ignore-AOSP-First: see above
Change-Id: Ie3a4f694dabee4224444b1aa6da0a0048b69fc75
tree: 2ac5921591da0145a4bdbf336ddf97cd4cf4abdd
  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.