Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 19f4e56db6bf49507263ebef0768c546e3498d67
commit19f4e56db6bf49507263ebef0768c546e3498d67[log] [tgz]
authorDave Mankoff <mankoff@google.com>Wed Oct 25 16:42:22 2023 +0000
committerDave Mankoff <mankoff@google.com>Wed Oct 25 16:44:13 2023 +0000
treeabfa682948b5933e5da10d0b5822e7ce7e7f5e39
parentea7b36343baf00aa3db16802d27601e4f29f55bd [diff]
Apex-Size-Increase: ~100KB for internal app.
Previous-Platform-Support: N/A. Aconfig is supported starting with 35
Change-Id: I247bae7e4c1e30476f9cc933facfcc6cb76196de
Aosp-First: No. For an internal app.
Test-Info: Adding tests to app to ensure it always builds.
Bug: 307526764
Test: manually built and run.
1 file changed
tree: abfa682948b5933e5da10d0b5822e7ce7e7f5e39
  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.