Hi all, starting this new thread as I am not sure if others are reading the Jakarta migration thread.
I would like to propose planning on dropping Java 8 support. I wouldn’t immediately do that, and I would also propose to do a major version update (Switching to 2.0.0) We could still maintain a 1.x branch for those people not able to update. The main reason is that we are currently blocking ourselves from updating many major plugins and dependencies. I noticed that when updating to the Jakarta namespace. Here there is no Netty version available that supports Jakarta and supports Java 8. Other libraries where we are not able to update without giving up on Java 8: * Airlift-Units (Stuck at 1.7 current 1.10) * Airlift * Antlr (Stuck at 4.9.3 current 4.13.1) * Caffeine (Stuck at 2.9.3 current 3.1.8) * Logback (Stuck at 1.3.14 current 1.5.6) * Mockito (Stuck at 2.23.4 current 5.12.0) * Thrift (Stuck at 0.17.0 current 0.20.0) * Spotless Plugin (We’ve got a workaround for Java 8) In my branch where I refactored the javax namespace to Jakarta after updating dependencies I was able to remove all exclusions of the BanVulnerableDependencies check. Also does dropping Java 8 and the Jakarta migration allow embedding IoTDB in recent Spring versions. So … what do you think? Chris
