Add non-updatable-framework-module-defaults

These java_defaults are useful for the java_sdk_libraries that belong to
non-updatable APEXes.

Defaults are very similar to the framework-module-defaults, the main
differences are:

1. non-updatable-framework-module-defaults enables @TestApi surface
2. non-updatable-framework-module-defaults doesn't enable
   strict_updatability_linting

Allow list of the users of these new defaults is controlled by the
defaults_visibility, so far only Virtualization apex is allowed to use
non-updatable-framework-module-defaults.

Bug: 243512044
Test: m
Change-Id: Id06fb6fc43be78c1bd92c29e7593df89e412f598
1 file changed
tree: caf54155aac119c8cdbce713631f048198d644f0
  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.