Yeah, I understand your concern for supporting the legacy applications especially for such users who have been using it in the production environment. But from the point of innovation, I think it would be great to use the latest JDK which has many new impressive features. And sooner or later, we still have to face the problem of dropping JDK 8. So why don't we consider it for now?
I don't think 200+ modules is a BIG problem for maintaining work. You can see Apache camel which has 500+ modules but still supports 3 LTS versions. There could be some way to help us to do backporting work such as using a github bot. Anway, I also think it would be an opportunity to think about the RoadMap of shardingsphere. Thanks, Zheng Feng zhangli...@apache.org <zhangli...@apache.org> 于2023年1月13日周五 14:42写道： > There are lots of legacy applications still using Java 8. > ShardingSphere-JDBC is a java lib, not standalone process, the LTS of Java > 8 is necessary. > > But there are 200+ modules in ShardingSphere, so I am afraid nobody > can undertake the costs of maintain 2 different versions. > > ------------------ > > Sincerely, > Liang Zhang (John) > Apache ShardingSphere > > > 吴伟杰 <wuwei...@apache.org> 于2023年1月12日周四 10:57写道： > > > I also want to use the Java 11 or 17. > > We have had to do some special handling in codes to avoid performance > > issues in Java 8 (such as JDK-8161372 [1]). > > > > [1] https://bugs.openjdk.java.net/browse/JDK-8161372 > > > > Regards, > > Weijie > > ----------------------------------------------- > > > > Wu Weijie 吴伟杰 > > Apache ShardingSphere PMC > > GitHub@TeslaCN > > > > Zheng Feng <zhf...@apache.org> 于2023年1月11日周三 20:18写道： > > > > > > > > Hi all, > > > > > > This thought is coming from upgrading antlr to 4.10.1 [1] which is only > > for > > > Java 11 now. Currently it looks like that the Hibernate 6.0.x [2] and > > > Quarkus 2.15.x [3] integrations has been blocked by this upgrading > issue. > > > > > > I think it could be some other 3rd party libraries with this similar > > issue > > > sooner or later. So it is time to think about the plan to drop JDK 8 in > > > shardingsphere now. > > > > > > I know this is BIG breaking change that could impact a lot of people > who > > > use the shardingsphere. Also it is not very clear in current roadmap > [4] > > > and the document for support JDKs. > > > > > > So my plan is to keep 5.x branch which sticks to JDK 8 and should be a > > LTS > > > version (I'm not sure how long we will be like to support it?). Then > bump > > > the master branch to 6.0 to drop JDK 8 support as soon as possible. > There > > > will be a little bit much more maintenance works with 5.x and master > > > branches. > > > > > > What the others think? and we definitely need a formal voting process > for > > > this plan after this discussion. > > > > > > Regards, > > > Zheng Feng > > > > > > [1] https://github.com/antlr/antlr4/releases/tag/4.10.1 > > > [2] https://github.com/apache/shardingsphere/pull/20119 > > > [3] > https://github.com/quarkiverse/quarkus-shardingsphere-jdbc/issues/84 > > > [4] > > https://shardingsphere.apache.org/document/current/en/overview/#roadmap > > >
