There's a bug in gwt-maven-plugin up to (including) 2.6.0; you have to run mvn process-classes gwt:run-codeserver
instead of just mvn gwt:run-codeserver
. This is fixed in 2.6.1.
Also, if you change anything in src/main/resources
, you'll have to run mvn process-resources
to make your changes available to Super Dev Mode (this is because you might use resource filtering, so Super Dev Mode doesn't directly look at src/main/resources
).
Similarly, if you use plugins that generate resources or Java sources, you'll have to run them manually (e.g. mvn generate-sources
or mvn generate-resources
; or just use the same mvn process-resources
as above, which will do everything at once). This will be necessary for example if you use gwt:generateAsync
and change your GWT-RPC interface (note that you'll also have to redeploy your server-side code).
Note: I just updated my answer in the linked post for GWT 2.6.0, and added a note about GWT-RPC, and the gwt-maven-plugin bug.