On Tue, Jul 18, 2023 at 8:04 PM Gilles Sadowski <gillese...@gmail.com> wrote: > > > Even the "units of measurement" work is a bit fragmented. If you want > > to use KILOMETERS and MILES for instance, or use FEET, you have to mix > > and match different libraries with the standard, and the different > > libraries are all based on different vintages of the standard. It > > would be nice to have a single library to be able to use. But I'd > > check with the JSR folks first to see if there was an interest in > > having an ASF implementation. > > If there is a reference implementation, why work on another?
Actually, just checking the relevant repos, some parts of the situation aren't too bad at the moment. The JSR 385 API and extensible service provider interface (but no actual units) had a release a couple of months ago and lives here: https://github.com/unitsofmeasurement/unit-api The Indriya reference implementation had a release a few weeks ago and lives here: https://github.com/unitsofmeasurement/indriya In the past, these releases were a little patchy and sometimes out of date with one another. At times, it wasn't clear whether the reference implementation was meant to live beyond the JSR spec period (I say that with no internal knowledge of the expectations of the authors and very limited visibility of their work) but it now seems like the reference implementation is being maintained. What hasn't changed is that other libraries have also been produced for other units, e.g. FEET, MILES, CELSIUS, FAHRENHEIT, LIGHT_YEAR, PARSEC, and KILOMETER [the reference implementation supports KILO(METRE)]. But these other libraries aren't necessarily on the latest API. Cheers, Paul. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
