Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 018e0d0f5403ec76f2f2a1035b099014ec442f10
commit018e0d0f5403ec76f2f2a1035b099014ec442f10[log] [tgz]
authorMårten Kongstad <amhk@google.com>Tue Apr 26 07:33:51 2022 +0000
committerMårten Kongstad <amhk@google.com>Tue Apr 26 07:35:51 2022 +0000
treea567e1d91ea7943ee054f2f5a2d06a9016b14f0c
parentb1e623fd6d9871cd356d6792999af2563f055aa9 [diff]
finalize_sdk.py: add --readme option

Every time an SDK is finalized, a new version history entry should be
added to prebuilts/sdk/extensions/README.md. Introduce a new option,
--readme <msg>, to better enforce this.

Test: manual: run finalized_sdk.py, inspect README.md
Change-Id: I2257dc2bcf710bb2cb616afa9b8e3d3cb307de8e
1 file changed
tree: a567e1d91ea7943ee054f2f5a2d06a9016b14f0c
  1. build/
  2. java/
  3. proguard/
  4. proto/
  5. sdk/
  6. tools/
  7. Android.bp
  8. generate_ml_bundle.sh
  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.