[threeten-dev] JapaneseDate DAY_OF_YEAR

roger riggs roger.riggs at oracle.com
Mon Jun 24 13:23:25 PDT 2013


Hi Stephen,

yes, we (Oracle) need to nail down the Japanese calendar details and get 
them corrected.
I've used JBS for some of these that seemed to be implementation bugs
and not directly related to the 310 spec.  But the bugs.sun.com 
visibility is poor.
Continuing to use Github is better for transparency of JSR 310.

I'll create an JBS issue for the commented out test cases.
As/if you discover other problems feel free to put them in Github.

Roger


On 6/24/2013 4:08 PM, Stephen Colebourne wrote:
> On 24 June 2013 20:43, roger riggs <roger.riggs at oracle.com> wrote:
>> On 6/24/2013 7:21 AM, Stephen Colebourne wrote:
>>> And there is a disagreemnet as to the start of the Meiji era.
>>> sun.util.calendar.Era says 1868-01-01, wheras our Japanese Era says
>>> 1868-09-08.
>>> Is the old Sun class wrong here?
>> yes, there is an issue for this in JBS 8015478, but I haven't gotten to
>> fixing it.
> I think its you/Oracle who need to decide on the correct dates for the
> Japanese era via the I18N team.
>
>>> Here are some more tests, with bugs commented out.
>>> https://gist.github.com/jodastephen/5849354
>> These look fine.
> This test case has a number of commented out lines that I felt should
> pass, but don't because of era-based issues (misaligned start dates
> and NPE from missing sun era class).
>
>>> Who is working to fix this class?
>> No one is dedicated; I've been working on identified bugs.
> I'll leave it up to you/Oracle to fix the tests I commented out and
> the era stuff.
>
> Should I raise other issues in GitHub?
> Stephen



More information about the threeten-dev mailing list