Guten Tag Martin Grigorov, am Dienstag, 17. September 2019 um 03:54 schrieben Sie:
> Wicket 7.x is being built with Java 7, not with Java 8. Support to build with Java 8 has been implemented in the past. Why is removing that not a regression? Especially because you don't nail things to JDK 7 like WicketStuff seems to do using toolchains. Your own docs don't distinguish between runtime and building things as well: > This Wicket version requires at least the following Java version: > JDK 7.0 or newer. https://wicket.apache.org/start/wicket-7.x.html#status There are others building Wicket 7 with Java 8 as well and you did commit changes to support that: https://issues.apache.org/jira/browse/WICKET-6615 http://mail-archives.apache.org/mod_mbox/wicket-dev/201811.mbox/%3cabaaada6-4581-e009-607f-4ecd04b88...@meiers.net%3E http://mail-archives.apache.org/mod_mbox/wicket-dev/201811.mbox/%3ccajmbs8jh687unhazbryr+xhejysckkl89mpnk7ysgtmcbre...@mail.gmail.com%3E Doesn't make much sense to commit support for JDK 8 more than once and remove it "silently" afterwards. Especially because the current master for Wicket 9 contains support to be build with JDK 12 and 13 as well instead of JDK 9 only. Any plans to remove that already? :-) Mit freundlichen Grüßen, Thorsten Schöning -- Thorsten Schöning E-Mail: thorsten.schoen...@am-soft.de AM-SoFT IT-Systeme http://www.AM-SoFT.de/ Telefon...........05151- 9468- 55 Fax...............05151- 9468- 88 Mobil..............0178-8 9468- 04 AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
