Use Advanced Search to search the entire archive.
[jsr363-experts] 0.8-RC3
- From: Werner Keil <
>
- To: "
" <
>
- Subject: [jsr363-experts] 0.8-RC3
- Date: Fri, 3 Jul 2015 13:47:03 +0200
Dear Experts,
The API already went out as 0.8-RC3 yesterday and is now available on
MavenCentral, too.
For 2 formatting issues, at least one under advanced investigation (see
https://java.net/jira/secure/RapidBoard.jspa?rapidView=12&view=planning)
the RI is not currently out. I know what the problem is there, the duality
of KILOGRAM and GRAM in SI and other unit systems causes an ambiguity for
some Mass units, where it can happen that MICRO(GRAM) internally becomes
NANO(KILOGRAM) (so the factor is always correct, so is the numeric value)
but a UnitFormat hack aiming to replace KILOGRAM with GRAM does not
understand that, so MIGRO(GRAM) ended up "ng" rather than "µg".
RI Unit tests catch this, and some aspect of the problem is already
addressed.
The 5 or so JUnit tests failing show this on the CI server:
expected:<[n]g> but was:<[pk]g>
It is actually mathematically correct but ugly and usually not what people
would expect.
A side-effect could be, that "chaining" operations, e.g. "PICO(KILO(GRAM)"
would result in a formatting based on GRAM for everything but KILOGRAM. So
if you chained them like that in the end you'd always get "ng", not "pkg".
If we really needed variation for some UnitFormat implementations, then we
could address that. For now especially the RI (which also does not
translate or localize units by default) should be fine with that.
If at least the GRAM vs. KG bug can be fixed, I expect RI to be released no
later than a week from now. I'll check the separate HERTZ issue (also
mathematically correct but the "human-readable" format expects different;-)
and everyone who can is welcome to have a look, too. Otherwise we have to
shift it into the next sprint. Either Public Draft or (should there be more
changes worth publishing in the meantime) another RC.
Regards,
Werner