On Thu, Dec 2, 2010 at 1:53 PM, Matt Richards <[email protected]> wrote:
> What are the ant targets to build a debug version of the client? > I was under the impression all that was needed is compile_gwt_dev, are > there others for the server side? > If you want to debug the client, I'd suggest using OOPHM. See https://sites.google.com/a/waveprotocol.org/wave-protocol/code/client-development-environment-set-up What compile_gwt_dev gives you is somewhat human readable JS and the stack trace produced in a shiny is deobfuscated. I some time use this when the bug is particularly nasty where I can't reproduce it in OOPHM. I'd recommending debugging the output JS as a last resource. > > -- > --Matt > > -- > 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]<wave-protocol%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/wave-protocol?hl=en. > -- David Wang -- 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.
