Hi,

The migration guide is still very short, i.e. there are no many changes in
master branch yet:
https://cwiki.apache.org/confluence/display/WICKET/Migration+to+Wicket+8.0
There are some changes in branch lambdas (
https://github.com/apache/wicket/tree/lambdas) which have to be evaluated
and eventually merged to master.

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

On Fri, Jan 8, 2016 at 1:57 AM, Sven Ludwig <[email protected]> wrote:

> Hi!
>
> it has been a while. I just checked
> https://cwiki.apache.org/confluence/display/WICKET/Ideas+for+Wicket+8.0
> and https://wicket.apache.org/start/wicket-8.x.html
>
> Can you provide a few links or pointers to commits, classes, methods,
> tests or functional interfaces (just as you see fit) regarding specifically
> the support for Lambda handlers?
>
> I would really like to have a closer look if code already exists and I
> would prefer to start with a hint from one of the devs.
>
> Kind Regards,
> Sven
>
>
> On 25.10.15 at 02:57, Mihir Chhaya wrote:
>
> > Thanks for the reply.
> >
> >
> >
> > -Mihir.
> >
> >
> >
> > On Sat, Oct 24, 2015, 8:18 AM Martijn Dashorst <
> [email protected]>
> >
> > wrote:
> >
> >
> >
> > > No. I don't think it will be in 6 months. We might do some milestones.
> >
> > >
> >
> > > We'll be sure to get Java 8 features right.
> >
> > >
> >
> > > Martijn
> >
> > >
> >
> > > On Saturday, 24 October 2015, Mihir Chhaya <[email protected]>
> wrote:
> >
> > >
> >
> > > > Hello,
> >
> > > >
> >
> > > > On apache wicket website download section, there is link for wicket 8
> >
> > > > snapshot. Just curious; is there planned or projected date decided
> for
> >
> > > the
> >
> > > > final release?
> >
> > > >
> >
> > > > Thanks,
> >
> > > > -Mihir.
> >
> > > >
> >
> > >
> >
> > >
> >
> > > --
> >
> > > Become a Wicket expert, learn from the best: http://wicketinaction.com
> >
> > >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to