http://gwt-code-reviews.appspot.com/611802/diff/1/2 File dev/core/src/com/google/gwt/dev/DevMode.java (right):
http://gwt-code-reviews.appspot.com/611802/diff/1/2#newcode408 dev/core/src/com/google/gwt/dev/DevMode.java:408: serverLogger.log(TreeLogger.ERROR, "Unable to process SCL args " + sclArgs); The SCL is already supposed to log any issues with the arguments - why add redundant logging? Note also that none of the SCLs supplied with GWT even implement processArguments, so this can't fail unless you are supplying your own (such as when using GAE). http://gwt-code-reviews.appspot.com/611802/diff/1/3 File dev/core/src/com/google/gwt/dev/DevModeBase.java (right): http://gwt-code-reviews.appspot.com/611802/diff/1/3#newcode1054 dev/core/src/com/google/gwt/dev/DevModeBase.java:1054: getTopLogger().log(TreeLogger.ERROR, "shell failed in doStartup method"); So what failures have you seen that aren't being logged in these methods? http://gwt-code-reviews.appspot.com/611802/show -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
