Re: GWT by hand (no xml configuration, no ant, no running gwt-dev.jar)

I honestly don't understand why you don't want to use *.gwt.xml files but well, you can create a module programmatically using ModuleDefLoader.createSyntheticModule (this is used in JUnitShell to create a module that inherits both your module –the one whose name you return from your GWTTestCase#getModuleName()– and com.google.gwt.junit.JUnit).

As for calling the DevMode and/or Compiler (and again, I don't understand why you don't want to simply call them from the command-line, and use -noserver for the DevMode and use your own Jetty server), *do* look into their main(): you have to create a CompilerOptions instance (or similar for DevMode) that you pass as constructor argument to a Compiler instance, and then call its run() method; and similarly for the DevMode.

Currently, the Compiler's main() uses a CompileTask and CompileTaskRunner, but they don't seem to bring much value; you'd better use them though to be future-proof.

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/9rHC4RzMr6EJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.