It looks like we can't use parameters in the ant build file to set properties. The recommended way is to make another .gwt.xml file which wraps the real one (includes it), and sets any additional properties, like the ones below.
-J On Wed, Oct 20, 2010 at 9:16 AM, Joseph Gentle <[email protected]> wrote: > If you add these lines: > <set-property name="user.agent" value="safari"/> > <set-property name="client.type" value="default" /> > <set-property name="loglevel" value="debug" /> > ... You can get it down to 1 permutation. Most of the developers @ > google use hosted_gwt, so they don't feel the pain. > > I totally agree about having another ant target. > > -J > > On Tue, Oct 19, 2010 at 11:05 PM, Vega <[email protected]> wrote: >> 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. >> >> > -- 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.
