On 16 March 2012 20:26, Ray Cromwell <cromwell...@google.com> wrote: > I agree with most of this, but I just wanted to mention that I think > breaking up the dependency chain will be a little tricky for maven > when it comes to tests. Maven general practice is that a given module > contains its tests and runs them. The problem with gwt-dev and > gwt-user is that many of the gwt-user tests can't run unless gwt-dev > has been built, but gwt-dev IIRC has some tests that depend on > gwt-user. So it may be that you need to make separate > gwt-dev-tests/gwt-user-tests subprojects. > > Personally, I'd like to break up GWT-user further into lots tiny > pieces, like Core, I/O, Emulation, RPC, Widgets, DOM/Media/HTML, etc > We can still build an uber gwt-user.jar, but there are lots of > projects that don't use everything, and being able to move stuff off > of the classpath speeds up the compiler and dev-mode. There are some > projects like PlayN for example, that pretty much only use Core.
Yes, that would be wonderful! -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
