Ooops, there is a few copy paste typo's in the module-X.gwt.xml naming below... please forgive me and ignore the inappropriately named .gwt.xml files :)
On Fri, May 21, 2010 at 3:53 PM, Andrew Hughes <[email protected]> wrote: > Like most projects, our GWT client is getting pretty big and it would > sensible to break it up into several maven modules. > > For example: > > +parent > +server (jar) > +shared (jar, with source attached) > +client-a (jar, with client-c.gwt.xml) > +client-b (jar, with client-c.gwt.xml) > +client-c (jar, with client-c.gwt.xml) > +client (war, with client.gwt.xml) > > If I run "gwt:run" (to launch the gwt development mode) from the "client" > module I won't see any hot code changes from modules client a,b and c (will > I???). It won't get the new code until I close the dev console, run mvn > install and re-run "gwt:run". Please tell me that I am completely wrong and > this is not the case. Dividing up our gwt client into modules seems good in > theory, but I don't want to it to be detrimental to the development mode. > > Cheers :) >
