Just a quick update. I wrote two blogposts about the topic of "modularizing" your GWT project:
http://ars-codia.raphaelbauer.com/2011/01/gwt-project-layout-part-1-simple.html http://ars-codia.raphaelbauer.com/2011/01/gwt-project-layout-part-2-large.html We are still continuing to improve and fine-tune our setup for many developers. But so far it is a quite nice experience. Using the approach described in the second post it is quite straight forward for new developers to become productive. Feel free to suggest any improvements.. We are really eager to learn and share ideas :) Best, Raphael On Sat, Jan 22, 2011 at 3:02 AM, Raphael André Bauer <raphael.andre.ba...@gmail.com> wrote: > @all: > I just wanted to say "thanks" for your suggestions. I already > successfully separated our initial "fat" project into several lean > independent gwt.xml modules. > > Currently, I am taking the next step mavenizing the modular gwt.xml > modules. M2Eclipse is a huge help to get a productive development > environment (aka workspace dependency resolution). Another challenge > is to make the gwt:run mode work using several maven modules. There is > a nice tip using a maven builder: > http://mojo.codehaus.org/gwt-maven-plugin/user-guide/productivity.html > . If that works as described I am really happy... :) > > Btw: The really cool thing is that Eclipse helps me a loooot to > refactor code. It is really simple and straight forward refactoring > even huge parts of a GWT project. If you have meaningful testcases it > is completely painless and almost fun... > > > I guess I should write a blog post about my experiences and possible > pros and cons when everything is finished. > > > Thanks again for your suggestions! > > Best, > > Raphael > > > > > > On Sat, Jan 22, 2011 at 2:36 AM, Raphael André Bauer > <raphael.andre.ba...@gmail.com> wrote: >> On Thu, Jan 20, 2011 at 8:58 PM, mike b <mbaker.t...@gmail.com> wrote: >>> think about compile times. We have 6 modules on our small project. Compile >>> time for all code including jar, war, and ear files is 7 minutes on a fast >>> quad core 4GB ram machine. IMO the more modules you have, the longer it >>> takes. There might be a better way to optimize (yes, I'm using >>> -localWorkers) but its still pretty long. >> >> Maybe I have a suggestion for you cutting compile times - but I am >> just guessing. You only have to gwt:compile GWT projects with entry >> points (hence war projects). E.g. in the gwt-maven plugin you can >> specify compileTargets. We currently also have a lot of support jar >> gwt projects - but only one war project that will be compiled using >> compileTargets directive. >> >> But - maybe I am wrong as I don't know your project structure... >> >> Cheers, >> >> Raphael >> >>> >>> best of luck! >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Google Web Toolkit" group. >>> To post to this group, send email to google-web-toolkit@googlegroups.com. >>> To unsubscribe from this group, send email to >>> google-web-toolkit+unsubscr...@googlegroups.com. >>> For more options, visit this group at >>> http://groups.google.com/group/google-web-toolkit?hl=en. >>> >> > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
