GWT-Maven

GWT-Maven 2.0-beta26 released

2008-11-20T16:42:00.000-08:00

Details here: http://groups.google.com/group/gwt-maven/browse_thread/thread/096756dd8a3ce07a

The docs have been updated too (better coverage concerning testing and using the archetype):
http://gwt-maven.googlecode.com/svn/docs/maven-googlewebtoolkit2-plugin/index.html

And, check out this super short way to use the Archetype (which has also been updated to use the new version): http://www.screaming-penguin.com/node/7628.

2.0-beta 24 minor enhancement release

2008-10-02T12:38:00.001-07:00

Announcement with details here:

http://groups.google.com/group/gwt-maven/browse_thread/thread/11ec1f405cdb5883

2.0-beta23 released (maintenance release) and Archetype added

2008-09-17T03:34:00.001-07:00

See the docs, 2.0-beta23 has been released, it addresses a few bugs (only a maintenance release), and a new Archetype has been added.

Docs are all updated:

http://gwt-maven.googlecode.com/svn/docs/maven-googlewebtoolkit2-plugin/index.html

New revs of GWT-Maven available (M2 2.0-beta22 - M1 1.6.0)

2008-09-10T09:54:00.000-07:00

There is a ton of new stuff in the new version of GWT-Maven.

I just thought I would give it a release notice here because it's a significant update with many issues resolved and a different approach to a few key features.

It's a crapload faster at launching the shell

It supports GWT 1.5.2 from the Maven central repo

Automatic setup and extraction of the GWT native libs is now handled a more Maven-y way

GWTTestCase support was rewritten and is a bit more robust

It supports I18N generation

In general uses some cleaned up interfaces, factories, etc, to remove code duplication

It does *NOT* support the bean gen stuff anymore (this is a bummer, but can't find the maintainer for this, and it has a lot of issues, so it's not supported anymore)

For more info see the mailing list announcement.

Oh and I forgot to mention one other thing I spent a lot of time on, it has all new, meaningful and accurate *DOCUMENTATION* as well ;).

Yes, it's still a "beta," for now. My plan is to see how the community responds to this new approach (which was tested as a branch for some time before it became a release), and then if things go well make a non beta release and put it in the central maven repo. Now that we are using more standard mavenized ways to do things (including using GWT deps from central), it should be a lot easier to get into central once it's known to be solid.

(As an aside I also released a new version of the M1 plugin a while back too, 1.6.0 - we use it at the office and it works fine, though I know not many other folks care about M1 stuff - I personally still find it to be often less frustrating and complicated than M2 - but any version of Maven involves some love/hate.)

M2 v 1.5.2 and M1 v 1.5.3 Available

2007-04-03T12:07:00.000-07:00

So I finally got around to cleaning up some longstanding complaints. Here is the rundown:

Both plugins now support multiple compile targets:

* For Maven1 the google.webtoolkit.compiletarget can now be a comma separated list.

* For Maven2 you need to use the multiple parameter format:

/> /> /> />

The gwt:mergewebxml for Maven1 is problematic with multiple compile targets, however.

The pathing issue for windows users with spaces in the path to the Java executable is corrected.

The classpathing for the gwt:compile issue for dependencies in Maven 2 is corrected.

The classpathing issue for GWTTestCase in Maven 2 is *not* corrected. I will be looking into this this week.

The gwt:generateClientBeans has gotten a number of enhancements/bug fixes and should be significantly better.

gwt-maven m2 Available.

2007-02-17T22:27:00.000-08:00

See this post in the newsgroup for details.

Sample example that is quite ample

2006-12-12T14:19:00.000-08:00

The sample app for gwt-maven now includes a DataSource example.

http://www.screaming-penguin.com/docs/maven-googlewebtoolkit-plugin/sample.html

Maven 1 plugin 1.0.4 available

2006-12-11T09:56:00.000-08:00

New minor rev of the 1.x gwt-maven plugin series, contains some minor bugfixes.

Docs updated and are here.

New version is in the repo here.

New docs for maven-googlewebtoolkit-plugin

2006-12-06T15:52:00.000-08:00

The maven-googlewebtoolkit-plugin (gwt-maven) now has a bit more documentation and a "sample" project. The sample is very simple GWT with RPC using the gwt-maven plugin (does not have datasources and such at this time, still does demonstrate the context.xml and web.xml usage with the plugin).

The docs are HERE.

I had hoped to host these docs on Google Code, as is the project itself (http://code.google.com/p/gwt-maven/) but for some reason any HTML file located there gets a mime type of text/plain (probably by design so you don't do exactly what I was trying to do) and therefore will not render as HTML in decent browsers (works great in IE, not in others).

Maven 1 plugin v 1.0.3 available

2006-11-22T15:22:00.000-08:00

The 1.0.3 version of the Maven 1 plugin is available in the repo. To install:

maven plugin:download
-DgroupId=com.totsp.gwt
-DartifactId=maven-googlewebtoolkit-plugin
-Dversion=1.0.3
-Dmaven.repo.remote=http://gwt-maven.googlecode.com/svn/trunk/mavenrepo/

This is a greatly enhanced version of the original. It includes several new features:

goal: gwt:mergewebxml

This goal will take the servlets declared in your GWT module and add them to the web.xml file in the target/webapp (or whatever) directory. This means you only have to declare your servlets in the gwt.xml file, not in both places. To go along with this, you can use:

goal: gwt:war

To spit out a ready-to-go war file.

Also, the default targets of gwt and gwt:debug have been enhanced. They will both now build a tomcat directory under "google.webtoolkit.tomcat", defaults to target/tomcat. This will include your context.xml in the right place, and take the non-GWT elements defined in your web.xml file and add them to the web.xml file the shell runs with, so your whole application should run. You should note, however, that if you want to use Tomcat DataSources, you still need to include commons-dbcp and commons-pool as project dependencies, just set them to war.bundle=false. This will ensure they are there when the shell runs, but don't end up in your war file.

There are some changes to the properties. First, the declaring of the dev-*.jar in the project.properties has gone away. We just add all of them to the classpath and hope you haven't put multiple versions in the same directory!

Also new:

google.webtoolkit.tomcat : sets the root for catalina.base when shell runs.
google.webtoolkit.extrajvmarg : Passes additional JVM args when shell and debug run.

If you are using a mac, you want to run maven with

-Dgoogle.webtoolkit.extrajvmargs=-XstartOnFirstThread

or put it in your ~/build.properties file.

Charlie is working on an extended sample project with database access and some detailed docs.

I also want to mention that Eduardo Pereda has been added to the project to flesh out the Maven2 functionality that I have been neglecting for so long.

Hello World

2006-10-11T09:47:00.000-07:00