http://gwt-code-reviews.appspot.com/1727804/diff/1/dev/codeserver/java/com/google/gwt/dev/codeserver/Options.java File dev/codeserver/java/com/google/gwt/dev/codeserver/Options.java (right):
http://gwt-code-reviews.appspot.com/1727804/diff/1/dev/codeserver/java/com/google/gwt/dev/codeserver/Options.java#newcode148 dev/codeserver/java/com/google/gwt/dev/codeserver/Options.java:148: return "The root of a directory tree containing GWT source code to compile."; On 2012/06/05 10:52:58, tbroyer wrote:
Does this mean SuperDevMode no longer loads sources from the
classpath? It picks up from the classpath, but this directory shadows the classpath. The reason is, at least for Google, we always produce source-jars in our internal build system, and you can't 'edit' them. That is, when we launch superdevmode, it has the source, but it's been compiled and put into jars on the CP. This directory allows us to specify another location to look at, in addition to the classpath (which is the fallback) For external users, it may not be needed, although I could see if superdevmode is launched from a Maven build you might run into the same issue. http://gwt-code-reviews.appspot.com/1727804/ -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
