Use Advanced Search to search the entire archive.
[jsr363-experts] Fwd: Fw uom-se#102
- From: Werner Keil <
>
- To: "
" <
>
- Subject: [jsr363-experts] Fwd: Fw uom-se#102
- Date: Wed, 2 Dec 2015 10:40:16 +0100
Dear experts,
Otavio might be a little busy, and while Spec Leads or those driving a
particular project/module have the ultimate say, we try to hear as many
qualified opinions as possible for most decisions, so any thoughts on
https://github.com/unitsofmeasurement/uom-se/issues/102 (a suggestion to
keep the Java SE port as Locale and i18n agnostic as the RI) ?
I mentioned my concerns or arguments in the thread. Those who have a GitHub
user, please feel free to also do so there.
We have not heard from some of the OpenJDK contributors I reached out to
following their JavaOne presentation of Kona:
http://hg.openjdk.java.net/kona However, if you just look at the
repository, everything other than COAP seems untouched for over 9 months
now. And even COAP has not been officially released like say Device I/O.
Frankly speaking, at least those at Oracle in the OpenJDK team (unless
they're made redundant or leave by themselves;-) must all be drawn into
rudder-boost for an obviously delayed Java SE 9 right now. Why else would
Mark have postponed the Final release just yesterday? So let's not worry
about OpenJDK right now. We'll wait for the result of the Public Review and
based on that plan a Final release, but unless something very unexpected
happens, we should be able to go final within a year from now. If any
OpenJDK sub-projects were delayed until Java SE 9 is finally there, we'd
have to live with that like everybody else. And being a standalone JSR
everyone can use it now or no later than a final release on all supported
platforms.
Regards,
Werner
---------- Forwarded message ----------
From: Werner Keil
<
>
Date: Tue, Dec 1, 2015 at 4:53 PM
Subject: Fw uom-se#102
To: Otávio Gonçalves de Santana
<
>
Hi,
What do you think of the demand in:
https://github.com/unitsofmeasurement/uom-se/issues/102
I already commented, and while we have not heard from OpenJDK contributors
around Kona, I'd rather handle this in a way OpenJDK does elsewhere. E.g.
"timezone data" etc. (which are usually more static btw, only TZ changes
every once in a while) coming from CLDR come with every Java SE profile
while ME has no notion of a Locale, hence locale-sensitive implementations
or l10n data makes no sense to the RI.
Feel free to comment or simply close ("wontfix"), if you think the ticket
is inappropriate.
Thanks,
Werner