History log of /frameworks/support/v17/preference-leanback/Android.mk
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
9439d708170c7dd6c985453fd1999bbe8445eddf 25-Oct-2016 Alan Viverette <alanv@google.com> Move all support library projects to use a single compilation unit

Also cleans up build files to include annotations as an explicit import,
set compileSdkVersion consistently to currentSdk, and remove unnecessary
lines. Removes obsolete API directories in VDC / AVDC.

Because NotificationCompatBase was using @removed APIs, updated that class
to use reflection. Also fixes method visibility in VDC / AVDC.

Bug: 29630077
Test: make and gradle builds successful
Change-Id: Ia9208246837347ce3d8df4adbe6b0ce406d3844a
/frameworks/support/v17/preference-leanback/Android.mk
c39d9c75590eca86a5e7e32a8824ba04a0d42e9b 25-Aug-2016 Alan Viverette <alanv@google.com> Add @RestrictTo(GROUP_ID) annotations to match @hide docs annotations

Also removes some unnecessary @hide annotations on classes that wouldn't
have shown up in docs anyway due to package/private visibility or NO_DOCS.

Bug: 27937193
Change-Id: Iab127a5a3ce57a2d61965d3cef782621eb3859f5
/frameworks/support/v17/preference-leanback/Android.mk
7b59d3ae599949c7c6b4c5806b4dda7f41147690 13-Jun-2016 Alan Viverette <alanv@google.com> Remove old API check artifacts, invoke gradle from old make target

Fixes paths in build.gradle so they are relative to the project root,
rather than the current directory.

Bug: 28124434
Change-Id: Ieeae97cd789a6addf3282f2c43cd754ca8e84c57
/frameworks/support/v17/preference-leanback/Android.mk
3c141cd9c1cfecd9352b82d9dae4d9601fabd4e6 11-Jun-2016 Yigit Boyar <yboyar@google.com> Revert "Remove old API check artifacts, invoke gradle from old make target"

This reverts commit 009647bbfa5efef608d6a660fc8ba191d876b1ed.

Change-Id: I59deae2a7180f58bc0c770f7b3f70962c8d2f73f
/frameworks/support/v17/preference-leanback/Android.mk
009647bbfa5efef608d6a660fc8ba191d876b1ed 09-Jun-2016 Alan Viverette <alanv@google.com> Remove old API check artifacts, invoke gradle from old make target

Fixes paths in build.gradle so they are relative to the project root,
rather than the current directory.

Bug: 28124434
Change-Id: I8cde9db47d60ec1220d35fce5ef6fd2c6e97b1f8
/frameworks/support/v17/preference-leanback/Android.mk
6759b1021d8198ad1d239bb30e5a102b99624bce 25-Feb-2016 Adam Lesinski <adamlesinski@google.com> Build support libs with AAPT2

Use AAPT2 to build the framework support libraries. Apps built with AAPT2 can more efficiently
link against these libraries by specifying their module name in LOCAL_STATIC_ANDROID_LIBRARIES.

Ex:

LOCAL_STATIC_ANDROID_LIBRARIES := android-support-v7-appcompat android-support-v4

Apps built with AAPT2 do not need to specify --auto-add-overlay or --extra-packages, as these
are automatically added as needed by the build system.

This change will not affect any apps that currently depend on the support libraries.
This is because they import the resources directly.

We use LOCAL_JAR_EXCLUDE_FILES := none only to support javac when building javadoc.
Jack builds are correct because the build system passes in the latest generated R.java
ahead of any previous ones packaged in classes.jack. This means we can dynamically reference
a support lib module, correctly seeing non-final R.java. Then at app package time, we only
include the final R.java generated by the AAPT2 packaging step.

Bug:25958912
Change-Id: I6577a91e4d428dd29fecaa86a26be43d4da8310c
/frameworks/support/v17/preference-leanback/Android.mk
57f39186667b8acef1a0ebeda585c357a751a8b3 02-Apr-2016 Adam Lesinski <adamlesinski@google.com> Revert "Build support libs with AAPT2"

This reverts commit 66b8608151c5923de3c9877bc03218d83f6b3beb.

Change-Id: I2178c0336bef8386e1f36ff3816b6dbf1e6a64d0
/frameworks/support/v17/preference-leanback/Android.mk
66b8608151c5923de3c9877bc03218d83f6b3beb 25-Feb-2016 Adam Lesinski <adamlesinski@google.com> Build support libs with AAPT2

Use AAPT2 to build the framework support libraries. Apps built with AAPT2 can more efficiently
link against these libraries by specifying their module name in LOCAL_STATIC_ANDROID_LIBRARIES.

Ex:

LOCAL_STATIC_ANDROID_LIBRARIES := android-support-v7-appcompat android-support-v4

Apps built with AAPT2 do not need to specify --auto-add-overlay or --extra-packages, as these
are automatically added as needed by the build system.

This change will not affect any apps that currently depend on the support libraries.
This is because they import the resources directly.

We use LOCAL_JAR_EXCLUDE_FILES := none only to support javac when building javadoc.
Jack builds are correct because the build system passes in the latest generated R.java
ahead of any previous ones packaged in classes.jack. This means we can dynamically reference
a support lib module, correctly seeing non-final R.java. Then at app package time, we only
include the final R.java generated by the AAPT2 packaging step.

Bug:25958912
Change-Id: I5235b73ac68f2050d089aefc3163901ff80f2d46
/frameworks/support/v17/preference-leanback/Android.mk
4ac91fa3f14db2f25345595fb921497c11d4e5c0 31-Mar-2016 Adam Lesinski <adamlesinski@google.com> Revert "Build support libs with AAPT2"

This reverts commit 0dac8d82e2a249d7c9c42ab259389e11cac15400.

Change-Id: I830fb18162b6eea8dde9e38f9dc39b02449ec846
/frameworks/support/v17/preference-leanback/Android.mk
0dac8d82e2a249d7c9c42ab259389e11cac15400 25-Feb-2016 Adam Lesinski <adamlesinski@google.com> Build support libs with AAPT2

Use AAPT2 to build the framework support libraries. Apps built with AAPT2 can more efficiently
link against these libraries by specifying their module name in LOCAL_STATIC_ANDROID_LIBRARIES.

Ex:

LOCAL_STATIC_ANDROID_LIBRARIES := android-support-v7-appcompat android-support-v4

Apps built with AAPT2 do not need to specify --auto-add-overlay or --extra-packages, as these
are automatically added as needed by the build system.

This change will not affect any apps that currently depend on the support libraries.
This is because they import the resources directly.

We use LOCAL_JAR_EXCLUDE_FILES := none only to support javac when building javadoc.
Jack builds are correct because the build system passes in the latest generated R.java
ahead of any previous ones packaged in classes.jack. This means we can dynamically reference
a support lib module, correctly seeing non-final R.java. Then at app package time, we only
include the final R.java generated by the AAPT2 packaging step.

Bug:25958912
Change-Id: I71bff080ff2694aa3df1c8a67d933e2daab0f245
/frameworks/support/v17/preference-leanback/Android.mk
e1cd5a1f80010eece43cb4608505fd39f4832c00 25-Feb-2016 Neil Fuller <nfuller@google.com> Pin support libraries to Java 1.7 so they can be used with dx

The .jar artifacts must contain v51 class files to prevent them
being rejected by dx.

Bug: 26753820
Bug: 27353172
Bug: 27338966
Change-Id: I03a881a86bb6e3fcaa4ccb33e6c0615157ee363f
/frameworks/support/v17/preference-leanback/Android.mk
82b55491586ac50a0f95b60e39a3c18d068941cf 22-Jan-2016 Chris Banes <chrisbanes@google.com> Update support lib to use correct current SDK

BUG: 26714403
Change-Id: I2153dbda365f4552a14df1f432239bddfbbbef00
/frameworks/support/v17/preference-leanback/Android.mk
95ad49b720f4990d39d05f7e46a5c7bc83afc9d6 19-Oct-2015 Chris Banes <chrisbanes@google.com> Fix multi source folder API checking

For libraries which have seperate source folders
per API level, the API generation doesn't currently
work correctly. When generating the stubs, we need to
input all source files, not just the final module.

This has uncovered some file in support-v4 which should
not be public API.

BUG: 20822048

Change-Id: I6216b9688e745db212959a07fcdc21bdd0aa5ab2
/frameworks/support/v17/preference-leanback/Android.mk
6d760296101d0dd1f3df8a696e0bf82ffaee2a49 01-Sep-2015 Dake Gu <dake@google.com> Move FadeAndShortSlide to leanback

Leanback need the class to workaround
Bug 23718734

Change-Id: I139e87727995041aa00bff2fd973248c14302845
/frameworks/support/v17/preference-leanback/Android.mk
c21389c7e56556c24e460d28caab732bad4c15d9 01-Jul-2015 Tony Mantler <nicoya@google.com> Add animations to LeanbackPreferenceFragment

The prefscreen-to-prefscreen animations used to be handled by the StackedLayout,
but now we can do them with fragment transitions.

b/22179367

Change-Id: I2141cc4701016b6f4743b94c2242053abb67b07b
/frameworks/support/v17/preference-leanback/Android.mk
1740c8f22aec10bd49ff860722d638f8c6c0b0a5 17-Apr-2015 Deepanshu Gupta <deepanshu@google.com> Add resources to recyclerview dependency.

Change-Id: I423c6b8f648da2e1e93994fa15d92dbfae7f44a2
/frameworks/support/v17/preference-leanback/Android.mk
f62fcdec92e2f96ec61579392ed2b593cff35b39 25-Feb-2015 Chris Banes <chrisbanes@google.com> Generate API files for the support libraries

make update-support-api
make check-support-api (run automatically on sdk builds)

BUG: 19478450

Change-Id: Idd0f12c457b7dc084a66158de452969d7afdb8dc
/frameworks/support/v17/preference-leanback/Android.mk
d2e2c839aad68a84aa190e615738e72795eb8bf3 23-Mar-2015 Tony Mantler <nicoya@google.com> Rename v17/preference to v17/preference-leanback

Change-Id: I687ef59f3e727b3b4ada07d62a7f3610f989a8b3
/frameworks/support/v17/preference-leanback/Android.mk