Compatibility of GWT 2.10.0 with GXT 2.3.1.a

[priyako...@gmail.com]

Hello Team,

we use following jars in our application - 

GXT .jar -        2.3.1.a

GWTx.jar -       1.5.3

Log4j-gwt.jar - 1.0

Wanted to know that will recent update of GWT 2.10.0 compatible with above dependencies.

[Leon Pennings]

From what I gathered, packages have been renamed from **.google.** to **gwtproject** or smth.

So without a gxt update to cover for the new packages, I doubt you can upgrade your project.

There is one simple way to check, just update the GWT version in your dependency manager (maven or whatever you use) and you'll find out soon enough.
 

Op maandag 18 juli 2022 om 06:56:23 UTC+2 schreef priyako...@gmail.com:

[Frank Hossfeld]

GWT packages have still the same name. AFAIK, there are no changes on package names.

In case you start using GWT modules, you will have to use the packages starting with 'org.gwtproject'. 

Starting with GWT 2.10.0 you can 'com.google.gwt' or 'org.gwtproject' as groupId inside the Maven dependency. Starting with one of the next release of GWT, only the 'org.gwtproject' groupId can be used.  

[Thomas Broyer]

In an ideal world, you'd reach out to those libs' maintainers and ask them if their lib is compatible with GWT 2.10.

But those are all libs that haven't had a new release in a decade:

* GXT 2.3.1.a was released in 2014

* GWTx 1.5.3 was released 2009 (GWT 2.0.0 wasn't even released at the time!)

* log4j-gwt 1.0 was released in 2012

You're quite fortunate that GWT has a rather extraordinary backward compatibility track and such a combination might still work with 2.10.0, but nobody in their own mind should even try that unless they're desperate.

If you're going to spend time on something, spend it on removing those outdated, unmaintained libs (you had between 8 and 13 years to do it already, but it's never too late). Stay on an older GWT version for as long as you can, but remove those libs (if you share code with the JVM that uses log4j –still using log4j 1.x? hope you migrated to reload4j–, then rewrite/copy the few bits that need to be emulated; for GXT and GWTx, replace with your own code or possibly another –maintained– lib).

If the project isn't worth it, then it's probably not worth either spending time updating to GWT 2.10 and make sure everything still works.

So first, let me ask: why do you want to update to GWT 2.10?

[Ricardo Serathiuk]

I work with an application using GWT 2.10.0 and GXT 2.3.1a. We have fixed some things on GXT 2.3.1a. With some fixes, you can run perfectly the GXT 2.3.1a in GWT 2.2+ (GWT 2.9.0 and 2.10.0 included).

[mmo]

> We have fixed some things on GXT 2.3.1a.  With some fixes, you can run perfectly the GXT 2.3.1a in GWT 2.2+ (GWT 2.9.0 and 2.10.0 included).

Would you mind to elaborate on these fixes? Have you documented these somewhere?

[Ricardo Serathiuk]

I have explained in another similar thread the steps:

https://groups.google.com/g/google-web-toolkit/c/IZRriHLTWxA/m/DIerF5bzAgAJ

Tips:

* You need to use this jar: https://mvnrepository.com/artifact/com.extjs/gxt/2.3.1a-gwt22

* Extract the jar source code (.xml and .java files, remove all .class files) and create an internal project with the source code.

* Try to see the errors and fix one by one.

* In com.extjs.gxt.ui.client.image.XImages, change its to extends ClientBundle and change all to AbstractImagePrototype ImageResource. After that, fix all errors.

* Most of the errors are about setHeading, AbstractImagePrototype and the com.google.gwt.user.client.Element deprecation.

I have made all the core changes in a day. And some fixes and improvements during the years. I do not remember all the changes, but it is a guide to start.

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-tool...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/a4aa86c7-d74a-48ef-a6c0-d687be2018aan%40googlegroups.com.

--

Ricardo Serathiuk

[Michael Conrad]

If you publish your work to a jitpack compatible public git repo and then follow the jitpack.io instructions, you could provide a Maven/Gradle ready dependency for others to use.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/CALVte5xy9Hdi%2BmykRRbXwOvdsa8DKPi_Q%3Dy8rJ94SxOwNkQhFA%40mail.gmail.com.

[Ricardo Serathiuk]

With an authorization of the Sencha and my company, I do it. :)