| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Those annotations could be inferred by some tools (like Kotlin), but the
https://checkerframework.org/ doesn't check inherited annotations
complaining about all equals() invocations that get nullable argument.
The change was generated by running
find . -name \*.java | xargs sed -i 's/public boolean equals(Object /public boolean equals(@Nullable Object /'
in the frameworks/base directory and by automatically adding and
formatting required imports if needed. No manual edits.
Bug: 170883422
Test: Annotation change only. Should have not impact.
Exempt-From-Owner-Approval: Mechanical change not specific to any component.
Change-Id: I5eedb571c9d78862115dfdc5dae1cf2a35343580
|
| |
|
|
|
|
| |
Bug: 141747409
Test: atest CtsLibcoreTestCases CtsLibcoreTestCases
Change-Id: Id3c9a56dcf86b6f5ec81d09d12e432fc97f178c0
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Track changes in libcore/
Bug: 148086409
Test: treehugger
Change-Id: I0aadc51e58eb5cc4ffca938429d5f31c0bc77edb
|
| |/
|
|
|
|
|
|
|
| |
ICU's TimeZone.toString() prints out too much information. Only the ID
is useful.
Bug: 149014708
Test: build only
Change-Id: I7d633f7946f82696e13dbc39749b6f9f44f83fa3
|
| |
|
|
|
|
|
|
|
|
| |
To avoid a @Nullable Boolean one method has been split into two. After
some changes in the last release this also removes an optional parameter
from the two new methods as it is now always null.
Bug: 148450671
Test: treehugger
Change-Id: I83be9647943c16ae30af4f8d032db428af1ad5fc
|
| |
|
|
|
|
|
| |
Test: treehugger
Bug: 148842434
Merged-In: If022a726a058a90cb5446d220628c76800da8e96
Change-Id: If022a726a058a90cb5446d220628c76800da8e96
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Behavioral change to remove the possibility of null from getTimeZone().
The rest are naming and documentation improvements.
Bug: 148450671
Test: treehugger
Change-Id: I412046ce343e76463bf27d8dc5fea46adfd85b0d
|
| |/
|
|
|
|
|
|
|
|
| |
Tidy up the libcore.timezone APIs to make them as close as possible to
android.timezone. In future, these classes should be repackages to be
the actual android.timezone classes, so the APIs need to be in sync.
Bug: 148086409
Test: treehugger
Change-Id: Ia520abcf00e691f4a1b5549dafec44b76075e31a
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Several android.timezone classes have already been exposed for the
telephony module work, so these tests provide coverage for those.
Additional APIs have been exposed for MTS testing, i.e. to provide
greater confidence that the tzdata module data is correct / is
being read correctly.
Also, small changes to existing code to make them consistent with new
classes. Small docs improvements.
Bug: 147884233
Test: see system/timezone change
Change-Id: I047b29f17a41993f859947a6d6c3685896fe4cb6
|
|
|
Introduce classes that exist to give the telephony module something
stable to call for in-process utilities: libcore cannot directly expose
System APIs today and the package names are internal. The APIs are the
subset of internal libcore.timezone APIs used by telephony code
currently.
Bug: 139091367
Test: See associated frameworks/opt/telephony commit
Merged-In: I6109aef77171346ecb103c190526b7b9b81012b2
Change-Id: I6109aef77171346ecb103c190526b7b9b81012b2
(cherry picked from commit 944aeffa85ab0a94e20a4edc7293fe70f904bddd)
|