Monthly Archives: July 2014

Setting up a Dropwizard + Gwt:SuperDevMode project on OS X using Eclipse, Maven and GitHub

Until now, I’ve been using Gwt on App Engine, developing alone and using an old version of Firefox so I could continue using Gwt’s dev-mode. I’ve never used Maven before and it’s about time I figured out Superdevmode. Dropwizard will hopefully act as a suitable replacement for App Engine.

I’m running OS X 10.9.4.

This document could do with a lot of work, but should be enough to get anyone off the ground.  My own project that’s using this is VeinToBrain whose pom.xml you maybe want to see. The code below here is all on GitHub at

Download Eclipse

I’ve been using the 64 bit version. I’m not sure of any reason to use 32 bit unless developing apps for 32 bit computers.

  • For now, get 4.3 (Kepler) because the Google Plugin for Eclipse hasn’t been updated for 4.4 yet.
  • There’s no installer, you just drag and drop the uncompressed archive into your Applications folder.
  • For security reasons, OS X will prevent you from running Eclipse until you right-click it and select Open and then dismiss the security warning.

Eclipse Security Warning

Download GPE

As of 14 July 2014, Eclipse 4.4 has been released but the Google Plugin for Eclipse hasn’t been updated for it, so we’re using Eclipse 4.3 for now. (TBH, I’m not 100% sure GPE is even needed.)

In Eclipse, go to Help, Install New Software, paste in the following download site and select the Google Plugin for Eclipse. Don’t worry about the Gwt SDK as it’s not offering the latest version and Maven should take care of it anyway.

Eclipse Install New Software Menu

If you get the following error after restarting (probably a fresh install of OS X and Eclipse) you’ll need to download a newer JDK. 1.7 is ideal for this project.

Eclipse Java  Version Error

Go through the normal install process and then go to Eclipse/Preferences, Java/Installed JREs, press Search and select Java SE 7. Press edit and copy the location of JRE home. Also in Eclipse/Preferences go to Java/Compiler and set Compiler compliance level to 1.7.


Maven is a collaboration tool so required libraries are downloaded from the same source and the same build procedure (i.e. tests & compilation) is followed by each member of the team. It centres around a file, pom.xml — the project object model. When a new library is needed in the project, one member updates the pom and when everyone pulls that commit, everyone is immediately using the new library from the correct source (You can browse the jars Maven has downloaded in ~/.m2/repository/). Maven also provides Archetypes which are basically templates for projects. Download the binary .tar.gz (same as zip but better compression) from:

In Finder menu Go, Go to Folder… /usr/local and make a new folder “apache-maven” and extract the archive in here. You’ll need admin permission.

Open a Terminal window, type nano ~/.bash_profile to edit the Bash profile (think autoexec) and add the following:

export M2_HOME=/usr/local/apache-maven/apache-maven-3.3.9
export M2=$M2_HOME/bin
export MAVEN_OPTS=”-Xms256m -Xmx512m”
export PATH=$M2:$PATH
export JAVA_HOME=/Library/Java/JavaVirtualMachines/jdk1.8.0_77.jdk/Contents/Home
export PATH=$JAVA_HOME/bin:$PATH

Run source ~/.bash_profile to load the changes and then mvn -v to check everything’s working.

Add Maven support to Eclipse (M2Eclipse) by installing the following using Help/Install New Software… Work with:

m2e – Maven integration for Eclipse
m2e-wtp – Maven Integration for WTP

If you select the latest version but you’re on Eclipse 4.3, it will notice and suggest the correct version for your environment.


Set up a repository on GitHub. Tick Initialize this repository with a README.

Download the GUI client, copy to Applications, run, enter your GitHub username and password, Install Command Line Tools when asked. It will ask you to install some XCode tools (small enough).

Your new repository should appear in the app and you can Clone To Computer, making sure to put it in your Eclipse workspace. Then in Eclipse, New/Project, General/Java Project, Next, put the same name as the git cloned project and it will immediately recognise it as a a Git project.

Also in the GUI app, under Settings, Ignored files, copy the contents of my .gitignore file (and change line 21 to match your own project name) so you don’t end up uploading loads of crap to GitHub.

Once it’s done, right click project, Configure, Convert to Maven Project.

In Terminal, set your GitHub details.

# Set your username
$ git config –global “Your Name Here”
# Set your email address
$ git config –global “”


Follow the Getting Started tutorial. Import it to Eclipse in using File/Import… then Maven/Existing Maven Projects

Once it’s working, we’ll change it so the REST application sits under* and the root serves static files. Add a folder called gwt under src/main/resources where we’ll later configure the Gwt compiler to output to. Edit the main DropwizardApplication class so all our REST calls go to

public void run(…)


And so it serves the index.html from the root.

public void initialize(…)

  bootstrap.addBundle(new AssetsBundle(“/gwt”, “/”, “index.html”, “gwt”));

When we add Gwt to the project setup, the dependencies will clash (specifically javax.validation). To solve this, we create profiles in Maven. Wrap the <dependencies> and <build> sections with







Test rebuilding your project with mvn package -P server. You should be able to visit http://localhost:8080/api/hello-world?name=brian and json will be returned

{“id”:1,”content”:”Hello, brian!”}

In Eclipse, I also had to go into the project properties, then Maven and put client,server in the Active Maven Profiles section.

Active Maven Profiles


Create a client profile in your pom for Gwt and add the core Gwt dependency (see: Maven GWT Plugin – Project organisation)









It also needs to be added to the server profile so the compiler knows what your client .java files mean, but the javax.validation library Gwt provides clashes with the one that Dropwizard provides, so we exclude that:













You need an index.html page in your src/main/resources/gwt folder which will be served by Dropwizard and fetch Gwt’s compiled JavaScript. The key line in it is:

Configure your client profile’s build section in the pom to execute the Gwt Maven plugin (i.e. Gwt compiler) and to output to your static files folder:




















You need a ProjectName.gwt.xml in your project root package. This file tells the Gwt compiler which libraries to use, which packages contain code to be compiled and which class of yours contains the Entrypoint (Gwt’s public static void main(String[] args) ).

  <inherits name=’’/>

  <entry-point class=’ie.brianhenry.gwtdropwizard.client.GwtDropwizardClient’/>

  <source path=’client’/>

  <source path=’shared’/>

The entrypoint class is a bit long to go into here. It’s an edited version of the Google Plugin for Eclipse sample code except it’s using RequestBuilder to GET json from your Dropwizard app rather than using Gwt RPC.

All client/server communication is asynchronous, so requests are given an AsyncCallback object that they call the .onSuccess method on once the request has completed.

When the data is returned, it’s just a http string of text, so we need to turn it into a Java object by using a Javascript overlay.

public class HelloWorld extends JavaScriptObject {

  protected HelloWorld() {}

  public final native String getId() /*-{



  public final native String getContent() /*-{

    return this.content;



and parsing it with JsonUtils in our request’s onResponseReceived(…) method.


To get all this running, compile the Gwt code using mvn package -P client then recompile the server side to include the newly created Gwt files with mvn package -P server and run the server again, but just visit http://localhost:8080/ this time.


For continuous development without a complete recompile process, we can use Gwt’s SuperDevMode. First, add the following line to your ProjectName.gwt.xml


Repackage client and server, run the server and in your project root folder run:

mvn gwt:run-codeserver -P client

The first time you run this, you’ll be told to visit the codeserver at http://localhost:9876/ to copy a bookmarklet to your bookmarks bar which you’ll then use to recompile the app after each small change.

SuperDevMode Recompile


What’s above should get you going but, as with any project, there’s bound to be more to configure.

When you begin testing, because the dependencies are split, you’ll have to configure Maven to only test the client code with the client dependencies, by putting this in the build/plugins section:











I’d like to have the run configurations set in Eclipse to possibly not need Terminal at all, but I haven’t looked into this at all yet.

Keep an eye on my actual project’s pom.xml which will be frequently updated (for a while!) and less likely to contain bugs.

Suggested edits to this blog are of course welcome! I’m no senior software developer yet, so appreciate any tips.


Various pages I read while learning all this myself.

Share run configurations:


Nice article that covers a Dropwizard setup 101: