Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 4fd10a5a909d07bf3dd21c103fe10377178416f9
commit4fd10a5a909d07bf3dd21c103fe10377178416f9[log] [tgz]
authorSamiul Islam <samiul@google.com>Mon Oct 11 22:54:18 2021 +0100
committerSamiul Islam <samiul@google.com>Wed Oct 13 17:24:32 2021 +0100
treec78882b7ae78a657689c3a3d1987951d17466a49
parente3e14c0ff155104dbe0081ee2736c72eb927a116 [diff]
Add visibility to test artifacts used for apexd_test

Bug: 187444679
Test: atest ApexTestCases
Test: atest StagedInstallInternalTest
Change-Id: I5f098a7df76a165791e1d72119297ac5b8e315fe
1 file changed
tree: c78882b7ae78a657689c3a3d1987951d17466a49
  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.