Age | Commit message (Collapse) | Author |
|
Previously, this used `AnnotationAttribute.value` but that has just
been renamed to `legacyValue`.
Bug: 354633349
Test: m extract-flagged-apis
Change-Id: Iaaee754c41fedd16f8c9432a21ec8339025c0a03
|
|
Bug: 385190204
Merged-In: Ibc80f09d54bec2c83814874d94a8f8eb22b5075f
Change-Id: If7779ae57fd91631d08bd8af5434c2ddd963aad7
|
|
|
|
|
|
While the `api_surface` property on `java_api_library` does not appear
to be used it, along with the `api_surface` property on `droidstubs`
will eventually be passed down to Metalava and will reference an
API surface defined in the `build/soong/java/metalava/main-config.xml`.
That means that the values will need to be consistent.
The `droidstubs` `api_surface` property is set by `java_sdk_library` to
be the name of an `apiScope` which uses `-` as separator not `_`. So,
it is `module-lib` not `module_lib` and `system-server` not
`system_server`. This change fixes the explicitly specified
`api_surface` properties that use `_` instead of `-`.
Bug: 391554590
Test: m checkapi
Change-Id: If23af2717148c3ea15432a1fbce2c06c46c280ce
|
|
Previously, `api-versions-jars-dir` contained `android.jar` files that
were consumed by Metalava when generating `api-versions.xml` files.
However, they are no longer used as those jars were copied into
`sdk_dir` by https://r.android.com/3454200 so `api-versions-jars-dir`
is no longer needed in `api_versions_base_defaults`.
Bug: 390113278
Test: # Before applying this change run:
tools/metalava/scripts/gather-android-metalava-artifacts.py before
# After applying this change run:
tools/metalava/scripts/gather-android-metalava-artifacts.py after
# Make sure that there are no differences.
meld before after
Change-Id: I4f04b81bfcddfb1c8b6ffb46d72b21a9d530f4ed
|
|
added AndroidLibraryDependencyInfo.
Bug: 377723687
Test: Unit tests and compare the ninja and mk files generated.
Change-Id: Iad4013d3212e8f575dd55bcfec0e2b659ae0d8db
|
|
Bug: 377723687
Test: Unit tests and compare the ninja and mk files generated.
Change-Id: I6fe92d788c9bbbe3b5b476d61c94e1105d1859b0
|
|
Previously, the previously released APIs were not passed when generated
`framework-doc-stubs` and `framework-doc-system-stubs`. That meant that
flagged APIs that were reverted would be removed even if they had
previously been released. This change fixes that by passing the
previously released API.
Bug: 379918901
Test: m framework-doc-stubs framework-doc-system-stubs
# Before this change they did not included ApplicationStartInfo
# After this change they both did and it was correctly tagged
# with @apiSince 35.
Change-Id: I2d02874d32fd62d166d66a66d8f72eed9f657511
|
|
After moving the code to mainline module, all interactions from
platform should be via APIs or relevant util classes cloned and
jarjar'd within the module.
This change moves such usages to existing APIs or makes a module-utils
copy of such classes to be used independantly in the module.
Flag: build.release_ondevice_intelligence_module
Bug: 376427781
Change-Id: I5bc5fa5b7e2e2ba2899b4cbba536103d66a6aa19
|
|
This will allow us to use the HealthFitness APIs across the framework,
most immediately for permissions.
Bug: 378992337
Change-Id: Iccd7c8efdff68e7d26d8f16d02ab361788cd6fda
Flag: EXEMPT DOCS_ONLY
Test: m framework-doc-system-stubs
|
|
Enables a lint that forces useing @FlaggedApi(..Flags.FLAG_FOO) instead
of @FlaggedApi("...FLAG_FOO"). This avoids the potential for typos
causing APIs to not ship as intended.
Bug: 322505144
Test: make checkapi
Flag: EXEMPT lint only
Change-Id: I3a78d918a38927b74c68a216cebf4b5bb692cbfa
|
|
main am: bfb3ed2149 am: 2c8c4fa5d2
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3342398
Change-Id: I57348dfb755982a4dfba4e2a7ce5232e8e62edb2
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
|
|
main am: d4e030c997 am: 77f1143bfc
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3342493
Change-Id: I786c2cb02f872f390e715b5d5f78648556fbd4af
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
This change modifies the dependency graph of framework-doc-stubs to
depend on the exportable stub source jar of the mainline modules,
so that the flagged apis symbols are not elided.
Test: m doc dist && unzip -l out/dist/offline-sdk-docs-docs.zip | grep "android/configinfrastructure/aconfig"
Bug: 377585897
Change-Id: I2de643c27417a0ccb21016a3bc495127f3a30f81
|
|
Previously, the `frameworks-base-api*-current-compat` modules would
perform a compatibility check between the latest released API
defined within multiple signature files and the current API
defined within a single signature file. That breaks on the latest
version of Metalava which has some more checks to ensure that the
API surfaces being compared are compatible.
Currently, the checks are heuristic based and essentially compare the
number of signature files for each API to catch comparing say public
API with one file against system API defined in two files (public +
system delta). This change works around the problem by merging the
files for the latest previously released API into a single file just as
is already done for the current API.
Longer term the signature files will contain information about which
API they belong to which will allow Metalava to make a much more
meaningful check at which point the affected modules can be simplified.
Bug: 374096206
Test: m checkapi
Change-Id: I934e7ac664b6b7fc9150a14b0787c0e706ccc3cd
|
|
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3282890
Change-Id: I4eeedd784df7eb5f5aedbbc881840877be544802
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
This is a prepartion CL to move VCN to its own libraries and
eventually migrate it from the non-updatable platform to Tethering
module.
This CL creates a new VCN directory with an empty java_sdk_library
and an empty java_library. In followup CLs, VCN source code will
be migrated to this VCN folder. VCN framework code and system
server code will be built into the two libraries.
Bug: 369703242
Test: build and boot
Flag: EXEMPT create new empty libraries; no functional change
Change-Id: I0f2e02771ac81a3d3fd588a6199be888ae299e52
|
|
Creating new jar "framework-platformcrashrecovery".
This would separate all the apis to a different sdk library while still
being part of core platform.
This jar is behind release_crashrecovery_module flag which also controls enabling CrashRecovery module apex.
Based on the flag only one of platformcrashrecovery jar or CrashRecovery Apex will be used.
So essentially on device if release_crashrecovery_module flag is
1. true: CrashRecovery Apex is present, this jar is not used
2. false: CrashRecovery Apex is not used, this jar is present
Bug: 289203818
Test: Jar is present in Bootclasspath on device
Test: ExplcitHealthCheckService registered on device
Flag: build.release_crashrecovery_module
Change-Id: I4696e74a1ba236614398b48a6d7145777079286b
|
|
When adding a dependencies, if the variants don't match, but the
dependency only has 1 variant anyways, soong will always use that
variant. This makes it hard to add new variants to soong, because the
1-variant fallback stops being used and you start getting missing
variant errors. Make changes to bp files such that all dependencies
correctly specify the variant to use.
Bug: 372091092
Flag: EXEMPT refactor
Test: m nothing
Change-Id: I305d9a549fc132c3d14f56eae1abbac1b9defd10
|
|
Currently, adding depedencies will use the only variant of a module
if only 1 variant exists. Otherwise, the variations of the two modules
+ the variations explicitly requested must match. The 1-variant
fallback causes issues for incremental soong, so remove reliances on it.
Bug: 372091092
Test: m nothing --no-skip-soong-tests
Change-Id: I778d1d8d67e9d0ccc3432f12e50d15c174b5dbf5
|
|
This allows simpler module definition and removal of
`exclude_static_libs` property from java modules
Test: m nothing --no-skip-soong-tests && ensure no diff in out/build-<product>.ninja file
Bug: 368127911
Change-Id: Iddcc6cc6284e0f85aca4aef208ce59dacb28ce5f
|
|
|
|
The module was enabled to build with from-text stub, but it was
accidentally configured to always build with from-source stubs with
aosp/3205867. This change re-enables from-text stub building for system
server stubs by creating a new build target
`android-non-updatable.stubs.system_server`, which is responsible for
from-text vs from-source toggling.
Test: CI
Flag: EXEMPT bug fix
Bug: 368048922
Change-Id: I6dbe222a416311a5194da60fd071334473a19384
|
|
Bug: 364930449
Test: compiles
Change-Id: Idb29e2fbd092cb606e0bc06a39c01cbf7ed8d567
|
|
|
|
|
|
Bug: 359548801
Test: presubmit and m framework-photopicker
Change-Id: I0429bb576f6cfc80c45debcc6ba4fe1851e9b99e
Merged-In: I0429bb576f6cfc80c45debcc6ba4fe1851e9b99e
|
|
Load hooks are very early, when trying to change the configuration
for certain modules in the build, we can't read the configuration
this early.
Bug: 362579941
Test: m nothing --no-skip-soong-tests
Change-Id: I08252aa42a92498f90863522d8eba243cd035ffc
|
|
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3216070
Change-Id: I8c40b853f65915888b757730faad7703e1ad209f
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
Now that androidx is using these more for SDK sandbox and usage
of stable AIDL is generally on the rise, go ahead and mark all
platform Parcelables as stable.
This is okay because all apps will share their definition from the
common BCP. If this is ever used on Parcelables not on the common
BCP, that may cause version mismatch and break usage of stable
AIDL that uses these interfaces.
Bug: 258850063
Test: build
Change-Id: Iba43040beda379f0735adf1af319a1dbfce99447
|
|
into main am: 28501b72b7
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3205867
Change-Id: I9aefb2d07bbb300af5fc4840bc2e58533d60e084
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
into main am: 6360982601
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3207399
Change-Id: I1efce35d6799f248978e666f1e09cdb812977db0
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
into main am: 43d59c5393
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/2982300
Change-Id: Iab69cb1ddf0838cf08e1f9b1c4b7e310ee7f9bd4
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
Revert submission 3207397-revert-2982300-java_api_library_non_sdk-FIKZOSARQI
Reason for revert: Post submit build breakage culprit fixed
Reverted changes: /q/submissionid:3207397-revert-2982300-java_api_library_non_sdk-FIKZOSARQI
Change-Id: Ie4741daf508c7cc9c6688091d44658bfb76df6b1
|
|
Revert submission 2982300-java_api_library_non_sdk
Reason for revert: DroidMonitor: Potential culprit for b/357648959 - verifying through ABTD before revert submission. This is part of the standard investigation process, and does not mean your CL will be reverted.
Reverted changes: /q/submissionid:2982300-java_api_library_non_sdk
Change-Id: I4224efbb47dc5ecf9afd7e3c9cd00b59a6c337ae
|
|
The toggle between from-text and from-source stubs are made within
java_sdk_library level stubs, and they no longer depend on the full api
surface java_api_library modules. Therefore, these can be safely
removed.
This change also rename android_*_stubs_current.from-source to
android_*_stubs_current, and remove the full api surface modules that
are currently generated from api.go.
Test: ENABLE_HIDDENAPI_FLAGS=true m
Bug: 327507877
Change-Id: If1f081693c7380e2ed5b5d4a1a7f7365ef1770ca
|
|
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3184524
Change-Id: Ifd16e2c08f928898de7d71bd196cb4714300305d
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
|
|
This change removes the combined_apis_defaults module type, given that
combined_apis module type is not defaultable as it creates a default
module in its module factory. The only usage of this module type has
been removed with https://r.android.com/3184819 .
Test: m nothing --no-skip-soong-tests
Bug: 349800749
Change-Id: Ib78eb965124b2c80e871b1bc022011843ebaab9a
|
|
main am: 9891943a11
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3184819
Change-Id: I93721cb915a62c838793c8c71afa00ebd7983943
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
Use soong select variable instead of combined_api_defaults which was not working as expected.
Bug: 349800749
Change-Id: Ie3567e43a47b62c96e2376de148cc6fa682cd4d1
Test: aninja -t path out/target/product/generic/obj/ETC/frameworks-base-api-current.txt_intermediates/frameworks-base-api-current.txt out/soong/.intermediates/packages/modules/CrashRecovery/framework/framework-crashrecovery.stubs.source/android_common/everything/framework-crashrecovery.stubs.source_api.txt
|
|
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3167797
Change-Id: I04983a7eb72a70280792677a84869d1c03f1462a
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
|
|
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3182455
Change-Id: Ie6afb58133e07ef6ef8606ae4113b090ff1e6694
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
This change allows combined_apis.bootclasspath and
combined_apis.system_server_classpath properties to be modified based on
configuration using select statements.
Bug: 349800749
Test: m nothing --no-skip-soong-tests
Change-Id: I08bf4200738268fe833389f15e24271058528944
|
|
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3174999
Change-Id: I861e0eae8063340425447f4e62f6163a37b38449
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
The `MethodItem` type represents both a normal method as well as being
the super type of `ConstructorItem`. That organization causes a number
of issues in Metalava and has lead to quite a few issues where code
that only expected to be run on methods and not constructors was run on
both. So, a new type `CallableItem` has been added that will eventually
become the super type of both `MethodItem` and `ConstructorItem` and
`ConstructorItem` will no longer extend `MethodItem`.
This change prepares this code for that change.
Bug: 352481366
Test: ./gradlew
Change-Id: I9f2f60ce60337db55246a43e23285921a895519b
|
|
This change specifies is_stubs_module property to a module that
provides stubs, so that the build system recognizes it and can be used
for inter-container dependency.
Test: m nothing
Bug: 338660802
Change-Id: I4a9da74f74fc3c40abd2d52028c86aca538d6e40
|