Screaming Penguin

I wasn't aware you can run a Maven archetype using a remote repository the way Stephen Nimmo noted in his post about GWT-Maven. I should have known better, but the way I described it previously in the GWT-Maven documentation was to tell people to download the archetype artifact first, then install it, and THEN use it. That way is a lame, the *right* way is so much nicer ;).

With this setup you can create yourself a GWT project in one line (a bit of a long line, but hey, it is a single line), and then you can run it with one command. You don't need to download GWT yourself , you don't need to setup dependencies and classpaths, you don't have to write a Hello World project, all that jazz is handled for you. (You do need Java and Maven 2 of course, but those are given ;).)

Check it:

mvn archetype:create -DarchetypeGroupId=com.totsp.gwt -DarchetypeArtifactId=maven-googlewebtoolkit2-archetype
-DarchetypeVersion=1.0.3 -DremoteRepositories=http://gwt-maven.googlecode.com/svn/trunk/mavenrepo 
-DartifactId=myGwtProject -DgroupId=com.myco

Then you have many GWT related facilities at your feet, via GWT-Maven. Run the GWTShell for example, and see your project update in real time while you change/edit code:

cd myGwtProject
mvn gwt:gwt

. . . or build yourself a WAR for deployment in a servlet container (war ends up in ./target) . . .

mvn install

. . . or debug your project, also via the GWTShell (this starts a remote process with the debugger hook enabled, and you can then connect to it in your favorite IDE/debugger) . . .

mvn gwt:debug

. . . or test your project using BOTH it's standard JUnit/TestNG Surefire tests, and special GWTTestCase tests . . .

mvn test

If you need more info see the GWT-Maven docs, but you get the idea.