GWT 2.6 is just over a decade old - while Java 8 didn't exist at the time it was first released, I see you're still using it. Latest GWT is 2.12, and requires a minimum of Java 11. The first step then is probably to update GWT as high as you can without breaking other things, then update Java to some recent version, then update GWT to latest.
GWT 2.6 supported an early version of Super Dev Mode - assuming that is what you were using, the way to use it has changed a bit, but is still present. No browser supports legacy Dev Mode (which used a browser plugin), so if you were using that, you'll need to set up some new dev guidelines for how to debug your application. GXT 3 has always been paid, but at that time they were still releasing GPL versions, so that is what you are using. It is likely to have problems running with newer than about GWT 2.8, but the fix is easy (and since it is GPL, you can edit that yourself, just change the broken call to getResourceMap().get... with .getResource... ). I've never used netbeans except as an experiment, and can't really help there. I pay for my own IDEA ultimate version, though not for the GWT support - you can either use the community edition, or Eclipse with the GWT plugin, but will need to make your own decision. One other topic not mentioned - a project from that era is likely using ant, and probably should be updated to Maven or Gradle. Quick recap using your numbering: 1. Aim for GWT 2.12, but you probably need to pause briefly at GWT 2.11 until you can drop Java 8. 2. Super Dev Mode - you do not need a browser plugin for this or specific IDE tools (unless you want them), just anything that can debug JS with sourcemaps to show the original Java. 3. Up to your own preferences, requirements - anything that can edit Java and understand your project setup should suffice. 4. Aim for Java 21+, but wait until you are using GWT 2.11, and then figure out what it is going to take to get your server updated too - likely that will be a bigger hurdle. 5. Actively developed UI toolkits I'm aware of include DominoUI and DnComponents 6. Payara still exists and is maintained. There are other good choices too. Without understanding your server code or requirements, one can't easily answer this. Odds are, updating the server is going to be a bigger task than updating the client. 7. Separation is a good idea, but not absolutely required. There are many benefits you will see here, from avoiding many classes of bugs, to faster compilation. As you consider your build system, also consider if this is some tech debt that can be paid down now and help your project going forward. Please email me off-list at co...@vertispan.com if you're looking for more guidance or assistance - our company regularly helps with projects like this, keeping existing projects alive by updating them without requiring a total rewrite with each platform shift. On Wednesday, February 5, 2025 at 6:48:58 AM UTC-6 at10...@gmail.com wrote: > Hi, > > We have a project with mixed architecture of client + shared + server > (RPCs). with following configurations: > 1. gwt-2.6.1 > 2. gwt4nb plugin > 3. jdk 1.8 > 4. gxt 3.1.1 (sencha) > 5. payara web server > 6. netbeans 18 > > > We want to upgrade the project in the latest version of GWT. we request > you to please suggest on the followings: > 1. gwt version we must choose? > 2. how will we achieve client debugging (as currently we are using > gwt4nb-plugin for the same.)? > 3. Which open-source IDE we should opt? > 4. Suitable jdk version? > 5. Alternative of sencha (as it is paid now, and we are only limited to > its grid control). > 6. Should we continue with payara? > 7. Do we require splitting of client, shared, server in separate projects > or we should continue the same architecture (as this is a quite big > project). > > > > > > -- 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-toolkit+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/8b555500-88c2-4b95-a231-484b8a0168f0n%40googlegroups.com.
