I see that Wicket 8.0.0 is already at Maven Central, so I will make a release of wicket1.5-tree !
On Tue, May 22, 2018 at 5:17 AM, Maxim Solodovnik <solomax...@gmail.com> wrote: > Hello All, > > While preparing wicketstuff release I noticed inmethod-grid depends on > `wicket15-tree` > Can someone release `wicket15-tree` ? > > On Mon, May 21, 2018 at 5:14 PM, Martin Grigorov <mgrigo...@apache.org> > wrote: > > On Mon, May 21, 2018 at 1:12 PM, Sven Meier <s...@meiers.net> wrote: > > > >> Hi, > >> > >> Martin moved the implementation to wicketstuff, so developers can still > >> use the old implementation in their project. > >> > >> I've fixed some things so it is still working with Wicket 8: > >> > >> https://github.com/wicketstuff/wicket1.5-tree/commits/master > >> > >> wicket1.5-tree isn't part of wicketstuff-code because - as its name > >> implies - it is legacy and people should move away from it. > >> > > > > Let's release a new version once Wicket 8.0.0 is at Maven Central. > > As Sven explained there is no reason to be part of wicketstuff/core and > to > > cut releases for it regularly. > > > > > >> > >> Have fun > >> Sven > >> > >> > >> > >> Am 21.05.2018 um 11:55 schrieb Maxim Solodovnik: > >> > >>> I can't see recent commits here: > >>> https://github.com/wicketstuff/core/commits/core-1.5.x .... > >>> > >>> On Mon, May 21, 2018 at 3:26 PM, Andrea Del Bene <an.delb...@gmail.com > > > >>> wrote: > >>> > >>>> hi, > >>>> > >>>> I've seen Sven lately did some work on this module, but I don't > >>>> understand > >>>> why its code is separated from the rest of WicketStuff project. In > this > >>>> way > >>>> it cannot be deployed to maven repository as part of WicketStuff > project. > >>>> Is it like this on purpose? > >>>> > >>> > >>> > >>> > >> > > > > -- > WBR > Maxim aka solomax >
