On Fri, Nov 14, 2008 at 9:52 AM, Ian P. Christian <[EMAIL PROTECTED]> wrote:
>
> 2008/11/5 <[EMAIL PROTECTED]>:
>>
>> I really do not want to put all my logging through GWT, and it seems
>> pretty weird that I would have to. Can any developers speak up about
>> whether gwt-maven is gobbling up stdout? How about any maven gurus?
>>
>> I definitely have both log4j and commons-logging dependencies
>> declared. As I stated before, log4j works properly when I deploy to a
>> dedicated container outside of the one provided by GWT.
>
> I'm also suffering with this. I've copied the log4j.xml exactly as
> linked before, and I'm not seeing any log output.
I've done some more poking around with this. It looks like GWT will
set a system property (presumably for hosted mode only). Test it with
this:
System.getProperty("org.apache.commons.logging.Log");
I get: com.gwt...CommonsLogger or something like that.
So if you've got log4j on your classpath, it may not be selected
because of this system property. You can explicitly reference log4j
when creating your logger, but that may not help you with a library
that's using commons logging. Looking for a way to override ...
-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
-~----------~----~----~----~------~----~------~--~---
