Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 8e3a96f3bcb4602ab72271d32548a15ea38ac524
commit8e3a96f3bcb4602ab72271d32548a15ea38ac524[log] [tgz]
authorAnvesh Renikindi <renikindi@google.com>Thu Nov 30 19:15:55 2023 +0000
committerAnvesh Renikindi <renikindi@google.com>Thu Dec 07 16:29:23 2023 +0000
tree27be24a479af059153f0bf2dc049d4aaa1122864
parent789b63dca04c810219011ba150cebab66afa25c9 [diff]
minsdk version upgrade

Change-Id: I9ca8a44af788a253af12e179070413db09987f7a
Merged-In: I0f1b47cbdfd53d4689a54a53707f0724ba52bbdb
Merged-In: I3796b792678b7f2dd07b8a213491bb0847855dd4
Test: Android JUnit Test
Aosp-First: No(Internal submitted)
Previous-Platform-Support:yes
1 file changed
tree: 27be24a479af059153f0bf2dc049d4aaa1122864
  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.