I also would like to disable assertions while debugging GWT. I agree that in general assertions are a good thing and it seems obvious you'd always want them, but sometimes there are assertions in dev mode for code that that runs fine in production, Though they don't affect production I sometimes have to fix them if I want to debug other real/production issues (in dev mode) that depend on that same code.
On Friday, October 1, 2010 at 6:29:57 AM UTC-7, Thomas Broyer wrote: > > > > On Oct 1, 12:48 pm, stumpy <[email protected]> wrote: > > How do I disabled assertions in GWT development mode? > > > > -da doesn't seem to do the trick > > I don't think it's possible: > > http://code.google.com/p/google-web-toolkit/source/browse/trunk/dev/core/src/com/google/gwt/dev/shell/CompilingClassLoader.java#860 > > (unless you manage to call setDefaultAssertionStatus on the > classloader too) > > I also can't see a reason why you'd want to do that... -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
