I tried these options to make GWT compilation faster: in the build.xml, "compile_gwt" target I added <arg line="- localWorkers 3"/> option - this means that now 3 cores will be used to compile the source. I personally find that the number of cores dedicated to compilation that give the best performance should be n-1, where n is the number of cores available in your computer. Also, in WebClient.gwt.xml , I uncommented the line <!-- <set-property name="user.agent" value="safari" /> --> I work with Firefox so I changed 'safari' to 'gecko1_8'.
On Oct 19, 10:44 am, Alex North <[email protected]> wrote: > The WebClient.gwt.xml was recently fixed to produce all the necessary > permutations (29) for a production build. This is necessary for good > browser > support, etc, but is really slow for development (with typically just one > browser most of the time). The compile_gwt ant target adds -style PRETTY > which makes the JS larger than it should be. > > Is it possible to set GWT properties in the ant file, so we could have a > build target that restricts to chrome/safari? > > - compile_gwt: unrestricted, no logging > - compile_gwt_dev: safari, PRETTY, logging enabled -- You received this message because you are subscribed to the Google Groups "Wave Protocol" group. 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/wave-protocol?hl=en.
