And jar size doesn't really matter on the server, does it? I find that argument pretty much a non-issue.
I don't like the fact that we are going to depend on a library and find out that in Java 7 it is no longer necessary (it is now a JSR). The problem is that they are not rubberstamping Joda but again doing a whole committee thing. This would mean new api's etc. At least with concurrent.jar they just rubberstamped the lot and incorporated it in java 5. Even though java.util.Date and java.util.Calendar are not perfect, they are the most used date implementations available and for instance Hibernate/JDBC/ibatis/etc. works directly with that. For such bindings you have to resort to yet another library/dependency if I'm not mistaken. I'm -0 for core, but +1 for extensions. It is not that we want to change the world by making the whole Java experience better, just the HTML serving part. Adding it to extensions and seeing the response to that will give us time to mature it and see if we can build more on top of it. Martijn On 2/3/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
why is it so big? complete wicket is 1.5 so only some date manipulations are 1/3th? johan On 2/2/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > > Hi all, > > For those who don't know, Joda Time: http://joda-time.sourceforge.net/ > is a *much* better replacement of the Java date and time APIs it many > ways (see their 'why Joda time section'). Also, Joda time will be the > basis of JSR 310 (http://jcp.org/en/jsr/detail?id=310). > > Date/ time handling wouldn't normally be part of Wicket's > responsibility, wouldn't it be the fact that our date related > components suffer from the JDKs API being bad. I wrote some components > and a converter based on Joda time that work better than the current > ones we have. The most important feature of those components is that > they take the client's time zone into account. I've tried to write > them against the normal date/time API, but got so sick of battling it > that I gave up. And as soon as I adopted Joda time (which we were > already using for our project), it worked superb! > > My proposal is to include Joda time as a dependency of the wicket core > project. I know *any* extra dependency raises eyebrows and I feel > great about Wicket hardly having any dependencies at the moment. > However, I feel this library is so good and could improve our core > components and converters so much that it is worth having the extra > dependency. > > Joda time is a maven 2 project, is Apache 2.0 licensed, and version > 1.4 is 512KB. > > Your thoughts/ votes? > > Eelco >
-- Vote for Wicket at the http://www.thebeststuffintheworld.com/vote_for/wicket Wicket 1.2.4 is as easy as 1-2-4. Download Wicket now! http://wicketframework.org
