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 18:45:34, scottb wrote:
On 2010/04/20 16:50:38, jat wrote: > I think it is better to more closely model what the actual distro
has, but if
> you prefer I can merge them together.
I think it's much nicer that way, for project management, build.xml
rules (which
I think you still need to update?), and svn up tools.
Jetty provides aggregation JARs: http://wiki.eclipse.org/Jetty/Reference/Dependencies#Aggregation_JARs though AFAICT they're only downloadable from the Maven repos: http://repo1.maven.org/maven2/org/eclipse/jetty/aggregate/ This should help reduce the number of JARs needed (not to a single JAR, but 2 or 3, as I don't know whether jetty-servlets and jetty-websocket are available in some aggregation JAR; the jetty-webapp aggregation JAR should cover all the others)
> 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.
I usually build them myself. :)
Source JARs are downloadable from the Maven repos (see link above) http://gwt-code-reviews.appspot.com/306803/show -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
