Rename ParserException to MeasurementParseException about unit-api HOT 8 CLOSED

A) Rename ParserException to MeasurementParseException for consistency with a large number of APIs and frameworks (JSR 310, 354, Jackson, Gradle,...) marking the old one deprecated.

from unit-api.

Removed usage of ParserException from a format() method, so I would leave it for now, and close this one. Leaving #58 open.

from unit-api.

Reopened this as it would be cleaner and more consistent with JSR 310, 354 and others.

The idea would be to leave ParserException in the API 2.0 if we have to (for backward compatibility) but simply extend a new MeasurementParseException and mark ParserException deprecated.

Please vote on either:

from unit-api.

B) Keep ParserException as it is.

from unit-api.

Why not MeasureParseException (makes more sense and shorter) ?

from unit-api.

But this exception can also occur while parsing Unit objects instead of Measure objects, isn't it?

from unit-api.

Yes, but Measure is not an API element any more, Quantity is. Having the base exception start with Measurement, I thought MeasurementParseException (similar to DateTimeParseException in Date/Time) would be a good name. We have a QuantityFormat interface now, so both Unit and Quantity can be parsed, which is why UnitParseException won't be enough.

from unit-api.

Although it is only an SPI element of Indriya, we have a Measurement interface ever since JSR 363, so calling it MeasurementParseException sounds more consequent since this exception will also extend MeasurementException. Compared to IncommensurableException it is just one more character ;-)

from unit-api.