Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 816b8b6b99063748c4d71a32d3f3c50599ea597e
commit816b8b6b99063748c4d71a32d3f3c50599ea597e[log] [tgz]
authorAndrei Onea <andreionea@google.com>Thu Oct 20 15:21:45 2022 +0000
committerAndrei Onea <andreionea@google.com>Thu Nov 24 18:58:41 2022 +0000
tree4e0d60696c417b4387c31ef7d4cc6190d42e24a6
parent2f06ef137334878469ae6404d5ef458f68748d99 [diff]
Add fetch code for classpath jars

Fetch all *CLASSPATH jars and dump their data into .pb files in the temp
directory shared between the target preparer and the testcases.

Test: atest ClasspathFetcherTest
Bug: 254647172
Change-Id: I008001975ba5febbec5fec20a908b1dcc02308f6
8 files changed
tree: 4e0d60696c417b4387c31ef7d4cc6190d42e24a6
  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.