On Mon, Jan 3, 2022 at 12:32 PM Mark Thomas <ma...@apache.org> wrote: > > On 03/01/2022 11:20, Rémy Maucherat wrote: > > On Mon, Jan 3, 2022 at 11:53 AM Rainer Jung <rainer.j...@kippdata.de> wrote: > >> > >> For reference: this is probably the ticket about moving JDT (and ECJ) to > >> Java 11: > >> > >> https://bugs.eclipse.org/bugs/show_bug.cgi?id=572389 > >> > >> And this is the parallel mail discussion: > >> > >> https://www.eclipse.org/lists/eclipse-dev/msg11703.html > >> > >> If we roll back the change for TC 10.0 and 9, there is also the later > >> change about JSP compilation for Java 17/18 that was depeding on the ECJ > >> update. > > > > Well, this is a big problem since we plan to support Tomcat 9 for a > > very long time and there's now no way to update JDT :( > > Any ideas ? > > I think we have options.
Ok :) > JDT bugs that affect JSP compilation are rare as are security bugs. On > that basis, the likelihood of an update being required is low. > > Tomcat 8.5.x has been stuck on ECJ 4.6.3 (last Java 7 version) since > 2017 and that hasn't been an issue so far. > > I don't think we have said Tomcat 9.10.x etc will continue to have Java > 8 as a minimum. It is the Java EE 8 API we are looking to retain and > while java EE 8 does specify Java 8 as a minimum I think we have a case > - in terms of extended support - to update that if we need a newer > version of Java in order to update a dependency we need to update. Indeed, nothing was said about keeping 9.x on Java 8. Now that I think about it, it would be annoying to do it as we would need to rewrite more code. > Users always have the option of replacing the ECJ JAR that ships with > Tomcat with a new (or older) version. Whatever we decide to do as the > default, users will always have the option to use a different ECJ JAR. > > Actually, using an older version might be tricky as we use the newer > constants but if we keep that in mind for 9.10.x onwards we could ship > with a newer ECJ and leave the option open for users to downgrade. Overall, I still think this is bad news, but you convinced me it could work ... > Sort of related, I am wondering about the build environment. We have > seen an issue with downstream building with Java 11 and there are > difficulties building 8.5.x particularly with a clean install of the > latest publicly available Java 7. What about switching all versions to > building with Java 11 and using the release compilation option to set > the appropriate Java API to build against? Does that work for avoiding the ByteBuffer problems ? Rémy --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
