[gwt-contrib] Re: subtree logging for problems

2009-04-22 Thread Freeland Abbott
Thanks. Typo fixed, submit at r5269. On Tue, Apr 21, 2009 at 6:27 PM, Lex Spoon sp...@google.com wrote: LGTM. There's a typo in ProblemReport: accessir. -Lex On 4/21/09, Freeland Abbott fabb...@google.com wrote: Here's the promised follow-on to my earlier, fixing the subtype logging

[gwt-contrib] Re: subtree logging for problems

2009-04-22 Thread Bruce Johnson
Would you be willing to drop a before and after example of the output for those of watching from the stands? On Wed, Apr 22, 2009 at 1:55 PM, Freeland Abbott fabb...@google.com wrote: Thanks. Typo fixed, submit at r5269. On Tue, Apr 21, 2009 at 6:27 PM, Lex Spoon sp...@google.com wrote:

[gwt-contrib] Re: subtree logging for problems

2009-04-22 Thread Freeland Abbott
From this patch (the bigger impact is my earlier one, which already had at least the after form thrashed on), the new, sublogger-using format is: [java] Compiling module com.google.gwt.sample.broken.Broken [java]Scanning for additional dependencies:

[gwt-contrib] Re: subtree logging for problems

2009-04-22 Thread Freeland Abbott
For the record, the original (pre-5256) output would have been (noting lack of specificity of error, which was my poor usability itch, as well as the several levels of nested logging that have been removed and other internal cleanup per Lex's encouragement): [java] Compiling module

[gwt-contrib] Re: subtree logging for problems

2009-04-21 Thread Lex Spoon
LGTM. There's a typo in ProblemReport: accessir. -Lex On 4/21/09, Freeland Abbott fabb...@google.com wrote: Here's the promised follow-on to my earlier, fixing the subtype logging to be a subtree logger. I'm still bothered by the multiple entries for E extends java.lang.Object, but I'm