In my case, there is no reason why we couldn't use the usertype proeject. However it would require going through all our model classes in all our libraries and re-annotating them with the org.jadira.usertype.dateandtime.joda class names ‹ and then testing each class properly. Keeping the old Joda-Time Hibernate library in place simply requires less effort; no code updates and less time regression testing.
Cheers Charles On 20/01/11 6:28 PM, "Chris Pheby" <ch...@jadira.co.uk> wrote: >Dear all, > >I have watched this thread with interest. The changes are straightforward >but they do break compatibility with older versions of Hibernate. One >issue with publishing a jar containing these patches is that Hibernate >3.5 and later are not yet in Maven central. In usertype I currently >provide runtime support for both 3.6 and 3.5 and earlier. There is also a >simple migration to JSR 310. > >Why would you not want to use the usertype project? I am very interested >in your feedback so I can address any issues you had. > >Thanks and Regards > > >Chris > ------------------------------------------------------------------------------ Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Joda-interest mailing list Joda-interest@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/joda-interest
