On Fri, Nov 1, 2024 at 7:17 PM Mark Thomas <ma...@apache.org> wrote: > > On 22/10/2024 15:01, Rémy Maucherat wrote: > > On Fri, Oct 11, 2024 at 9:47 AM Rémy Maucherat <r...@apache.org> wrote: > >> > >> On Thu, Oct 10, 2024 at 10:01 PM <ma...@apache.org> wrote: > >>> > >>> This is an automated email from the ASF dual-hosted git repository. > >>> > >>> markt pushed a commit to branch main > >>> in repository https://gitbox.apache.org/repos/asf/tomcat.git > >>> > >>> commit dac8def47dd9037e050853462612bac37b095ba8 > >>> Author: Mark Thomas <ma...@apache.org> > >>> AuthorDate: Thu Oct 10 12:52:51 2024 -0600 > >>> > >>> Update Jasper to compile to Java 21 by default > >> > >> JDT now produces a weird failure on > >> jakarta.servlet.jsp.el.TestImportELResolver when run on Java 23 (no > >> problem on Java 21). > >> [junit] java.lang.ClassCastException: class > >> org.eclipse.jdt.internal.compiler.lookup.PlainPackageBinding cannot be > >> cast to class org.eclipse.jdt.internal.compiler.lookup.ReferenceBinding > >> (org.eclipse.jdt.internal.compiler.lookup.PlainPackageBinding and > >> org.eclipse.jdt.internal.compiler.lookup.ReferenceBinding are in > >> unnamed module of loader 'app') > > > > This works with JDT 4.30 but 4.31+ fails on Java 23+ (Java 21 works). > > The test is a very simple JSP with a static import, so basically any > > static import seems to cause the issue. > > It has to be a JDT issue since the INameEnvironment.findType works > > just fine in Jasper (up to the point of failure). > > Possibly this: > https://github.com/eclipse-jdt/eclipse.jdt.core/issues/2817 > > I just tested the latest 4.34 integration build and the issue is fixed > so we should be be able to pick up the fix for this JDT bug in > December/January depending on when we tag the December releases.
Nice, problem solved ! Rémy --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
