diff options
| author |  Adam Michael <ajmichael@google.com> | 2016-11-30 04:38:09 +0000 |
|---|---|---|
| committer |  Irina Iancu <elenairina@google.com> | 2016-11-30 08:09:18 +0000 |
| commit | f699b502ef6a57dc68570486191ad1c318e8fd1b (patch) | |
| tree | 5a6f9aae6006167ea5054372b2a134b9523d8b68 /CHANGELOG.md | |
| parent | 79d09f7fae477dbdd57a79ec406e159c588155eb (diff) | |
Delete old targets from android_sdk_repository_template.bzl
In December 2015, these JARs needed for these targets were removed from all subsequent Android SDK releases. They were replaced by a two local maven repositories:
<android sdk>/extras/android/m2repository and <android sdk>/extras/google/m2repository. Furthermore, the new dependencies are AARs and the Maven repositories are sem-ver'd so the developer needs to select the version of the library to use.
In https://github.com/bazelbuild/bazel/commit/2fcf0e I added support for android_sdk_repository to parse these local maven repositories and generate java_import and aar_import rules along with their dependencies.
Since these "extras" do not ship with the SDK by default and are not versioned with the build-tools, you cannot currently download the old JAR versions. As such, anyone who has updated their Android SDK in the last year should not have been able to download the old JARs.
See https://github.com/bazelbuild/bazel/issues/1745 for the tracking issue and information on migrating from the old targets to the new ones.
RELNOTES: Top level @androidsdk support library targets have been replaced by @androidsdk//<group id>:<artifact id>-<version> for Android SDK Support and Google Play Services libraries.
--
MOS_MIGRATED_REVID=140562616
Diffstat (limited to 'CHANGELOG.md')
0 files changed, 0 insertions, 0 deletions