Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / b853f31f284bb8c1d1eaba7aefe568cd9e5b1565
commitb853f31f284bb8c1d1eaba7aefe568cd9e5b1565[log] [tgz]
authorAnton Hansson <hansson@google.com>Wed Apr 06 12:06:06 2022 +0100
committerAnton Hansson <hansson@google.com>Thu Apr 07 11:01:05 2022 +0100
treee1334c2b67330e5ef84160d496b0770279abcdf7
parent53c913e727360e6d85440dc9d1db6405efea08c6 [diff]
Make finalization script also copy compat txt files

We need to duplicate the txt files in an additional location in
order for compatibility tracking to work. Make the script copy them
to that location as well.

Test: run finalize.py for version 2
Change-Id: I31848ad3f5cd0c264c68b4cdd874c93615de600a
1 file changed
tree: e1334c2b67330e5ef84160d496b0770279abcdf7
  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.