Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / bb370e35e339ba753d8ed71b558d24162891bcd6
commitbb370e35e339ba753d8ed71b558d24162891bcd6[log] [tgz]
authorAnton Hansson <hansson@google.com>Mon May 30 17:49:05 2022 +0000
committerAnton Hansson <hansson@google.com>Mon May 30 17:50:35 2022 +0000
tree3437d2c400299388590e299a02af58ce9800f0a1
parentfc0ea40e8d94a5837ff5ce50bb0f9ed90bbf65c9 [diff]
Allow modules-utils-locallog to be used in modules

Already in use by many different apexes, by depending on the source
directly.

No-Allowed-Deps-Check: build refactor

Test: m
Change-Id: Id64021afa503e3679eb3d93cc8f06c8aa5d05dd7
1 file changed
tree: 3437d2c400299388590e299a02af58ce9800f0a1
  1. build/
  2. java/
  3. proguard/
  4. proto/
  5. sdk/
  6. tools/
  7. Android.bp
  8. MODULES_OWNERS
  9. OWNERS
  10. PREBUILTS_MODULE_OWNERS
  11. PREUPLOAD.cfg
  12. 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.