| a4baee7fe55f82ec0576aa173e5e6555fe8552ea |
|
22-Feb-2018 |
Anton Hansson <hansson@google.com> |
frameworks/opt/calendar: Set LOCAL_SDK_VERSION where possible.
This change sets LOCAL_SDK_VERSION for all packages where
this is possible without breaking the build, and
LOCAL_PRIVATE_PLATFORM_APIS := true otherwise.
Setting one of these two will be made required soon, and this
is a change in preparation for that. Not setting LOCAL_SDK_VERSION
makes the app implicitly depend on the bootclasspath, which is
often not required. This change effectively makes depending on
private apis opt-in rather than opt-out.
Test: make relevant packages
Bug: 73535841
Change-Id: I6b6411cb008ddaf9f1aac419bf7432b3215f100a
/frameworks/opt/calendar/tests/Android.mk
|
| 5151af823c9c03bedd30b41caaa01e53e3324c76 |
|
08-Dec-2017 |
Paul Duffin <paulduffin@google.com> |
Stop statically including legacy-android-test
Statically including legacy-android-test leads to duplicate classes
which causes build time problems (with Proguard) and runtime problems on
older SDK versions. This change:
* Stops statically including legacy-android-test.
* Adds compile time dependencies on andoid.test.base, android.test.mock
and android.test.runner where necessary.
* Adds <uses-library android:name="android.test.runner"/> to any
affected package to ensure that the classes that were included by
legacy-android-test are still available at runtime. That also adds a
dependency on android.test.base and android.test.mock.
The following change descriptions were generated automatically and so
may be a little repetitive. They are provided to give the reviewer
enough information to check the comments match what has actually been
changed and check the reasoning behind the changes.
* tests/Android.mk
Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because
CalendarCommonTests's source depends on its classes and because of
these changes they are no longer present on the compilation path.
Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
because statically including the classes in CalendarCommonTests
results in duplicate classes which leads to build time and compile
time issues.
Bug: 30188076
Test: make checkbuild
Change-Id: Iadc6b967caaf8d5ce5b8a348ad33e1407da8470f
/frameworks/opt/calendar/tests/Android.mk
|
| 2de86d3eaf4d22baa452817e549516cc4add1bf8 |
|
17-Jan-2017 |
Paul Duffin <paulduffin@google.com> |
Prepare for removal of legacy-test from default targets
In preparation for removing junit classes from the Android API
the legacy-test target will be removed from the
TARGET_DEFAULT_JAVA_LIBRARIES. This change adds explicit
dependencies on junit and/or legacy-android-test to ensure that
modules will compile properly once it is removed.
Bug: 30188076
Test: make checkbuild
Change-Id: Ic37712e161ed1daeff800fb10e21c9f59682efe7
/frameworks/opt/calendar/tests/Android.mk
|
| 0d3524562e330e74f150a17c4dc4dd66a0faae46 |
|
08-Jul-2011 |
Andy McFadden <fadden@android.com> |
Relocate common Calendar classes
Move some classes from android.pim to com.android.calendarcommon.
Bug 4575374
Change-Id: I0da19545253f0bc887d2c284414f372ad740e946
/frameworks/opt/calendar/tests/Android.mk
|