On Thursday, May 3, 2012 4:25:58 PM UTC+2, Joseph Lust wrote: > > This topic has been discussed on > SO<http://stackoverflow.com/questions/5079163/gwt-multi-module-vs-single-module-project>and > other places. > > I am familiar with the suggested GWT archatype, but we found it limiting > for large projects. Instead, we (40 devs) use the following Maven project > structure to break up our project: > > > - MainProject.pom > - Client-Interfaces.pom (or POJO's as you put it) > - Client-GWT.pom (frontend GWT code, uses Interfaces) > - Server.pom (backend Java code, uses Client-Interfaces) > - Web.pom (Tomcat settings) > > So just running the main pom will build the interfaces that are then used > by the server side code and the client side GWT. The *Web* project > contains Tomcat specific items and dictates how the *war* is packed up. > *Benefits: *You don't need to rebuild the whole project if changes are > only in your services. Great because services compile in a few seconds, GWT > in several minutes. >
Just a quick note: this is exactly what https://github.com/tbroyer/gwt-maven-archetypes does (except for the server vs. web separation; that's something we did in our project too, but I didn't think it was worth putting into the archetypes: people should just split the module if/when they feel the need for it; I might add it to another archetype though); this is *not* the same as the archetype from the gwt-maven-plugin! Announcement: http://tbroyer.posterous.com/announcing-gwt-maven-archetypes-project -- 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/-/r-lqZNBrjWUJ. 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.
