Expand visibility of sdkinfo proto

Embed it into all the modules that are part of the updatable API
surface, ahead of actually introducing any new API levels with
requirements on these modules.

Also rename to current_sdkinfo for clarity.

Bug: 188787081
Test: Inspect apex files
Change-Id: I93ba55f1c1b4f60f36a26a2397088a5471eef850
1 file changed
tree: f2cb502516f4cf756de71a55a5c26a55f793c5af
  1. build/
  2. java/
  3. proto/
  4. sdk/
  5. tools/
  6. Android.bp
  7. generate_ml_bundle.sh
  8. MODULES_OWNERS
  9. OWNERS
  10. PREUPLOAD.cfg
  11. 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.