Decommissioning is probably a good thing. I know I sometimes get confused between extensions/dateTime as to which one I'm using. But IIRC extensions uses java.util.date and datetime uses joda. How are you going to rectify that part of the merge?
Thanks, Tom Burton -----Original Message----- From: Andrea Del Bene [mailto:an.delb...@gmail.com] Sent: Friday, February 06, 2015 6:54 AM To: dev@wicket.apache.org Subject: Re: Decommission of wicket-datetime Yes of course :) > ... and move the remaining YUI packages to wicketstuff-yui ? > > Sven > > On 06.02.2015 16:22, Andrea Del Bene wrote: >> I see. Also the two DateTextField have no functional difference. This >> is in short what I would do: >> >> Remove: >> /wicket-datetime/src/main/java/org/apache/wicket/datetime/DateConverter.java >> >> >> Move to wicket-utils: >> /wicket-datetime/src/main/java/org/apache/wicket/datetime/PatternDateConverter.java >> >> >> /wicket-datetime/src/main/java/org/apache/wicket/datetime/StyleDateConverter.java >> >> >> >> Move to wicket-extensions: >> /wicket-datetime/src/main/java/org/apache/wicket/datetime/markup/html/basic/DateLabel.java >> >> >> >> Merge wicket-datetime DateTextField into the existing >> wicket-extensions DateTextField. The first one has a DateConverter as >> constructor parameter which is used internally instead of a more >> generic IConverter<Date>. it would be nice to have single component >> with the same constructors of the existing two. >> >> What do you think?
