Google Web Toolkit

Build & Deployment

Select your GWT module file and right-click to select the Google Web Toolkit > Deploy module command or click on the Deploy Module button in the main Eclipse toolbar to open the Deployment dialog

 

Specify the application server deployment options
  • The name of the WAR file
  • The server path for the WAR file
  • The GWT compiler style
    • Obfuscated (default)
    • Pretty
    • Detailed
  • Maximum memory for the GWT Compiler
Select the path where the WAR file should be copied.
  • Can be a local directory
  • Can be a server location
Multiple files are created by the Deployment dialog.
  • The WAR file which should be deployed to your server
  • A build.xml file for an easy, repeatable build process

Note that the build.xml file will be regenerated any time that the Deploy module command is used.

The build.xml file contain all of the steps needed to recreate the WAR file and deploy it  to your server.
  • Create the JAR file
  • Invoke the GWT compiler
  • Generate web.xml file
  • Package up the WAR file
  • Deploy to the server

Note that if the module folder has files named build-1.5.xml or build.1.5.xml, then these files will be used as the templates for deployment. This allows you to completely customize and repeat the build process. You can add/move operations and targets as long as the modified script still references the same template variables. The original files are located here:

com.instantiations.designer.gwt/com/instantiations/designer/gwt/actions/deploy/build-1.5.xml

You can rebuild and redeploy your WAR file by right-clicking in the build.xml file and selecting Run As > Ant Build or Run As > Ant Build... (to invoke the ANT build.xml editor).

You can use the ANT build.xml editor to select specific targets to execute.

 

 

  

 

 

 


 

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 3.0 License.

Authentication required

You need to be signed in with Google+ to do that.

Signing you in...

Google Developers needs your permission to do that.