Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 892d2fd80d620f75c820115fc42d4078f87d6ca5
commit892d2fd80d620f75c820115fc42d4078f87d6ca5[log] [tgz]
authorPaul Duffin <paulduffin@google.com>Fri Dec 16 10:01:55 2022 +0000
committerSelim Cinek <cinek@google.com>Mon Jan 16 11:12:06 2023 +0000
tree8488f8b24044860a3427673d5f015cc8beda9e16
parentbf49995d901274379f7c0f503d5ed075c6e7e7db [diff]
Added constraintlayout-core and constraintlayout-core-nodeps

Test: None
Bug: 259525483
Merged-In: I94c1fd76482036e259fa366b8e0f1ff692d621b9
Change-Id: I94c1fd76482036e259fa366b8e0f1ff692d621b9
1 file changed
tree: 8488f8b24044860a3427673d5f015cc8beda9e16
  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.