Screaming Penguin - Source Does Matter

Not sure it's real, though clever either way ... http://news.ninemsn.com.au/article.aspx?id=665847

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:

GWT-Maven

From the group: release notes for 2.0-beta26:

Address these issues (includes the patches):
http://code.google.com/p/gwt-maven/issues/detail?id=172 - doubled classpath entries
http://code.google.com/p/gwt-maven/issues/detail?id=176 - same/related to 172
http://code.google.com/p/gwt-maven/issues/detail?id=173 - resource filtering

Ok, so I was all set to write a big rant about how Flickr isn't using REST at all, even though they call it REST everywhere (it's a very nice RPC API, but REST it's not). Then, I did a quick search for similar rants and found this.

Enough said, thanks to Gareth Rushgrove I don't have to write a rant now ;).

To summarize, in Gareth's own words:
And remember, just because an API makes use of HTTP doesn’t make it RESTful.

You know the drill by now, the 2008 time is here: Child's Play.