Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 02b056f7aad2a05f7aa3752f9ccc0aac55aa7460
commit02b056f7aad2a05f7aa3752f9ccc0aac55aa7460[log] [tgz]
authorAnton Hansson <hansson@google.com>Tue Oct 24 14:56:05 2023 +0000
committerAnton Hansson <hansson@google.com>Tue Oct 24 14:56:05 2023 +0000
treeaa0f1c1a78d2850f44e01a83ad7e96734738b601
parentfe257632190b26e77c78f2cd9c89d6741712dc6d [diff]
Expand visibility of non-updatable module defaults

This allows for use by java_sdk_libraries that are defined in
frameworks/base. More specifically, by the defaults that expand upon
these defaults.

Bug: 306806877
Test: presubmit
Change-Id: I0a52ffbc1e67a376a5ae14aa34d229c898cf0ce7
1 file changed
tree: aa0f1c1a78d2850f44e01a83ad7e96734738b601
  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.