Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / c0af2d059da10b3a8908b5d9ed8e62795ec1e367
commitc0af2d059da10b3a8908b5d9ed8e62795ec1e367[log] [tgz]
authorPaul Duffin <paulduffin@google.com>Fri Dec 16 10:01:55 2022 +0000
committerPaul Duffin <paulduffin@google.com>Fri Dec 16 10:01:55 2022 +0000
tree28fd43d41a7a48e565d0632f635131b72bbe557c
parentb79362fa534fa27650e10a96b384fffbf7f3e108 [diff]
Added constraintlayout-core and constraintlayout-core-nodeps

Change-Id: I94c1fd76482036e259fa366b8e0f1ff692d621b9
Test: None
Aosp-First:
Apex-Size-Increase:
Previous-Platform-Support:
Test-Info:
1 file changed
tree: 28fd43d41a7a48e565d0632f635131b72bbe557c
  1. build/
  2. java/
  3. javatests/
  4. proguard/
  5. proto/
  6. sdk/
  7. tools/
  8. Android.bp
  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.