Schlagwort-Archive: maven

GPE, eclipse and maven never ending story. Done.

I don’t know how many times I had to start over and over again, searching for the latest versions, searching for „how to make“ the Google Eclipse Plugin, eclipse and maven work together.

The problem is: too many tools that don’t seem to like each other fighting over project layout and classpath. Java EE packaging specs and GWT specialities coming from DevMode don’t really make things easier. If you were not a pro in all of this, you ended up with a mess. I have seen it too often.

Since m2e integration things started getting better. And finally, using recent versions from the following official update sites, it started working flawlessly. Even the DevMode/ classpath issue that made us patch the Jetty launcher past year is solved!

I’ll try to keep this posting here up-to-date, so you won’t have to read through all the docs, tips, tricks comments from here and here again and again.

What you need:

  • m2e – maven integration for eclipse
  • m2e-wtp – maven Integration for WTP

I am using the latest stable releases from Well, not always, I am going as stable as possible: the actual wtp integration is still in incubation… but works…

Talking numbers, this are the version numbers I used here:

  • m2e – Maven Integration for Eclipse
  • m2e-wtp – Maven Integration for WTP (Incubation)
  • m2e connector for mavenarchiver pom properties

I have installed a few m2e connectors I required for other non GWT projects, I think they are not needed for a GWT project. Just for the curious:

M2E connectors are a bridge between Maven and Eclipse. When a maven plugin is bound to a lifecycle phase like generate-sources, or process-sources it becomes a part of Eclipse build. (source)

Don’t use the archetype. And if you do, remove the maven-war-plugin plugin. I am using the copyWebapp configuration option in the gwt-maven-plugin to copy the

stuff into the folder used by the DevMode and build system located at 


By the way, defaults work fine now, there is no need to setup/ fix the path configs for the plugin anymore. If you use M2E to update the project configuration things will work.

If you are sure your config is right, and you are absolutely sure you have at least the versions mentioned above, try killing your eclipse config with

This will leave you with a completely missconfigured project in eclipse. Let m2e update the project again. Sometimes I get the error that m2e did fail setting up the project description. Ignore it, do it again.



Outdated posting about Maven and GWT

I recently read the posting on the GWT Blog: GWT and Maven – Playing Nicely Together Since 2008.

Well, I must say that I am surprised and sad about it:

  • The posting talks about GWT 1.5.3 (we already know about that for a long time – so why now?)
  • GWT and Maven stopped playing nicely together since GWT version 1.6

The new GWT building „layout“ is great and at the same time it is a NO-GO for many of us. It generates the GWT app directly into the folder where it expects to find the web.xml and all the other resources we usually keep under SCM.

I really was hoping to use plain vanilla Maven and Ant to create GWT apps, but at the moment I can’t do it. And I am waiting (as many others) to get a working maven plugin that does the building magic.

Why can’t it be done right once and for all?

How many times will I have to hack a build infrastructure for a GWT project???

Or am I missing something?