Porting a Google Web Toolkit Netbeans Project (GWT4NB) to the Latest GWT and GWT4NB
A while ago I was blogging about some experiences with the Google Web Toolkit (GWT) and Netbeans.
I reported on the existence of a great plugin (GWT4NB) that GWT-enables your Netbeans (starting from NB 6.5).
Well today I upgraded to NB 6.7 (from 6.5), to GWT4NB 2.6 (from 2.0.4) and to GWT 1.7 (from 1.5.3) and could not compile my GWT project anymore. Here are the steps I went through to make it run again:
- Create an new empty Web project. When Netbeans asks you what framework you’d like to use (last sept of the wizard) select the Google Web Toolkit.
- Be sure that the GWT Installation Folder points to the latest version of GWT (1.7 in my case).
- Copy the content of both:
build-gwt.xmlandgwt.propertiesto these files in your old project. - Make sure you keep the entry
gwt.module=...of your old project. - You might need to check the properties of the old project and make sure the “Frameworks” entry is referencing the latest version of GWT.
This should do, you should now be able to run and compile the old project with the latest GWT and GWT4NB plugin (at least it worked for me!).
Also note there is a bug in the (new) generated build-gwt.xml for GWT4NB 2.6.9 (and probably earlier) where the -war option is not being supplied to the target debug-connect-gwt-shell-17 (and other versions).
You’ll need to add the following argument to that target (eg at line 373 of the build-gwt.xml produced by GWT4NB 2.6.9)
Thanks for your post, it got me going long enough to find this bug (which I’ll register with the GWT4NB crew).
Let’s try that again (adding HTML &nn; codes by hand):
<arg value=”-war”/>
<arg path=”${build.web.dir}/”>
Thanks for that Mike!
Thanks that helped. In the last line the /” should be the otherway round “/