Deprecation and removal of support of DX was announced here:
https://android-developers.googleblog.com/2020/02/the-path-to-dx-deprecation.html.
There is says:
As of On Feb 1st, 2021, we’ll move to step 3, removing DX fully from
Android Studio and any other build environments.
Test: m sdk
Test: m win_sdk
Bug: 185479734
Bug: 73711890
Change-Id: I2fdbab7ce7ab50a637baf523ae5c2e87ab01fb8c
Deprecation and removal of support of DX was announced here:
https://android-developers.googleblog.com/2020/02/the-path-to-dx-deprecation.html.
There is says:
As of On Feb 1st, 2021, we’ll move to step 3, removing DX fully from
Android Studio and any other build environments.
Test: m sdk
Bug: 185479734
Bug: 73711890
Change-Id: I2d7601037ed4135e00cf48b4b9f490a86fec90cb
The version used to build the platform at a given point in time
might not be the best to use for external developers. Sometimes
bugs in old VMs have to be worked around in D8. Those bugs do
not affect the platform build, but could affect other users.
Therefore, we use separate versions for building the platform
and for shipping in buildtools.
Additionally, make sure that the licenses for libraries shipped
with D8 are reflected in the buildtools NOTICE file.
Test: make -j PRODUCT-sdk_phone_armv7-win_sdk sdk_repo
Test: make -j PRODUCT-sdk_arm64-sdk sdk_repo
Bug: 111748733
Change-Id: I0ca07e45647ea95816f5e96e991673ee24ed9983
core-lambda-stubs.jar will be used to provide an empty
LambdaMetafactory when compiling with javac.
Bug: 65210042
Test: m -j PRODUCT-sdk-win_sdk sdk_repo
Change-Id: Icfef901806b758a0ace2b1937b26b2c3ae00a3d1
development's sdk.atree depends on the generated file
/sdk/files/sdk_files_NOTICE.txt which was accumulating
all the tools notices.
However this file isn't generated anymore.
This replaces it by a static file.
This is only good as a temporary measure to fix the build.
The proper fix is to recreate the SDK rule to generate the
combined NOTICE.txt and move it in development.git
Change-Id: I27e4f38e756b81b002d16dfac5ccaa54a4463786
