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. On 2010/04/20 16:33:18, scottb wrote:
Is this still going to be needed with the new Jetty?
I have no idea. I didn't understand the purpose for it and I don't have a JSP sample to test with. 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"/> On 2010/04/20 16:33:18, scottb wrote:
1) Um.... wow. So many jars??? In the past we've smashed several
jars together
for things that we treat as really one piece.
I think it is better to more closely model what the actual distro has, but if you prefer I can merge them together.
2) Can we avoid the whole JETTY_SRC thing? Just put a -src.zip in
GWT_TOOLS. Sorry, that shouldn't have been there at all -- I just had that while I was getting it working. I didn't see any obvious way to get a source jar, and even from svn trunk I didn't see it (but then I am no maven expert), so I wasn't planning on including it. 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"/> On 2010/04/20 16:33:18, scottb wrote:
Unrelated.
Done. http://gwt-code-reviews.appspot.com/306803/show -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
