This goal doesn't exist anymore. The build system automatically
translates it to "sdk".
Test: m win_sdk dist && inspect out/dist/apistubs
Change-Id: Ia54e92c96ef91250351735827ab07e339fe26c15
Metalava has a feature to "enhance documentation" which is mostly based
on auto-generating documentation text based on source-retention
annotations. This is turned on automatically for doc stubs, but here
we are enabling it for module's jar stubs as well.
The point of this is to be able to replace the module source code with
module jar stub source code when generating doc stubs -- something
previously not possible because most source-retention annotations are
not present in the jar stubs.
In order for the enhancement to work properly, metalava needs to be
passed the annotation source code rather than the annotations library.
This is because of various javadoc tags controlling what documentation
is generated, e.g. @paramDoc, @returnDoc etc.
Bug: 186197911
Test: manually inspect module stub source code is enhanced
Change-Id: I3fda4cd64e49c1da33fe614c30aafd9fa0dba3b9
dist_group replaces owner and the default is going to change, set it
to the current default "android" for module java_sdk_libraries.
Bug: 186723288
Test: m checkbuild
Change-Id: Id4d20471a8106718fb1529f5c83c9ca5ffb2a569
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
