Hi Keith,
We are in the process of upgrading to GWT 2.0.0, so what our best
practices are is an interesting question right now, but here goes:
1. Our main pain point is the /war conundrum you spoke of.
- We configure the maven-war-plugin with <webappDirectory>${basedir}/
war</webappDirectory> (new step that became required when we upgraded
to GWT 2.0.0 gwt-maven-plugin 1.2)
- We do this in both the single war and the multiple jar projects (see
#3 below)
2. We use Eclipse but not the GWT Eclipse plugin (haven't had time to
look at it yet)
- We build with 'mvn install' (includes gwt:compile), and generate
Eclipse project files with 'mvn eclipse:eclipse' goal
- We are able to remote debug in Eclipse using 'mvn gwt:debug' goal
3. In order to assemble a WAR file we define a maven war project that
assembles 3 separate GWT modules, each of which is defined in a maven
jar project.
- This might be a bit of an oddity in that each of the GWT module
*jar* projects includes a src/main/webapp folder that contains a
web.xml file.
That web.xml file is used only for gwt:run of the individual module.
- In order to gwt:run an individual module we must first 'mvn
war:explode' it (new step that became required when we upgraded to GWT
2.0.0 gwt-maven-plugin 1.2)
- A master web.xml file that supports all of the modules at once is
defined in war project src/main/webapp folder.
The master web.xml file works for both gwt:run of the assembled WAR,
and for when the WAR is bundled into an EAR for live deployment.
Cheers,
Dale
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
