Mostly LG, but please hold off until I get my JUnitShell change in.
http://gwt-code-reviews.appspot.com/306803/diff/1/2 File dev/core/src/com/google/gwt/dev/shell/jetty/JettyLauncher.java (right): http://gwt-code-reviews.appspot.com/306803/diff/1/2#newcode479 dev/core/src/com/google/gwt/dev/shell/jetty/JettyLauncher.java:479: * JSP compilation work. Is this still going to be needed with the new Jetty? http://gwt-code-reviews.appspot.com/306803/diff/1/4 File eclipse/dev/.classpath (right): http://gwt-code-reviews.appspot.com/306803/diff/1/4#newcode20 eclipse/dev/.classpath:20: <classpathentry kind="var" path="GWT_TOOLS/lib/jetty/jetty-7.0.2.v20100331/jetty-xml-7.0.2.v20100331.jar" sourcepath="/JETTY_SRC/jetty-xml/src/main/java"/> 1) Um.... wow. So many jars??? In the past we've smashed several jars together for things that we treat as really one piece. 2) Can we avoid the whole JETTY_SRC thing? Just put a -src.zip in GWT_TOOLS. http://gwt-code-reviews.appspot.com/306803/diff/1/4#newcode49 eclipse/dev/.classpath:49: <classpathentry kind="var" path="GWT_TOOLS/lib/sun/swingworker/swing-worker-1.1.jar" sourcepath="/GWT_TOOLS/lib/sun/swingworker/swing-worker-1.1-src.zip"/> Unrelated. http://gwt-code-reviews.appspot.com/306803/show -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
