On Tuesday, May 29, 2012 1:26:10 PM UTC+2, Niraj Salot wrote: > > Hi All, > > What should be consider as Best Practice for Large Project Structure ? > > We have multiple modules inside the projects. Also We would like to > make sure that single change in one module does not require compile of > all the files. It should be just that module only. > > How to achieve this in GWT Project Structure ?
GWT does not provide tools to determine whether a compiled GWT module is up-to-date wrt its sources. If you use Maven though, gwt-maven-plugin<http://mojo.codehaus.org/gwt-maven-plugin/>does it. This is assuming that by "module" you mean a GWT "app" module (one that you give to the GWT Compiler), rather than a GWT "library" module (one that you <inherits/> in an "app" module), because the GWT compilation is "monolithic"; there's no such thing like "incremental compilation" of a GWT app. For a large project, I'd rather modularize the build, as Кирилл Карпенко suggests. Using Maven, you can look at https://github.com/tbroyer/gwt-maven-archetypes as starting point (see http://tbroyer.posterous.com/announcing-gwt-maven-archetypes-project for a quick overview), and then simply create as many `client` module as the number of GWT "app" modules you have. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/MfJ1phiSZqsJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
