Re: Decommission of wicket-datetime

Mon, 09 Feb 2015 05:20:37 -0800

Sorry, I was mistaken by another pair of namesake classes named DateConverter.... DateTextField from extensions module uses DateConverter from utils module, not the one from datetime. So in short, I agree to decommission datetime and move it as it is to wicketstuff. The only minor thing I'm concerned of is that DateConverter from utils doesn't seem to be able to take the time zone difference between clients and the server into account. So it might be nice to keep such a DateConvert as part of Wicket distribution. It would be easy to add another date converter for this purpose (for example TimeZoneDateConverter) coping the one from datetime. The only downside of this solution is that we must move the dependency on Joda to utils module... 
I was thinking:
a) move the module from Apache Wicket master branch to WicketStuff master
branch
b) explain in the migration guide that the Maven dependency and the package
names have changed from X to Y

But with all the suggestions to move and merge classes I am not so sure
that the migration process will be very smooth for the end user

Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov

On Sun, Feb 8, 2015 at 4:42 PM, Andrea Del Bene <[email protected]>
wrote:

Reply via email to