Well yes, and no ... Generally, we should be Java 8 buildable (just plc4j) ... however some code had been added to the code generation that broke this "build on 8" feature (at least I know of the "orElseThrow()" usage.
So we could fix this and make it buildable with Java 8 again ... or for the sake of simplicity we simply give up on Java 8 and simply continue to ensure the libraries we build are runnable on 8. Chris -----Original Message----- From: Otto Fowler <[email protected]> Sent: Freitag, 17. Dezember 2021 13:06 To: [email protected] Subject: Re: [DISCUSS] Officially go to Java 11 Just to clarify, we have required Java 11 to build for some time now, but our documentation has still stated java 8 or even both 11 and 8 in different places for a while now. From: Christofer Dutz <[email protected]> <[email protected]> Reply: [email protected] <[email protected]> <[email protected]> Date: December 14, 2021 at 10:38:19 To: [email protected] <[email protected]> <[email protected]> Subject: [DISCUSS] Officially go to Java 11 Hi all, Otto just bumped me about us still referencing Java 8 as minimum version. I think we could be Java 8 compatible, if we only want to build the java part. However as soon as we also build c or go, we need 11 due to the cmake-maven-plugin. Also do we need it in order to build some of the integration modules. So I think instead of investing time into ironing out the Java 8 incompatibilities, I would like to make the minimum version 11 officially. I know that in the past I said, that customers might be needing Java 1.8, but as officially almost nobody admits using PLC4X and we know nothing about the setups people are using we'll simply do a decision on the facts known to us. Right now, this is: * Supporting Java 8 adds more work for me and doesn't bring an advantage that I'm aware of. * Sebastian would love to officially be allowed to use Java 11 goodness Chris
