Hi, Drop java 8 will bring some CVE fixed, but also reduce a common option for users, for this, I will -0.
Maintaining two branch will surely resolve the issue, but this will bring much additional work... For this, I will -1 Although we put 0.13 and 1.x version in our download page, we actually do not maintain the 0.x branch and there is on plan to release a new 0.x version. So, as there is a lot to do with 1.x this year (the table schema, data subscription, tsfile consensus), I prefer not to do the drop this year. Jialin Qiao Christofer Dutz <[email protected]> 于2024年5月17日周五 14:43写道： > > So we have real numbers? > > I also haven't used an oracle jre for quite some time for these reasons. > > Would a double branch strategy work? That the project maintains a 1.x branch > with Javax and Java 8 and a 2.0 branch with Jakarta and Java 11? > > Sort of like we had the 0.x and 1.x branches around? > > Chris > > > Gesendet von Outlook für Android<https://aka.ms/AAb9ysg> > ________________________________ > From: Trevor Hart <[email protected]> > Sent: Friday, May 17, 2024 4:01:14 AM > To: dev <[email protected]> > Subject: Re: [DISCUSS] Drop Java 8? > > I think a lot of organisations are sticking to Java 8 because of the change > to Oracle license that was introduced in Java 11. > > > > If you use Oracle 11 JRE you need to pay Oracle for a license. > > > > This was why Open JDK came about. > > > > Personally I use IotDB with Open JDK 11 (Eclipse Temurin) which does not > require a license. > > > > Thanks > > Trevor Hart > > > > > > > > > ---- On Fri, 17 May 2024 13:30:15 +1200 Yuan Tian <[email protected]> > wrote --- > > > > Hi Chris, > > It seems that a lot of people still use jdk1.8 in their product environment. > > Best regards, > --------------------- > Yuan Tian > > On Thu, May 16, 2024 at 8:10 PM Christofer Dutz > <mailto:[email protected]> > wrote: > > > 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 > >
