Re: GXT 2.3.1 to 4.0.2 migration

2022-08-05 Thread Lorenzo Aditi
How to change that? It is a .class file (compiled) of a the gxt dependency. I don't have the hand over that. Do you mean creating a class that extends ListField and overriding that method? If so is there a way in java to tell the compiler to use the overidden class instead? Le vendredi 5 août

Re: GXT 2.3.1 to 4.0.2 migration

2022-08-05 Thread Ricardo Serathiuk
Try to change the line 322 of ListField to this: sb.append(m.get(prop).toString()); Em sex., 5 de ago. de 2022 às 16:34, Lorenzo Aditi escreveu: > Hello, > > We used to have GWT 2.4 & GXT 2.2.5 and we migrated to GWT 2.8.1. > > Now I am using GWT 2.8 with gxt 2.2.5 and Jdk 1.8.0_291, even when

GXT 2.3.1 to 4.0.2 migration

2022-08-05 Thread Lorenzo Aditi
Hello, We used to have GWT 2.4 & GXT 2.2.5 and we migrated to GWT 2.8.1. Now I am using GWT 2.8 with gxt 2.2.5 and Jdk 1.8.0_291, even when upgrading gxt-2.3.1a-gwt22 I still get this error when maven is building I got this error jar:file:/war/WEB-INF/lib/gxt-2.3.1a-gwt22.jar!/com/extjs/gxt/ui

Re: [ERROR] Unexpected internal compiler error | BytecodeSignatureMaker.java:59 | at com.google.gwt.dev.Compiler.main(Compiler.java:113)

2022-08-05 Thread Jens
GWT (gwt-dev) depends on ASM 9.2 which supports up to Java 18. On your compile classpath you have gwt-websockets which depends on ASM 5.x. Seems like that ASM version is used during GWT compilation. ASM's ClassVisitor constructor checks the byte code version of the class file and if it is too