On Fri, Dec 12, 2008 at 6:15 PM, <[email protected]> wrote: > Ok, do you have a work around? I can not simply start using log4j > directly, I have a dozen projects that are exploiting > commons-logging..
I haven't come up with anything yet. In Tomcat outside of the GWT launch, the logging works fine of course. In launch mode or whatever it's called (hosted mode?), I think there are 2 options: 1. Determine how to log to the GWT console using the gwt treelogger returned by commons logging. 2. Patch GWT to change it's logging behavior. Probably 1 is the easier route, but I don't yet have a solution for either. The other thing is that in the absence of good logging, I'll often opt for the debugger or even Window.alert(..). Sad, I know. -Dave --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "gwt-maven" 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/gwt-maven?hl=en -~----------~----~----~----~------~----~------~--~---
