Should we be tied to a specific GWT version? about gwt-maven-plugin

[cristcost]

Hi,
I think that for the moment the strategy should stay the same (tied to a specific version of GWT):
if we will be able to modularize better GWT and GWT will ever have a more independent "dev" jar that has classes for building only (as I see from how gwt-servlet is made, today gwt-dev has also runtime code), then I think it will be best to bind gwt-maven-plugin only the "dev" jar, and I expect that it should work with a range of revision of the user packages.

In practice this should mean that the pom.xml has only gwt-user (of a range of supported revision) as a project dependency, and a gwt-maven-plugin as a plugin that imply the use of a specific gwt-dev. I think that this is not possible today so the strategy should stay the same.

Specifically, I think that the only serious "cons" is the 4th point (and I think the 2nd point is actually a pros as it is a best practice :-D ).

Hope this opinion helps,
Cristiano

[tbroyer]

I answered "no". The plugin is no longer tied to a specific version of GWT, and only a few properties can be configured as maven plugin properties. Also, we now fork a JVM for GWT and require gwt-dev to be a project dependency (it's better anyway to avoid version conflicts, and works better with dependency:tree and the like; it's a new GWT best practice, even with the codehaus plugin).