I believe we don't need to stress much since all our dependencies
(except one) are still compatible with Java 1.8.
I agree that we can switch to Java 11 when 1.8 fades away. This change
does not cost us much cause we develop (as life shown) mainly on 11 already.
Long time ago Java 11 was issue for Karaf, now it shouldn't be a case.
Best,
Łukasz
On 21.09.2021 10:30, Christofer Dutz wrote:
Hi all,
up to now PLC4J has been built in a way, that we can run PLC4J applications on
VMs down to Java 1.8. Initially the main reason for sticking to 1.8 was that I
knew that a lot of edge devices simply only supported Java 1.8. This might have
changed.
Currently Java 11 seems to be the version a lot of other projects are
targetting. I would strongly suggest that we not target any newer versions, in
order to not exclude too many plaforms form using PLC4J.
I just had a look at the support roadmap of LTS versions from Oracle:
1.7 has ended premier support, but extended support is still available.
1.8 will be ending premier support next March (2022) and extended support is
available till December 2030
11 will be ending premier support on Septermber 2023 and extended support on
September 2026
17 will be the next LTS version with premier support till September 2026 and
extened support till September 2029
Would like to reach an agreement before investing too much time in addressing
the OPC-UA test issue with Java 1.8
My general opinion would be to stay compatible with 1.8 for now and to fix the
issue and to move up to 11 as soon as support runs out some time next year.
Christ
