Skip to content


Repository files navigation

GWT Eclipse Plugin

Join the chat at

This repository houses the source for the GWT Eclipse Plugin.

Thanks to our Sponsors

Sponsors that provide man power and equipment to help get the job done.


The Google Cloud Tools team has put a significant amount of effort in helping bring the GWT Eclipse Plugin to market.

Not Included



  • GWT SDK Selection
  • GWT Compiler Launcher
  • GWT Development Mode with Jetty Launcher (a.k.a DevMode Super Dev Mode)
  • GWT Development Mode Launcher (a.k.a CodeServer Super Dev Mode)
  • GWT Legacy Development Mode Launcher (a.k.a Classic Dev Mode or OOPHM Dev Mode)
  • GWT Java Editor
  • GWT UIBinder Editor
  • OOPHM for Legacy Dev Mode
  • CSS Resources Editor
  • Maven integration


Supports the two GWT Maven plugins.


Install from the Eclipse marketplace.

Drag to your running Eclipse* workspace. *Requires Eclipse Marketplace Client


The Eclipse repositories for this plugin.


Release update site.

Production Zip

Download the repo in a zip file from the latest release at the releases page. The current release is 4.0.0


The staging repository is also at, under the nightly version. At this time, these are signed with a self-signed certificate.



Simply use Maven to import all the plugins and modules.

  • Use Eclipse Import and choose import with Existing Maven projects. Don't forget to select recursive import.
  • Select all the projects and import them. This will create the .project, .classpath and .settings files. If some exist, they will be overwritten.

Target Definition

The target defintion build is based off of the Google Cloud Tools. Follow their instructions to build.

  • Install the target.tbd plugin - Install the targets plugin.
  • Once the plugin is installed, right click on the target.tbd file and set the target.
  • Note: The targets will have to be updated by setting the targets. This will regenerate the Eclipse target files.


To build, Apache Maven and Java 17 are required. Invoke mvn verify to build and test. The resulting update site can be found in repo/target/repository for local deployment and testing.


Creating a release requires signing artifacts. Set the following environment variables before running mvn verify:

  • SIGN_KEYSTORE - Path to a pkcs12 keystore that contains a key to use to sign this release
  • SIGN_STOREPASS - Passphrase for the keystore
  • SIGN_ALIAS - Alias of the key to use to sign the release
  • SIGN_KEYPASS - Passphrase for the key
  • SIGN_TSA - URL of a Time stamp authority to use to sign this release

At this time, releases are performed manually. The releases deployed to the marketplace will be signed with the certificate for


Releases are uploaded as zips to the release part of the Github project page, and also deployed at as Eclipse update sites. Releases will be added to the GWT-Plugin page on the Eclipse Marketplace.


There are a couple of archetypes that are used to test.