The new targets defined here ended up not being used for the purpose
I had in mind -- delete them and move the android.jar defaults back
to frameworks/base, where the only user now is.
Test: m
Merged-In: I9612c5c13ea38705ea949cf0836a790eafaf447f
Change-Id: I9612c5c13ea38705ea949cf0836a790eafaf447f
These build rules are work-in-progress libraries to produce SDK jars
based on SDK 30 but with updated mainline module stubs.
They aren't yet ready to be used, as some of the components need
tweaking (for example, the android-non-updatable prebuilt does not
have resources in it)
Migrate in the android.jar defaults from frameworks/base to avoid taking
a dependency on that repository.
Bug: 184839225
Test: m android_30_modules_current{,_system}
Change-Id: Ie696406c57f437c9c46d727311ff2956b2c8c4ea
I'm adding some other modules in a follow up, and to avoid creating
a large messy bp file, do some re-organization ahead of time.
Bug: 184839225
Bug: 185128417
Test: m
Change-Id: Icd655e680f7138582ddf34fb0e0e78e9bdd7a927
modules_current is the correct API for bootclasspath module
libraries, but it is unnecessarily restrictive for system server jars.
Test: m
Change-Id: Ic84f4c5edb4444e4c3042e19cada0caca9b16e1d
For modularization of connectivity classes, connectivity classes in
frameworks/base are planned to move to packages/modules/Connectivity.
To facilitate the work, classes are first moved to
frameworks/base/packages/Connectivity, so they can then be moved all
together with their history to packages/modules/Connectivity.
Bug: 171540887
Test: m
Change-Id: I78c7adbfe2242b1d3179d07d3cb1f0ff8a203d65
This decouples modules from frameworks/base, and this repo also has
a different automerger strategy.
Add //frameworks/base/apex:__subpackages__ to the defaults_visibility
to preserve the existing behavior.
Test: m
Merged-In: I1cf8cbbccf042a8503bf751ab057742cca357585
Change-Id: I1cf8cbbccf042a8503bf751ab057742cca357585
