You mean going the -noserver route? I like the convenience of starting the entire app within Jetty in dev mode. How about allowing a descriptor that specifies the jars required by GWT?
Most apps probably require at most a handful of third-party GWT jars but have a large number of jars required by the server so the overhead of scanning all jars in the classpath is quite undesirable. On Thu, Jan 5, 2012 at 1:43 PM, Thomas Broyer <[email protected]> wrote: > For a "fairly large" project, you'd probably better have separate server > and client (and shared) projects. > > -- > http://groups.google.com/group/Google-Web-Toolkit-Contributors -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
