Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 88cc4d6af5cbb10593d6ecca8a0afca3cc2b5cdf
commit88cc4d6af5cbb10593d6ecca8a0afca3cc2b5cdf[log] [tgz]
authorDario Freni <dariofreni@google.com>Fri Nov 03 13:22:32 2023 +0000
committerDario Freni <dariofreni@google.com>Fri Nov 03 13:22:37 2023 +0000
tree237be299d683207d96f0bdf99cae5d85ff68d737
parent60aa1a35e93f8d32335db511d37c21f9be5e4a84 [diff]
Assign default bug component to targets in this directory.

This CL is being created to improve the test attribution in android. It has been 
found that the tests owned by this OWNERS are not not being attributed to a
buganiser component.
This is part of a bigger effort to attribute all of the aosp code. 

If you think that the buganiser component is not correct please update
this CL with correct component and drop a +2.
We will use the updated component and merge the CL

Bug: 309090038
Change-Id: Ic8ee48ae6e58cffcd4c02e37dc9346d4f90316ce
Test: N/A
1 file changed
tree: 237be299d683207d96f0bdf99cae5d85ff68d737
  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.