On Thu, Jul 23, 2009 at 9:24 AM, BobV <b...@google.com> wrote: > > Generally, as much as I hate to say it, it seems we'd want variations of > the > > tests both with and without stack trace code, so that we don't > inadvertently > > break one mode or the other. It is much like "-draftCompile" in this > > respect. > > That would imply that emulated stack traces would have to be triggered > by a command-line switch or a Java environment property as opposed to > deferred-binding rules.
Technically, wouldn't it just mean we should not pin down the value of the deferred binding property that controls it? It would double the number of permutations, tho. Still, do you disagree with the premise? --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
