DO NOT MERGE Add last finalized version to metadata file.

This CL builds the .latest.version target which contains the last
finalized version. This version is read and populated inside the
metadata file.
The CL also verifies whether all the java sdk libraries under a module,
which has been finalized atleast once, have the same extension version.

Bug: 242316893
Test: atest --host mainline_modules_sdks_test --no-bazel-mode
(cherry picked from https://android-review.googlesource.com/q/commit:7719a9790afb89cca5d7b342865b284d4bc0e79a)
Merged-In: I94acf448b25d76c45a4bfd3d54fc276e2f01c7cc
Change-Id: I94acf448b25d76c45a4bfd3d54fc276e2f01c7cc
2 files changed
tree: 268a88eaf2d47012e342b270bbbbe04bcc809f55
  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.