| Age | Commit message (Collapse) | Author |
|---|
|
RecurrenceProcessor#yearDay was returning incorrectly for July 1st due
to a wrong hard-coded value. Updating it to the correct value and adding
some unit tests for the function.
Bug: 111972497
Test: atest com.android.calendarcommon2.RecurrenceProcessorTest#testYearDay
Change-Id: If468db15d0f66ca059460fbf09d360360cfe8cdd
|
|
See build/soong/README.md for more information.
Test: m checkbuild
Test: atest CalendarCommonTests
Change-Id: Ib914c5ff464240fa136306e8dde8b90507bf887d
|
|
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
|
|
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
|
|
524cce0089 am: f40b38da25 am: 6db7eaee89
am: 886d7d1277
Change-Id: I9fc9b526e1ce01ecf07c04d2f12e6f5c59c732f4
|
|
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
|
|
- Handle multi-line EXRULE and RDATE.
- Fix existing tests.
- Add more tests.
Fixes: 31054618
Test: adb shell am instrument -w com.android.calendarcommon2.tests/android.test.InstrumentationTestRunner
Change-Id: I73eb8dc876adb253e093d68685deefcc9b02953e
|
|
Fixes that recurring appointments goes invisible
when hit by the failsafe limit.
There is still a hard limit in RecurrenceProcessor,
but at least this limit is applied on a per-event
basis, meaning that it's always possible to create
new recurring appointments without them going invisible.
Change-Id: I6c9e1e10db78e1b73ea9f2b7104621fbbd906452
|
|
Change-Id: I5bd618866d6484037671376e192ee3217c42c366
|
|
Allow for consecutive ";" in rules for recurring events.
Bug 6312732
Change-Id: I3bd82b7818cd755eec7129ca6497746a91cb6653
|
|
Change-Id: I9a354fe360376c43da2290535a038bd6ab4facd3
|
|
Bug: 5876746 Android calendar syncing broken by certain repeated events
Change-Id: Ia0b2bc610148302b1cc3d751c47a958950abfb46
|
|
Specifically
If count < 0, assume 1
If interval < 1, assume 1
Bug: 5676414
Change-Id: I942cdaffcfb98a922c5867c9d08be322c64a0f94
|
|
RFC 5545 says WKST is significant in weekly rules with nonzero
intervals and BYDAY rules, and also in yearly rules with a BYWEEKNO
part. Yearly with BYWEEKNO seems to be generally broken, so this
only attempts to correct weekly recurrences.
Bug 1641249
Change-Id: Icad8762be4685036fc50bed0cc75970e774a21a8
|
|
RFC 5545 says the behavior is unspecified. This just updates
the comments (no code changes).
Bug 5075775
Change-Id: I87d131c260570e2990bb05f624c90f7d78a1eb89
|
|
This adds support for rules like FREQ=MONTHLY;BYDAY=SA,SU;BYSETPOS=x
(for the popular "first weekday of the month" sort of recurrence).
Implementing fully general support for BYSETPOS is a bigger task.
Bug 4946753
Change-Id: I437c0cf52bbed2a191729b3891c3afda62ffb633
|
|
The definition of "recur" in 4.3.10 suggests that FREQ must
come first, but the description is really just trying to say that
FREQ is mandatory. The text makes it clear that there is no
ordering on rule parts.
This removes the explicit test, and updates the set of test
rules.
Change-Id: I908ae388456a7df2d12a0c18a2174af8f95ec421
|
|
Adds a few more tests for RecurrenceSet.
Also, fix the RecurrenceSet TAG.
Change-Id: I429cbea065e2b5d8d3a97662e54b9428ad8be257
|
|
Move RecurrenceProcessor and DateException, so that app code can
access the recurrence generator. Useful for e.g. bug 4977517.
Change-Id: Iaeb3e486a6a4133aa3d361d73461a0a0a3771bb4
|
|
Drop the shared ID so that the tests can be installed and run.
Updated a comment.
Change-Id: Ic58088c3cbda601bc44203815a80866c3d318b3b
|
|
Move some classes from android.pim to com.android.calendarcommon.
Bug 4575374
Change-Id: I0da19545253f0bc887d2c284414f372ad740e946
|
