Derek Chen-Becker <[email protected]> writes: > Of course, now that I'm actually digging into the code, it really makes me > want to switch to using Joda Time :).
Yes, yes, yes!! Seriously, I've been thinking about this myself, creating subclasses for all classes using Date. It would be awesome if Lift would use Joda time, but I assume there will be too many breaking changes at this point..... > Also, the LiftRules.parseDate function currently does DateTime > parsing, so I would have to make a breaking change to rename it to > parseDateTime and add new parseDate and parseTime (and associated > format methods). Thoughts? I think this is the right solution. Don't know how much will break because of this though. But hey, if we're breaking things anyway, why not put in Joda time (or maybe scala-time http://github.com/jorgeortiz85/scala-time/tree/master ;-) /Jeppe --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
