The GWT compiler must only see source code that the compiler is able to translate into JavaScript. If your client side code, your shared code and your server code live in the same project the GWT module xml points the GWT compiler to the client source code only. Without this mechanism the GWT compiler would try to compile server code to JavaScript and would likely fail to do so as GWT can only compile a subset of the JRE classes to JavaScript.
-- If you use Maven and you have split your GWT project into three distinct Maven modules, e.g. app-client, app-shared, app-server, the GWT module's <inherits> mechanism can be generated because app-client and all its dependencies should only contain code compatible with the GWT compiler.
The new gwt-maven-plugin developed by Thomas Broyer is able to do this <inherits> generation based on the Maven dependency tree for your client side Maven modules.
Although the <inherits> can be generated when using Maven you often need a GWT module for further configuration (Deferred binding, code generators, configuration properties, etc).
https://github.com/tbroyer/gwt-maven-plugin
-- J.
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/groups/opt_out.
No comments:
Post a Comment