Adrian Crum wrote: > > Joda Time claims to fix the problems with the Java date/time API, while > it duplicates the problems in the Java date/time API. The only real > advantage to Joda Time is the additional calendars - which OFBiz already > has in the ICU4J library. > > The author of JSR-310 complains about Joda in the spec and claims that > JSR-310 is better than the Joda Time API. I don't believe JSR-310 will > become a part of the Java spec any time soon. JSR-275 is more mature and > has seen a lot more activity than JSR-310, yet even that doesn't have > enough votes to get it into the Java spec. > > If we actually had a choice, I would vote for using JSR-310 over Joda > Time. The problem is, there is no library that I can find. So far it > appears to be a draft specification only. > > In the meantime we could really use a simple set of date/time classes > that take the guesswork out of handling dates/times. I started with the > Quantity pattern and included some good ideas from JSR-275 and JSR-310. > I believe the result is easy to use and reliable. > > Mini-language has a set-calendar element - maybe that is the end result > of the conversation you were thinking of. >
Ahh that is good info -- what made me think of it was a Java Posse podcast I had been listening to when they were going through some of the proposed Java 7 enhancements. I had remembered them talking about Joda rather favorably at the time. At any rate, I am more than happy to use TimeDuration in its current form and cut over to whatever you provide going forward. If I made an changes I will post them up so we can review and discuss if they have any merit. This conversation has forked quite a bit from its starting point. I think we had agreed that it is probably better to handle "setup" as a separate WorkEffort rather than coupling setup and actual task time in a single WorkEffort. Time constraints as they are, what I am going to do for our project is re-activate the creation of the TimeEntry and only make use of "task time". If one of our customers is interested in "setup" they would create a related WorkEffort and manage it consistently with other WorkEffort entities (in regards to time tracking, estimate, and task time). Once I have something complete I will wrap it up in a patch for you guys to review. This would include UI elements to make use of the TimeEntries that are created in relation to the WorkEffort both in that component and in Manufacturing (as per Jacopo's suggestions). I suspect this thread or its related JIRA will get more legs once I am closer to delivering something. -- View this message in context: http://n4.nabble.com/Regarding-SVN-commit-r892904-tp2018084p2019187.html Sent from the OFBiz - Dev mailing list archive at Nabble.com.
