If we are going to make this change it will have to be v3.0. And we
should release a v2.2 first.
Stephen
On 4 January 2013 16:32, Brian S O'Neill wrote:
> In Joda-time 2.0, changes were made to make the code compliant with the
> Java 5 memory model, but without breaking compatibility. The soluti
In Joda-time 2.0, changes were made to make the code compliant with the
Java 5 memory model, but without breaking compatibility. The solution
was to define several fields as volatile, because declaring them as
final would break subclasses or serialization.
Making the BaseDateTime fields volatil
