Google Git
Sign in
android / platform / packages / modules / common / 5fc8511dffe2838eedde1da1418bae3d2611c03e
commit5fc8511dffe2838eedde1da1418bae3d2611c03e[log] [tgz]
authorPaul Duffin <paulduffin@google.com>Thu Sep 29 13:12:44 2022 +0100
committerPaul Duffin <paulduffin@google.com>Mon Oct 03 10:48:10 2022 +0000
treedbd875485a9da38b55ea234d115c7ab85021c273
parent2d23b0efb848f871c95d87257981b5bbaf93d659 [diff]
Add UpsideDownCake to releases that need snapshots to be built

Bug: 249769908
Test: packages/modules/common/mainline_modules_sdks.sh
Change-Id: I2b945f9db628c90b3823972787713dce39b9df75
Merged-In: I39804d89ad15109da47b5caa4a20ca2ef74b0e37
1 file changed
tree: dbd875485a9da38b55ea234d115c7ab85021c273
  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.