Hi Tobias, I didn't get your idea. Clirr checks against Wicket 7.0.0. It is 7.0.0 because all 7.x should be binary backward compatible. Even if you move the target it would be the same because it would be transitive.
Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Tue, Sep 27, 2016 at 2:39 PM, Tobias Soloschenko < [email protected]> wrote: > Hi Martin, > > can we register a new jar for the clirr check after the next release - or > is the last jar used to do the clirr check? Then it would be for one > release that there is a clirr issue and after this it would be fine. > > kind regards > > Tobias > > > Am 27.09.2016 um 14:17 schrieb Martin Grigorov <[email protected]>: > > > > Fixed! > > > > It seems the backport from 8.x (master) broke it. > > The generics are fine with JDK 8. > > > > But now there is broken Clirr because of Csrf request cycle listener > > > > Martin Grigorov > > Wicket Training and Consulting > > https://twitter.com/mtgrigorov > > > > On Tue, Sep 27, 2016 at 2:07 PM, Martijn Dashorst < > > [email protected]> wrote: > > > >> In ApplicationSettings this fails. Both in Eclipse and maven. > >> > >> Martijn > >> > >> -- > >> Become a Wicket expert, learn from the best: http://wicketinaction.com > >> >
