Nothing depends on these. They were only here for easy comparison
with the merged variant while we ironed out diffs.
Rename the merged variants instead of having duplicate compilation
rules.
Bug: 171029603
Test: m nothing
Change-Id: I7859589b93b861439fb1b7de084e52294da53671
Merged-In: I7859589b93b861439fb1b7de084e52294da53671
This achieves two things:
- it's been noted that non-updatable-api is a confusing term as it has
to be updated every time the API changes
- the api-review logic trigers on txt files in subdirs named 'api',
which non-updatable-api does not trigger on
I will (less urgently) try to get rid of the term "non-updatable" from
other places too, perhaps going for "non-module" or "core" as a
replacement.
Bug: 171029603
Test: m checkapi
Change-Id: I843efb4880b6caaf3872e9b0918fd710fb93d979
This achieves two things:
- it's been noted that non-updatable-api is a confusing term as it has
to be updated every time the API changes
- the api-review logic trigers on txt files in subdirs named 'api',
which non-updatable-api does not trigger on
I will (less urgently) try to get rid of the term "non-updatable" from
other places too, perhaps going for "non-module" or "core" as a
replacement.
Bug: 171029603
Test: m checkapi
Change-Id: I843efb4880b6caaf3872e9b0918fd710fb93d979
Merged-In: I843efb4880b6caaf3872e9b0918fd710fb93d979
This target existed just to track the "full" module lib API surface,
until the individual pieces had the same standards. However, now:
- the full current.txt file is available as a build target
- all the individual .txt files are API reviewed, checked against
last api, linted, and changes result on API council bug updates
The .txt files will be removed in a separate CL.
Bug: 171029603
Test: m checkapi
Change-Id: Ib8ec547871045f77fb73aa82f192b5a7767d0c33
Previously all droidstubs modules were classified as highmem. Annotate
only the huge modules as such, to allow more parallelization of lowmem
droidstubs modules.
Bug: 170701554
Test: NINJA_HIGHMEM_NUM_JOBS=3 m checkapi
Change-Id: I83ae88222110d7afe4009076e951c88a5188ca83
This makes it impossible to add new @TestApi in modules, of which
there are none right now and we don't want any going forwards, either.
Bug: 170395679
Test: m test-api-stubs-docs-check-current-api
Change-Id: I527ca7b580350372bee72b65f6596a46eab2ce04
This makes it impossible to add new @TestApi in modules, of which
there are none right now and we don't want any going forwards, either.
Bug: 170395679
Test: m test-api-stubs-docs-check-current-api
Change-Id: I527ca7b580350372bee72b65f6596a46eab2ce04
Merged-In: I527ca7b580350372bee72b65f6596a46eab2ce04
Nothing uses these outputs anymore. The compat tools have been
migrated to use a new file in I082d18fc2b8a57ea8c5941d5c955a7970ab9d860.
Bug: 158465496
Test: presubmit
Change-Id: I51a1f3f5e43092f5431358d705379cc33b60b835
Include @SystemApi APIs in the test_current stub jar, while keeping
the @TestApi and @SystemApi API txt files tracked separately.
A side-effect of this change is that string constants of @SystemApi
permissions are no longer inlined in the test api tracking, possibly
because metalava was previously incorrectly peeking at @SystemApi
whereas it is now explicitly forbidden to do so. I don't believe the
API txt change has any practical effects.
Bug: 129133308
Test: presubmit
Change-Id: I23d3c88624ee7599485c3390a0440b78bc18a0a2
Merged-In: I23d3c88624ee7599485c3390a0440b78bc18a0a2
The official API differences report is not produced from the
artifacts this rule creates, but by manually running metalava
with the right txt files.
As there are no other known users of these jdiff files, remove them
for now.
Bug: 158465496
Test: m
Change-Id: Iee9dd1a5d5543f3f629e3631c8224e6bfe4dddcb
Include @SystemApi APIs in the test_current stub jar, while keeping
the @TestApi and @SystemApi API txt files tracked separately.
A side-effect of this change is that string constants of @SystemApi
permissions are no longer inlined in the test api tracking, possibly
because metalava was previously incorrectly peeking at @SystemApi
whereas it is now explicitly forbidden to do so. I don't believe the
API txt change has any practical effects.
Bug: 129133308
Test: presubmit
Change-Id: I23d3c88624ee7599485c3390a0440b78bc18a0a2
These two were missing from some of the lists of all modules,
as they either weren't standardized or not available in the branch
where the list was first added.
Bug: 169034951
Test: m
Change-Id: I16c67ef8a433e6720953a2046c09add13a8102ed
AppSearch build file only defined a subset of the stubs and api
tracking, which prevents making progress on creating a correct "merged"
current.txt. Convert it to the standard build setup modules should use.
Implementation wise, this is a little bit special in that it's somewhere
between a module and not. The implementation library requires platform
internals to compile. The stubs do not, and we rely on this to make
the build work at all -- via impl_only_libs we compile the stubs
*without* framework-minus-apex, which allows framework-minus-apex to
depend on the stubs.
Bug: 169304493
Test: m checkapi
Change-Id: I10a331bb6df56072cb9e9ada99ae47c5446869fd
I missed this in If608be48276f0a7f76afd714656267ed379ce062, which added
last_released tracking to the other *-non-updatable APIs. See that
change for more context.
Bug: 170105267
Test: m checkapi
Change-Id: I32d09c7fc155c04295dc16028a568e3381c09e4b
This makes the build fail when APIs are removed from the (non-updatable)
framework.jar, and e.g. into a module. This is in general not safe, so
is a reasonable default. When it needs overriding (when e.g. creating
now modules), incompatibilities.txt can be used for that.
Bug: 170105267
Test: m checkapi
Change-Id: If608be48276f0a7f76afd714656267ed379ce062
This makes the build fail when APIs are removed from the (non-updatable)
framework.jar, and e.g. into a module. This is in general not safe, so
is a reasonable default. When it needs overriding (when e.g. creating
now modules), incompatibilities.txt can be used for that.
Bug: 170105267
Test: m checkapi
Change-Id: If608be48276f0a7f76afd714656267ed379ce062
Merged-In: If608be48276f0a7f76afd714656267ed379ce062
The stub libraries had a dependency to framework-internal-util which is
a collection of java static libraries whose source code is
auto-genmerated (e.g. via protoc, aidl, etc.)
The library was added as a dependency because some Java files that are
fed into the metalava for the stub code generation have references to
some of the auto-generated symbols. However, this is more than
necessary. Furthermore, that setup will create a circular dependency
when framework-internal-utils (or its transitive dependencies) have a
dependency to the stub libraries due to 'sdk_version' setting.
Fixing the problem by replacing the dependency to
framework-internal-util with a few number of libraries.
Bug: 169618843
Test: m
Change-Id: I30c953ed220e84ab295548845fff0b26e3c060b6
Bug: 168301990
Test: Built offline-sdk-docs with and without the change and
diffed them. There were some changes other than the timestamp.js
file. With these changes classes that implemented the
Object.equals(Object) method had some extra documentation that
explained that the parameter could be null. The reason for this
change is that the stubs generated with this change includes
android.annotation.Nullable whereas previously they included
androidx.annotation.Nullable. The change is a very minor
improvement over what is currently uploaded to
developer.android.com/reference so not worth backporting.
Diffed api/public/current.txt against
frameworks/base/api/current.txt and made sure that the latter was
a superset of the former and there were no differences in the area
that overlapped.
Change-Id: I3767948b4659b18b813c8eed66258af98ac4a241
This moves the android.media.audio.common, android.media.permission and
android.media.soundtrigger_middleware AIDL files to a their own
separate aidl_interface module for Java.
Previously, because of how the framework JAR is configured, those
files were automatically compiled into it and we had to disable Java
for this target, creating a discrepancy between C++ and Java, which
would require us to similarly diverge any dependent targets if we want
cross-language support.
As part of this change, we also had to switch from using the
FileDescriptor type to ParcelFileDescriptor, as this is the only type
supported outside of the framework JAR and is also the recommended
practice.
Test: Manual verification of basic soundtrigger functionality.
Change-Id: Ib65c19dd7c7f5433cfa527fa74bb61ac677f5cf5
The issue with missing resources has been fixed.
This reverts commit 9b0a74f0a3ae653954f432bf8892533aa2522015.
Bug: 161214753
Change-Id: I863e76f199f7e209dfc86a85320f394c2285e71a
Test: diff sdk artifacts before and after
