[jira] [Resolved] (WICKET-6105) Decommission wicket-datetime

["Maxim Solodovnik (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/WICKET-6105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maxim Solodovnik resolved WICKET-6105.
--------------------------------------
    Resolution: Fixed

> Decommission wicket-datetime
> ----------------------------
>
>                 Key: WICKET-6105
>                 URL: https://issues.apache.org/jira/browse/WICKET-6105
>             Project: Wicket
>          Issue Type: Task
>          Components: wicket, wicket-datetime
>    Affects Versions: 8.0.0-M1
>            Reporter: Martin Grigorov
>            Assignee: Maxim Solodovnik
>             Fix For: 8.0.0-M8
>
>
> Discussion at dev@: http://markmail.org/message/uqu6gfma6wihwcwt
> The idea is to:
> * preserve DateConverter classes in wicket-util (and use Java 8 java.time.** classes instead of Joda-Time).
> * move DateLabel to wicket-extensions
> * synch -datetime's DateTextField with -extensions' DateTextField
> * move everything else in WicketStuff project so existing applications could easily migrate to Wicket 8
> there are many topics to improve on:
> - DateConverter should be name DateTimeConverter and convert to LocalDateTime
> - DateField should work on a LocalDate (no longer extending DateTimeField)
> - without the DatePicker we could merge DateField and DateTextField
> - TimeField should work on a LocalTime (no longer extending DateTimeField)
> - for DateTimeField we should consider whether it works on ZonedDateTime or LocalDateTime - AFAIK most people use the former



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)