Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 70835ee13d62e0d89ff726665126a3ecf12eb1d0
commit70835ee13d62e0d89ff726665126a3ecf12eb1d0[log] [tgz]
authorAndrew Vuong <akvuong@google.com>Fri Nov 11 22:44:29 2022 +0000
committerAndrew Vuong <akvuong@google.com>Fri Nov 11 22:46:56 2022 +0000
treebd295913adbdef4b8c25ce4e000671ae011d9951
parent7aa68307e4d3946af0c937da2f159218644eb679 [diff]
Add flatbuffer-java to allowed_deps

Apex-Size-Increase: 4KB
Previous-Platform-Support: None
Aosp-First: yes
Test-Info: Library has its own set of manual tests by running external/flatbuffers/tests/JavaTests.sh. Follow-up to add android tests bug: 258833030
Test: external/flatbuffers/tests/JavaTests.sh and m
Change-Id: I33f26cf26b1fd4e3268153b30c50976a006ec0d9
1 file changed
tree: bd295913adbdef4b8c25ce4e000671ae011d9951
  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.