I've changed the announcement following Martin's advices. On Tue, Apr 16, 2019 at 11:33 AM Tobias Soloschenko <[email protected]> wrote:
> Hi, > > > Am 16.04.2019 um 10:40 schrieb Martin Grigorov <[email protected]>: > > > > On Tue, Apr 16, 2019 at 11:23 AM Ernesto Reinaldo Barreiro < > > [email protected]> wrote: > > > >> Hi, > >> > >> Apologies for chiming in... > >> > >> On Tue, Apr 16, 2019 at 11:10 AM Martin Grigorov <[email protected]> > >> wrote: > >> > >>> I think we should note that JUnit has been upgraded to 5.x. This is > >>> something that a developer faces quickly. I've updated my app's tests > to > >>> JUnit 5.x as well, but it would be good to know whether just adding > >>> junit-vintage-engine would make it possible to postpone the upgrade of > >> the > >>> application tests. > >>> > >> > >> So... Migration is not so painless as from 7.X to 8.x? Would it be more > >> > > > > I have the feeling that adding junit-vintage-engine to the application > test > > classpath should be enough but someone has to confirm. > > > > > >> correct to call it wicket 11? So, Java 11 is implied? > >> > > > > I think there was a discussion many moons ago and the decision was to not > > follow the Java version. > > > > Yes, that is correct. > > > > >> > >> > >>> Spring is upgraded to latest 5.x, but this most probably won't affect > the > >>> apps. > >>> > >>> > >>> On Mon, Apr 15, 2019 at 9:55 PM Andrea Del Bene <[email protected]> > >>> wrote: > >>> > >>>> Hi, > >>>> > >>>> I'm working on the announcement for 9.0.0-M1. I'd like to have your > >>>> opinion about it and I need your help to better elaborate the "New > and > >>>> noteworthy" section. You can find it on web site repository: > >>>> > >>>> > >>>> > >>> > >> > https://github.com/apache/wicket-site/blob/asf-site/2019/_posts/wicket-9.0.0-M1-released.md > >>>> > >>>> Thank you! > >>>> > >>>> > >>> > >> > >> > >> -- > >> Regards - Ernesto Reinaldo Barreiro > >> > -- Andrea Del Bene. Apache Wicket committer.
