So? Any movements on this? :) about jsr354-api-bp HOT 3 CLOSED

That's not entirely true. Large companies have a very long term production cycle and even for ongoing development are in many cases restricted to Java 6 or 7 (in production untouched there are certainly many cases of Java 1.4 or 5, too trust me;-) Especially for ThreeTen I consider the BP (this idea was largely modeled after) pretty much a waste of time, since applications under SE 7 or before can pretty much use JodaTime and many with such need did. They would in almost every case keep JodaTime or if the solution can be ported to Java 8 then switch to ThreeTen, but not waste (litteral;-) Time and Money on a Joda to BP to ThreeTen journey. JodaMoney has never even barely reached adoption we saw for JodaTime over the years, and it lacks almost every aspect of JavaMoney, especially the vital part of currency conversion (else you may just as well put BigDecimal and Currency in one class;-) so there should be quite some demand out there. Assuming we want to do it.

from jsr354-api-bp.

What we (as contributors and users of the ThreeTenBP) must keep in mind, is that this "fork" of the API (it is nothing more than that at the end of the day) means, everything from RI to libraries must be completely back-ported, too.
That's why JSR-363 chose a more lightweight approach of keeping the API portable. So some parts of the library (e.g. those directly dependent on Java SE 8) need to be duplicated or maintained for multiple platforms, while e.g. data types like "Heart Rate" only depending on the API are cross-platform, too, making their reuse easier;-)

from jsr354-api-bp.

Ok, thanks

from jsr354-api-bp.