On Fri, Jun 8, 2012 at 1:49 PM, Thomas Broyer <[email protected]> wrote:
> ServletContainerLauncher is simple enough to be reused here. The > default implementation based on Jetty 6 could be pushed in a separate > JAR and the SuperDevMode would warn users if it finds a > WEB-INF/web.xml, isn't run in -noserver mode, isn't launched with a > specific ServletContainerLauncher, and the default implementation is > not found in the classpath. Alternately, it could be bundled in > gwt-user.jar in the SDK (though not on Maven). Okay, I don't know much about it yet, but I think we should do the experiment. Unlike regular Dev Mode, I think this should be off by default. How about we add a flag or two? Maybe something like: -warDir path/to/my/expanded/warDir If you don't supply this flag then it works like it does now (we do nothing). If it's supplied then we start up a ServerContainer. I expect we'll need other flags too. There's currently a directory under each CompileDir called "war", which contains compiler output. I assume we have to copy that into the user's warDir somehow, or somehow make the files appear there on the server? If we have multiple modules, do we put them all into the same warDir? Getting Gerrit to work sounds like a good proof of concept. - Brian -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
