am skip reason: Change-Id I0ed740e51b6b39c58842a58eabcf3cdf404e73fa with SHA-1 8ec05ff5f6 is in history
Change-Id: I80269040417341c4b75c1100213cfcb09663efac
This was not previously possible due to LoadHooks being run after the
module was registered.
Bug: 155462403
Test: m nothing
Change-Id: Ia8383b9d1272bb12c8a83948753a0e4b0d98a650
am skip reason: Change-Id If0ee967d37425540e69b4ce9304229d9f2cd86bd with SHA-1 872a144dca is in history
Change-Id: I0678ef508bbd49c28ea657600303f05a59274adf
Move depsInfo into android for easier sharing with APK code.
Bug: 149622332
Test: m, diff'ing outputs for conscrypt module.
Change-Id: If0ee967d37425540e69b4ce9304229d9f2cd86bd
Merged-In: If0ee967d37425540e69b4ce9304229d9f2cd86bd
Exempt-From-Owner-Approval: cp from aosp
(cherry picked from commit 872a144dca)
am skip reason: Change-Id Ib3f671493f1d230116bec51b884e8072643b10d4 with SHA-1 5ff28e50b8 is in history
Change-Id: I169552f232ad8ad02a0d472474661cee445741aa
@TestApi does not have stability requirements, so we shouldn't be
checking its compatibility with the last released version.
This CL removes the expectation that a test-removed.txt is checked in
for each module during finalization.
Bug: 155197156
Test: m (with SDK 30 imported)
Change-Id: Ib3f671493f1d230116bec51b884e8072643b10d4
Merged-In: Ib3f671493f1d230116bec51b884e8072643b10d4
(cherry picked from commit 6bf8e415a50826a378cc58aba87854f52c9f1d32)
am skip reason: Change-Id Idbded6b633315034e669e9c5dd2bd30725d5c76b with SHA-1 0fd1de5f0b is in history
Change-Id: I5c0a6cb6d020e1d41b1775854e55b6fa82eb1752
am skip reason: Change-Id I101fa6b03d2530b16e4394a9e466fead48be0ff0 with SHA-1 0c83aba28e is in history
Change-Id: Ie06a72ec6d56cdd3c203f040c448fceb4d896a5a
am skip reason: Change-Id Ib1acf3073e96fe23c92d292ec0b1a91e2cd408db with SHA-1 8cf899afcc is in history
Change-Id: I57c9f1b1b16ce5e122c796f4dc195f2ad2b6a1d2
Previously, errors that were found when splitting visibility rules were
only reported in the check phase and simply ignored during the gather
phase. That was because every visibility property that was processed in
the gather phase had already been checked in the check phase. However,
that is not strictly true as it has always been possible to add a
mutator between the check and gather phases that creates a module with
invalid visibility properties that will just be ignored. Fortunately,
that has not happened.
A follow up commit will add the capability to create modules after the
defaults have been applied which means the chances of invalid visibility
properties being ignored will increase.
This change makes both phases report any errors they find. It will not
have any impact on existing code as if any errors are reported in the
check phase then the build will exit before the gather phase. It will
prevent any invalid visibility errors from being ignored.
Bug: 155295806
Test: m nothing
Merged-In: I101fa6b03d2530b16e4394a9e466fead48be0ff0
Change-Id: I101fa6b03d2530b16e4394a9e466fead48be0ff0
(cherry picked from commit 0c83aba28e)
Adds a couple of new methods to manage visibility property instances to
reduce duplication and encapsulate the implementation slightly better.
The AddVisibilityProperty method is exported as it will be needed by
other packages in follow up commits.
Bug: 155295806
Test: m nothing
Merged-In: Ic1a9bb1e151fc6ae65761344fd210b4e4ba74fbc
Change-Id: Ic1a9bb1e151fc6ae65761344fd210b4e4ba74fbc
(cherry picked from commit 5ec73ecc08)
Treehugger Robot