But wasn't that the hole point of the renaming change from wicket 1.4 / 1.5 to
wicket 6, wicket 7, wicket 8?
I myself dont give anything about version numbers anyway, just curious ....
----- Ursprüngliche Mail -----
> Von: "Martin Grigorov" <mgrigo...@apache.org>
> An: email@example.com
> Gesendet: Montag, 16. April 2018 16:37:04
> Betreff: Re: [DISCUSSION] Java future and Wicket
> I think we should not relate Wicket version to anything.
> Wicket 9 will be released when there is enough new features. And the team
> decides when enough is enough.
> It should be build with the latest LTS JDK whatever it is at the moment.
> The version of EE4J / Servlet specs are also not relevant to Wicket's
> On Mon, Apr 16, 2018 at 4:03 PM, Korbinian Bachl <
> korbinian.ba...@whiskyworld.de> wrote:
>> Maybe stupid question but: why not align with Java EE?
>> -> Java EE8 relies on JDK8, not JDK 9 - and wicket 8 relies on JDK 8
>> -> Java EE9 (or whatever naming scheme comes) might rely on Java 11 lts ->
>> so align wicket 9 (or whatever EE naming scheme) with JDK 11?
>> In the end the Java version itself is not so imprtant for Wicket as IMHO
>> the EE is as its all in EE space in view to the web-server-side...
>> (wicket needs servlet and thats part of EE)
>> ----- Ursprüngliche Mail -----
>> > Von: "Martijn Dashorst" <martijn.dasho...@gmail.com>
>> > An: firstname.lastname@example.org
>> > Gesendet: Montag, 16. April 2018 11:52:55
>> > Betreff: [DISCUSSION] Java future and Wicket
>> > All,
>> > With the new release schedule of Java where they will (have)
>> > release(d) Java 9, 10 and 11 in one year, what will we do with
>> > Wicket's dependency on Java?
>> > Will we move with the Long Term Support versions? AFAIK this will
>> > require us to upgrade every year to a new major version.
>> > Or will we stay with LTS-- as our major supported Java version?
>> > If so, how do we work with deprecated technologies that we (or our
>> > dependencies) use when they get removed, or Wicket plain stops working
>> > on Java 10 (or Java 11), or stops building on one such version?
>> > In the long run, I don't think it is possible for us to align Wicket
>> > versions with major Java versions as we could in the previous years:
>> > - wicket 1.5 -> Java 5 (actually Wicket 1.4, but who's counting)
>> > - wicket 6 -> Java 6
>> > - wicket 7 -> Java 7
>> > - wicket 8 -> Java 8
>> > would the next major version of Wicket be 11?
>> > - wicket 11 -> Java 11?
>> > Martijn