-
Notifications
You must be signed in to change notification settings - Fork 18
SimpleUnitFormat won't parse what it just formatted #201
Comments
By the way, I've tried upgrading the dependencies to:
Result is still the same. |
You should not use something like "µ" with |
Ah sorry, I actually tried both ASCII and DEFAULT, both fail (the output is slightly different, the substance does not change, the class cannot parse what it just formatted). Let me update the code sample. |
It's a little weird, but currently our focus is on Indriya where a sort of round-trip from The same does not work in uom-se, I cannot say, if and who could backport everything that's been improved with Indriya into uom-se, because it will ultimately replace it? @aaime Would you be able to use EDR level Indriya? Currently |
D'oh, sorry, that's not what I mean, had to search the term on urbandictionary.com (not a native english speaker). Updated the example code! |
Not for "systems.uom:systems-common-java8", that (until it may eventually be archived) is supposed to use uom-se, but the modules without the "java8" qualifier, e.g. "systems.uom:systems-common" are backed by Indriya 1.0 already. Indriya is the new Reference Implementation (RI) and when JSR 385 goes live, Indiya 2.0 will be Final. The most recent version is the 2.0-EDR Milestone. |
Do you have a guess about when Indiya will be released? Even just a vague guess, weeks, months, years? |
It is a pretty clear guess thanks to JCP.next and the SI system undergoing many changes early next year. Even if the SI changes were postponed (unlikely but not impossible) we plan to release 2.0 in Q1 of 2019. |
I see you closing the ticket, does that mean we should migrated to Indriya? |
Yes, if you can and are not bound by a legacy application that uses 1.0 and can't be changed, please do. |
The following little program shows a case in which the SimpleUnitFormat does not seem to be able to parse back what it just created:
The output being:
Considering that it might be classpath related, here is what I have:
The text was updated successfully, but these errors were encountered: