Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 4239d7b57b851c028de6c8146aae328bb6ec762e
commit4239d7b57b851c028de6c8146aae328bb6ec762e[log] [tgz]
authorsatayev <satayev@google.com>Tue May 18 19:32:02 2021 +0100
committersatayev <satayev@google.com>Tue May 18 19:32:02 2021 +0100
tree443d12609cbbb60e2a0f870b1f2a60500811f896
parentbb9ba93a7dced2d27699ae989d155c0b9374e659 [diff]
Use absolute paths in classpaths.proto.

The intention before was to use relative paths to a partition where a
config is defined. However, jars in /system_ext partition are planned to
be declared in /system's classpaths.proto config.

Bug: 180105615
Test: atest derive_classpath_test
Change-Id: I4f955303631ba84b47d6e287c7b4f59c1e198da1
1 file changed
tree: 443d12609cbbb60e2a0f870b1f2a60500811f896
  1. build/
  2. java/
  3. proto/
  4. sdk/
  5. tools/
  6. Android.bp
  7. MODULES_OWNERS
  8. OWNERS
  9. PREUPLOAD.cfg
  10. 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.