We need to bump the gwt version in the pom.xml with each RC, and with the final release.

We also need to fix the pluginRepository entry.

From Dave:

maven changes needed are

1. Change gwt.version in expenses pom to 2.1.1-rc1
2. Change version 2.1.0 to 2.1.1-rc1 in tools/scripts/maven_script.sh
3. Run maven_script.sh to install current build in your local repo

Test cases: 1. Run Expenses app with mvn gwt:run. See samples/expenses/MAVEN-README for funky run cmd with cd hack 2. Import into Eclipse (w/ or w/o STS) as existing maven project and Run As | Web App

Would be even better if we could lose the 2.1.0.M3 pluginRepository in expenses/pom.xml and instead use gwt-maven-plugin version 2.1.0-1 (just released). I'll test that config.

http://gwt-code-reviews.appspot.com/1202801

Off to a bad start. mvn says it can't find the gwt-user 2.1.1-rc resource, and suggests that I upload it using exactly the commands the mavne_script.sh does. Output attached.

Could issue 4853 be fixed at the same time? (or at least for 2.1.1 "GA")

To make GWT 2.1.1 work with gwt-maven-plugin 2.1.0-1, you have to explicitly declare gwt-user and gwt-dev as plugin dependencies. I'm almost sure it's not a "supported use" of the plugin though. org.codehaus.mojo gwt-maven-plugin 2.1.0-1 com.google.gwt gwt-user ${gwt.version} com.google.gwt gwt-user ${gwt.version} ...

(and note that in the plugin's is no longer needed or even meaningful, and is simply ignored)

See also http://jira.codehaus.org/browse/MGWT-256.

As long as the plugin behavior noted in tbroyer's solution is intentional, no plugin fix is required.

Re-opening this because we'll need to do the same thing for any other RCs, and for GA

Dave, do we really need the roo, spring and slf4j version properties in the pom.xml file?

@rjrjr no, we don't need any Roo, Spring, slf4j stuff in the POM since we're no longer building the Expenses sample with Roo

Left the roo / spring stuff in place for now

r9423