My mistake!
https://issues.apache.org/jira/browse/WICKET-6219 is applied to 6.25.0 as
well.
I'll release WB 0.9.21!

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

On Fri, Dec 30, 2016 at 6:34 PM, Tobias Soloschenko <
[email protected]> wrote:

> Then let's wait for 7.6.0
>
> kind regards
>
> Tobias
>
> > Am 30.12.2016 um 18:15 schrieb Martin Grigorov <[email protected]>:
> >
> > The issue with the fragments is only with Wicket 7.5.0+
> >
> > On Dec 30, 2016 6:58 PM, "Tobias Soloschenko" <
> > [email protected]> wrote:
> >
> >> Hi,
> >>
> >> currently there is a vote for Wicket 6.26.0 to be released. I guess it
> >> would make sense to build WB with that new version and test it.
> >>
> >> @Martin - WDYT?
> >>
> >> kind regards
> >>
> >> Tobias
> >>
> >>> Am 30.12.2016 um 17:33 schrieb Ronny Pscheidl <
> >> [email protected]>:
> >>>
> >>> Hi,
> >>> but this isn't fixing the issues with bootstrap components which are
> >> using wicket:fragment tag.
> >>>
> >>>> Am 30.12.2016 um 16:47 schrieb Martin Grigorov <
> >> [email protected]>:
> >>>>
> >>>> Hi,
> >>>>
> >>>> You can use older WB with latest Wicket.
> >>>> They are binary compatible.
> >>>>
> >>>>> On Dec 30, 2016 5:43 PM, "john.j.cool" <[email protected]>
> >> wrote:
> >>>>>
> >>>>> Hello,
> >>>>>
> >>>>> when is the release 0.9.21 of wicket-bootstrap planned? we need it
> >> because
> >>>>> of the security issue in wicket prior to 6.25.0.
> >>>>>
> >>>>> john.j.cool
> >>>>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: [email protected]
> >>> For additional commands, e-mail: [email protected]
> >>>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [email protected]
> >> For additional commands, e-mail: [email protected]
> >>
> >>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to