Given the fact that nobody officially admits using PLC4X or what they are using it for, we shouldn’t guess that people are using it. So, I’m in favor of dropping 1.8 support and to focus on the use cases that we know of.
I know that some reported issues seem to indicate that some people use 1.8, but I have no idea if that’s just for some experiment. However, some “success stories” being published, definitely would swing my vote, but as long as that’s not happening. +1 on dropping 1.8 support. Chris Von: Christofer Dutz <christofer.d...@c-ware.de> Datum: Freitag, 8. Dezember 2023 um 15:16 An: dev@plc4x.apache.org <dev@plc4x.apache.org> Betreff: [VOTE] Drop Java 1.8 Support Hi all, in the past we have settled with requiring Java 11 for building plc4x and making sure the libraries we build are compatible with Java 1.8. Now it looks as if some of our libraries are no longer runnable on Java 1.8 and we would need one of the following two options: 1. Re-Enable the animal-sniffer-plugin to ensure binary compatability with Java 1.8 and fix the location in the code 2. We officially drop Java 1.8 support As we like to vote with “+1” and “-1”, I therefore start this vote as: Do we want to officially drop Java 11 support? Chris
