I think I understand the question, but I am not sure why you are having any problems. You want server side logging to happen, even in the shell - either to console or to file, whatever you have it configured for.
That works fine for me. I also just added a simple test to the "simplesample" app and it works there too. Check your configuration, it's got to be something with what configuration files are in the classpath while in the shell, versus the server, etc. GWT-Maven doesn't gobble anything up, and really neither does the embedded Tomcat. Now, the embedded Tomcat doesn't have any default logging setup like a full blow Tomcat does, but I assume you are configuring your logging yourself anyway. Have a look at this project: http://gwt-maven.googlecode.com/svn/trunk/maven-googlewebtoolkit2-plugin/simplesample/ Specifically I have some logging here: http://gwt-maven.googlecode.com/svn/trunk/maven-googlewebtoolkit2-plugin/simplesample/src/main/java/com/totsp/sample/server/SampleRemoteServiceImpl.java And I have a log4j config here: http://gwt-maven.googlecode.com/svn/trunk/maven-googlewebtoolkit2-plugin/simplesample/src/main/resources/log4j.xml And the output shows up BOTH in the same console window where I launched "mvn gwt:gwt" and in the log file I have configured there. On Nov 5, 5:14 pm, [EMAIL PROTECTED] wrote: > 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. > > -jesse > > On Wed, Nov 5, 2008 at 2:35 PM, David Durham, Jr. > > <[EMAIL PROTECTED]> wrote: > > > Right. This project has support for client-side and server-side > > logging, so I thought it might be useful. I honestly haven't used it. > > Why don't you try capturing the log implementation type. and sending > > that to your client for output. One common issue is not having a > > log4j or commons-logging dependency declared in your pom. As I > > recall, tomcat will provide those libraries through the common or > > shared classloader. > > > -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 -~----------~----~----~----~------~----~------~--~---
