Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / e6c971fe014b24afee4521fc0ac21cca3b8fe745
commite6c971fe014b24afee4521fc0ac21cca3b8fe745[log] [tgz]
authorRemi NGUYEN VAN <reminv@google.com>Tue Mar 23 15:02:20 2021 +0000
committerRemi NGUYEN VAN <reminv@google.com>Mon Apr 12 09:39:17 2021 +0900
tree84923046394d487347b9ffa76e0622da01cf935d
parentf3282bd901d2d153cff0b8f8a50a911498318020 [diff]
Update allowed_deps for connectivity

All targets were prepared for connectivity modularization, and include
framework-connectivity dependencies, service-connectivity dependencies,
and interfaces with netd and dnsresolver.

Bug: 171540887
Test: m

Merged-In: I879d2260c4779f4c88c26fe1c5b6b8a93c159e40
Merged-In: I0d3771c025d3b3cd5782462fc902f92146384d63
(clean cherry-pick from downstream branch)

Change-Id: I0d3771c025d3b3cd5782462fc902f92146384d63
1 file changed
tree: 84923046394d487347b9ffa76e0622da01cf935d
  1. build/
  2. java/
  3. sdk/
  4. MODULES_OWNERS
  5. OWNERS
  6. PREUPLOAD.cfg
  7. 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.