On Fri, Sep 3, 2021, 12:08 Korbinian Bachl <korbinian.ba...@whiskyworld.de> wrote:
> Apologies for hijacking this, but can we assume now the following? > > wicket 8: java 8 + java apis + servlet 3.1 + jQuery > wicket 9: java 11 + java apis + servlet 3.1 + JQery > wicket 10: java 17 + jakarta apis + servlet 5.x + no jQuery > So far no one is going to remove jQuery > ?? > > > ----- Ursprüngliche Mail ----- > > Von: "Andrea Del Bene" <an.delb...@gmail.com> > > An: "dev" <dev@wicket.apache.org> > > Gesendet: Freitag, 3. September 2021 10:45:03 > > Betreff: Re: Wicket 10 based on jakarta.** APIs ? > > > not a big deal imho :-) > > > > On Fri, Sep 3, 2021 at 9:47 AM Martin Grigorov <mgrigo...@apache.org> > wrote: > > > >> On Fri, Apr 2, 2021 at 2:58 PM Martin Grigorov <mgrigo...@apache.org> > >> wrote: > >> > >> > Hi, > >> > > >> > Now since we have 9.3.0 released is it time to start thinking/working > on > >> > Wicket 10 ? > >> > > >> > Here are few ideas what to break :-) > >> > > >> > 1) Move to Servlet 5.x, i.e. jakarta.servlet.** > >> > 2) Use @Inject + @Named instead of @SpringBean. If everything is > covered > >> > by @Inject we may deprecate @SpringBean in 9.x > >> > 3) Depending on the release date we may even bump Java to 17 (it is > going > >> > to be released this September and it is going to be LTS). I expect > Wicket > >> > 10.0.0 to be released in 1-2 years from now, so by this time Java 17 > >> should > >> > be mainstream! :-) I know that this is too brave. Most projects still > use > >> > Java 8 for some reason. > >> > > >> > >> Spring people announced their plans for supporting Jakarta EE - > >> > >> > https://spring.io/blog/2021/09/02/a-java-17-and-jakarta-ee-9-baseline-for-spring-framework-6 > >> It is planned for Q4 2022 and it will require Java 17 ! > >> > >> It seems we will be forced to require Java 17 too. > >> > >> > >> > Regards, > >> > Martin > >> > > >> > > > > > > -- > > Andrea Del Bene. > > Apache Wicket committer. >
