Add ExoPlayer-related targets to allowed_deps

Bug: 203391388
Test: m
Test-Info: No behavior change. The media apex already
depends on ExoPlayer targets.
Apex-Size-Increase: 0. Dependency already exists in the media apex.
Previous-Platform-Support: No behavior change. The media apex already
depends on ExoPlayer targets.
Aosp-First: Yes.
Change-Id: Iaa097dab34800549f8d0aee425c1de3d34cd4317

Change-Id: Id0399050a44a16f03fb5f99c48f3295ecee18e41
1 file changed
tree: a786202c2c9a775305c9ccec536682aa880de255
  1. build/
  2. java/
  3. proguard/
  4. proto/
  5. sdk/
  6. tools/
  7. Android.bp
  8. generate_ml_bundle.sh
  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.