diff options
| author | 2024-09-30 16:13:45 +0100 | |
|---|---|---|
| committer | 2024-10-07 13:37:01 +0100 | |
| commit | 9b56546fa31a9c613a51f0e7c4f0e98f021af597 (patch) | |
| tree | 7c23e9efe25090c2ec97a72a0010cf48304e11b4 /apex | |
| parent | 8c92c912612dd8aec64ed6f632a6e545ea6e5c72 (diff) | |
Add missing Javadoc dependency to `framework-mediaprovider`
The `MediaStore.java` file imports
`android.media.ApplicationMediaCapabilities` and references it from
the Javadoc of some of `EXTRA_ACCEPT_ORIGINAL_MEDIA_FORMAT` field.
Strictly speaking, that class should have been imported in the stubs
to ensure that the references in the Javadoc could be correctly
resolved. However, due to some inaccurate handling of imports in
Metalava the import was not added to the stubs.
The handling of imports in Metalava will be improved and so the class
will be correctly imported. However, that would lead to a compile time
failure because `ApplicationMediaCapabilities` is not on the classpath
when compiling the stubs. This change avoids that by adding the missing
dependency in preparation for the Metalava changes.
Bug: 371955471
Test: m droid
tools/metalava/scripts/gather-android-metalava-artifacts.py before
tools/metalava/scripts/gather-android-metalava-artifacts.py after
meld before after
Change-Id: I00b967ae1d015a39c9a7a0b073786ced291784fb
Diffstat (limited to 'apex')
| -rw-r--r-- | apex/framework/Android.bp | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/apex/framework/Android.bp b/apex/framework/Android.bp index 1c13ff7ea..17b2829e3 100644 --- a/apex/framework/Android.bp +++ b/apex/framework/Android.bp @@ -38,6 +38,11 @@ java_sdk_library { installable: true, + stub_only_libs: [ + // Needed for javadoc references. + "framework-media.stubs.module_lib", + ], + libs: [ "androidx.annotation_annotation", "framework-media.stubs.module_lib", |