Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 5053a09f4f0b0adfe90dead96903aaf5af67724e
commit5053a09f4f0b0adfe90dead96903aaf5af67724e[log] [tgz]
authorAnton Hansson <hansson@google.com>Fri Jan 28 13:22:10 2022 +0000
committerAnton Hansson <hansson@google.com>Fri Jan 28 13:22:10 2022 +0000
treee8d387d2554f782e6dd4a70dc752306bfa9f0b93
parentf098c2264967756360fe7ac13141f61a385367e4 [diff]
Update visibility to impl jars

The "merged" impl jar definition is moving to a new directory.

Bug: 169103987
Test: m nothing
Change-Id: I8eee60259f00fed281f0c579b12e9e99a4f6612e
1 file changed
tree: e8d387d2554f782e6dd4a70dc752306bfa9f0b93
  1. build/
  2. java/
  3. javatests/
  4. proguard/
  5. proto/
  6. sdk/
  7. tools/
  8. Android.bp
  9. generate_ml_bundle.sh
  10. MODULES_OWNERS
  11. OWNERS
  12. PREBUILTS_MODULE_OWNERS
  13. PREUPLOAD.cfg
  14. 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.