Hi, we got a similiar problem in our project. At startup in DevMode we get:
log4j:WARN No appenders could be found for logger (org.eclipse.jetty.util.log). log4j:WARN Please initialize the log4j system properly. log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more in And after that lots of errors like: log4j:ERROR A "org.apache.log4j.ConsoleAppender" object is not assignable to a "org.apache.log4j.Appender" variable. log4j:ERROR The class "org.apache.log4j.Appender" was loaded by log4j:ERROR [sun.misc.Launcher$AppClassLoader@566d0085] whereas object of type log4j:ERROR "org.apache.log4j.ConsoleAppender" was loaded by [WebAppClassLoader=MyPortal (0.1)@61c42ccd]. This is only in DevMode and it seems to have no other effect then to be a little annoying but this was not the case with 2.5.1 so there seems to be something changed with the startup. This is why we don't know if it's safe for us to upgrade to 2.6.0 or not. I tried to move the log4j dependencie in Eclipse runconfig from User to Bootstrap but this seems not possible because we are using maven dependencies and our structure there now looks like: *Bootstrap Entries*- JRE System Library User Entries - main/src - main/resource - test/src - test/resource - *dependency*/main/src ... ... + MyPortal (default classpath) --- MyPortal (folder icon) --- Maven Dependencies (libs icon) --- GWT SDK 2.6 (libs icon) In this structure everything under +MyPortal is not openable. The dependency projects are also provided via the pom.xml as dependency and one of it is our domain model which should not be on the client. But if I understand the information in this thread correctly everything under "User Entries" is on the clients classpath instead (or both?) on the webapps classpath? Can you please provide us some information about the impact of this change in our case or how to fix this issue? Am Dienstag, 19. November 2013 16:06:38 UTC+1 schrieb Thomas Broyer: > > Hmm, you have way too many things in your classpath: server-side > dependencies need not (and should not) be in the DevMode classpath, only in > the war's WEB-INF/lib. > I'd try that first (trimming the classpath, to make sure Log4J, Spring et > al are only present in, and loaded from, the web context classloader). > > On Tuesday, November 19, 2013 12:00:21 PM UTC+1, pierre wrote: >> >> Hi, >> >> After switched to use GWT 2.6 RC1, DevMode Jetty 8.1 fail to initialize >> the logger for the web container. >> >> Attached 2.5 log and 2.6 log with >> -Dorg.apache.commons.logging.diagnostics.dest=STDERR -Dlog4j.debug=true for >> reference. >> >> Any tips/hints will be welcome. >> >> Many thanks! >> >> >> >> -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/groups/opt_out.
