AFAICT the amount of GWT modules shouldn't noticeably influence the compilation time.
What increases compilation time is lines of code obviously, the amount of permutations that need to be compiled (for example I18n can produce lots of permutations), wether or not you use more than one worker during compilation (parameter -localWorkers) and finally outdated CPUs and RAM shortage (GWT developers should have decent machines to work with, not that 5 year old 3GB Windows 7 notebook). So for production builds or test builds you probably don't care about the compile time as these builds are done on build servers anyways. For the occasional development compiles you can decrease compilation time by limiting permutations to a single one and skip most optimizations by using the -draftCompile parameter. How many lines of client side GWT code does your app have and how many permutations do you produce? A compile time of 8-12 minutes doesn't sound too unreasonable if the app is already large or has lots of permutations. -- J. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
