| 69fc4ab478c65571e31c4156c4cff998cef4ecec |
20-Apr-2017 |
Przemyslaw Szczepaniak <pszczepaniak@google.com> |
Remove ValueBased paragraphs from java.time javadocs
The ValueBased link is unreachable.
Test: make docs
Bug: 35129434
Merged-In: I9751b2ad51776134d5695798e1fc1dcefe04c455
Change-Id: I667e0d3534891aca7dd5379ccc0571418af5ee49
(cherry picked from commit fa84287e36805c14f8177d449207b9701faacd10)
ijrahDate.java
apaneseDate.java
inguoDate.java
haiBuddhistDate.java
|
| 6975f84c2ed72e1e26d20190b6f318718c849008 |
01-Mar-2017 |
Tobias Thierer <tobiast@google.com> |
Make Android patch docs in ojluni more consistent with style guide
This CL consists of an automated and a manual part (originally
reviewed as separate CLs, then squashed together before submitting
in order to minimize the number of times each Android-changed line
is touch, since that makes future git archaeology on these simpler).
Automated part: Run the following command (performs regex replacements):
find ojluni -name \*\.java | xargs sed -i \
-e 's/Android[- ]changed/Android-changed/ig' \
-e 's/Android-changed :/Android-changed:/g' \
-e 's/Android-changed \(BEGIN\|END\)/\1 Android-changed/g' \
-e 's/Android-changed - /Android-changed: /g' \
-e 's/Android[- ]removed/Android-removed/ig' \
-e 's/Android-removed :/Android-removed:/g' \
-e 's/Android-removed \(BEGIN\|END\)/\1 Android-removed/g' \
-e 's/Android-removed - /Android-removed: /g' \
-e 's/Android[- ]added/Android-added/ig' \
-e 's/Android-added :/Android-added:/g' \
-e 's/Android-added \(BEGIN\|END\)/\1 Android-added/g' \
-e 's/Android-added - /Android-added: /g' \
-e 's/----- \(BEGIN\|END\) android\( -----\)\?/\1 Android-changed/g' \
-e 's/\/\* \(BEGIN\|END\) Android-changed \*\//\/\/ \1 Android-changed/g'
Manual part: Move BEGIN Android-* lines out of block comments
Some Android-{changed,removed,added} lines occurred inside block comments.
This CL targets places in ojluni that contained the String "* BEGIN Android-"
Changes made by this CL include:
- Move the "BEGIN Android-" line into a line comment (the style guide
mandates that "Android-" lines are always in line comments). In many
cases, that line comment is immediately followed by a block comment
holding commented-out upstream code.
- Add corresponding "// END Android-" line comments, where missing.
- Drop documented import changes altogether. These create noise for
little benefit:
(1.) Most import problems will be found at compile time
(2.) They generally correspond to documented changes elsewhere in
the file.
- In most cases, the phrasing of comments and the decision whether to
keep commented out upstream code was not changed by this CL.
- Some additional tweaks were made in line with the style guide.
No attempt was made to:
- Verify that commented-out upstream code actually matches the
current upstream.
- Make any fixes (eg. to comments) that would have required
git archaeology (looking up historic commits).
Bug: 35841464
Test: make droid cts update-api
Change-Id: Ibc60979cb6061cfb0e9c7096cc9dcab30ddfa733
ijrahChronology.java
|
| 21c40e1463c0026f5df4faa5b17cb34ed4ec267c |
15-Feb-2017 |
Tobias Thierer <tobiast@google.com> |
Document Android changes/additions vs. upstream in Calendar.java
- Add missing comments for Android additions/changes
- Clarify the extent of changes with existing comments by
introducing BEGIN/END lines.
- Fix typo in Android-added @hide method name
getJapanesImperialInstance()
Consideration whether each change is correct or should be upstreamed
is not part of this CL.
Bug: 35235723
Test: make droid cts
Change-Id: I5fa9565162b62c1d4ce51875c7b83a000ef1b289
apaneseChronology.java
|
| 1d3a3b7676bc344c9daf25285d19f86b3b6c946a |
10-Feb-2017 |
Przemyslaw Szczepaniak <pszczepaniak@google.com> |
Javadoc fixes
Ported from openjdk8u121
changeset: 11449:11a8193dfa30
user: dfuchs
date: Wed Mar 02 11:14:35 2016 +0100
summary: 8148820: Missing @since Javadoc tag in Logger.log(Level, Supplier)
changeset: 11280:b6d732a87fc5
user: psandoz
date: Wed Jan 21 09:46:24 2015 +0000
summary: 8062901: Iterators is spelled incorrectly in the Javadoc for Spliterator
changeset: 11914:7f169fa54a10
user: rpatil
date: Wed Oct 12 16:29:59 2016 +0530
summary: 8166875: (tz) Support tzdata2016g
changeset: 11022:6cd4ceeb2f05
user: igerasim
date: Tue Aug 25 19:45:07 2015 +0300
summary: 8134356: {@code} tag contains < and > sequences
Test: CtsLibcoreTestCases
Bug: 31028374
Change-Id: Ie48fa6d5fb6d629a624492c499a40a0ef96bde8b
hronoLocalDate.java
|
| 00b9ee797814c738b829458a800c163a5832283f |
08-Feb-2017 |
Przemyslaw Szczepaniak <pszczepaniak@google.com> |
java.time.chrono.Chronology.isLeapYear fix
Ported from openjdk8u121
changeset: 11249:17ed74f96963
user: robm
date: Fri Dec 04 18:40:59 2015 +0000
summary: 8067800: Clarify java.time.chrono.Chronology.isLeapYear for out of range years
Test: CtsLibcoreTestCases & CtsLibcoreOjTestCases
Bug: 31028374
Change-Id: I0f515a82a36af1f6da0186510d2c5ca808f3a41a
ijrahChronology.java
|
| 3866c080537c37ff7bd246b8d7b1651cd83a07c3 |
21-Nov-2016 |
Joachim Sauer <jsauer@google.com> |
Fix Japanese Chronology.
The JapaneseChronology class depends on the ImperialJapaneseCalendar
being returned by Calendard.getInstance(). Since Android always returns
a GregorianCalendar from that class, the tests will fail.
This fixes the problem by importing the JapaneseImperialCalendar class
from the OpenJDK (with minor tweaks to remove mentions of the ZoneInfo
class) and adapting the relevant classes to use a new explicit method on
Calendar to request such a calendar instance.
Also apply update LocaleGregorianCalendar to jdk8u60 which fixes an
off-by-one error in calculations related to eras.
Added ChronologyDisplayNameTest to ensure future Chronologies return
sane values for their display name and their eras display names.
Bug: 28832222
Test: artrun testng-time.xml
Test: run cts -m CtsLibcoreTestCases
Change-Id: I3eb5d4509ad03ee3d736c7926c605f378b56d0b2
apaneseChronology.java
apaneseDate.java
|
| 14b36b486e3ab4a94eec7dad1bb4dcbe188e5cf5 |
21-Oct-2016 |
Joachim Sauer <jsauer@google.com> |
Fix loading calendar properties.
Calendar properties should be loaded as fixed resources and not from the
file system.
Bug: 28832222
Test: Loading java.time classes now succeeds, java.time tests still fail.
Change-Id: I47188f8558f3fbc6ed49bbc66d5eb93a860e8619
ijrahChronology.java
|
| c9dd3385ea6f927052783f42fb1282fb093e636e |
01-Sep-2016 |
Joachim Sauer <jsauer@google.com> |
Initial import of java.time.
This is a verbatim copy of the classes in java.time from the jdk8u60
branch of the OpenJDK.
They are not yet part of the build and wouldn't compile yet (no local
modifications whatsoever).
Bug: 28832222
Test: Not build, not tested.
Change-Id: I8bb148cb1095b08af895c4abffed9f22b107c218
bstractChronology.java
hronoLocalDate.java
hronoLocalDateImpl.java
hronoLocalDateTime.java
hronoLocalDateTimeImpl.java
hronoPeriod.java
hronoPeriodImpl.java
hronoZonedDateTime.java
hronoZonedDateTimeImpl.java
hronology.java
ra.java
ijrahChronology.java
ijrahDate.java
ijrahEra.java
soChronology.java
soEra.java
apaneseChronology.java
apaneseDate.java
apaneseEra.java
inguoChronology.java
inguoDate.java
inguoEra.java
er.java
haiBuddhistChronology.java
haiBuddhistDate.java
haiBuddhistEra.java
ackage-info.java
|