On 2009-11-23 11.08, Niclas Hedhman wrote:
I think we all know that the java.util.Date class is pretty miserable
in many ways. I hope you all know that there is a solution, called
Joda Time which is a much better thought out time handling package.
I would like to suggest;
- We remove java.util.Date from being used in Qi4j. Use Joda time
instead, for instance for lastModified.
- Strongly discourage java.util.Date usage in Qi4j applications.
We could even "not explicitly supported" for java.util.Date in
serialization (treated as a Serializable), which would quickly move
people away from it.
Opinions?
So, then we would get a hard dependency on Joda Time, right? What is the
usecase that is driving this, and are there any specific cases in the
Qi4j codebase where java.util.Date is causing problems?
/Rickard
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
