edit/save/refresh gwt modules

One of the best features of gwt is the edit/save/refresh development cycle. This has worked great when working with only one module. But what about when the application is broken down into multiple modules?

More specifically, we've moved towards a structure where we have a main ui module with an entry point and multiple additional modules which "hook" into it. So the main ui module inherits these other modules (libraries). The GWT Shell is always launched with the main ui, but it doesn't reflect the other module changes on refresh. We have to rebuild and relaunch the shell to see it.

As 开发者_如何学编程gwt is being used to build larger and larger apps, the architecture will tend towards breaking it down into smaller modules rather than one monolithic app. Any suggestions to overcome this limitation?

Thanks much, Mohnish

We do something very similar in terms of using multiple modules in one application. In the command to start the GWT shell we include every module in the argument list and then we are able to see changes to any module with a refresh.

We're using the maven gwt plugin to build our multi-module project. Turns out they have a solution for this posted on their site which works great: http://mojo.codehaus.org/gwt-maven-plugin/user-guide/productivity.html.