GWT and AppEngine part 2

Just had fun dealing with an error when deploying to appengine that said that I need to compile my module.  After much searching and playing, I finally discovered that I had to run a maven compile first.  I had been avoiding that because my maven compiles had been erroring out.   I assumed that they weren't doing anything.  They were apparently doing enough, though, to allow the google eclipse plugin to finish the job when deploying.

Upon investigation of the compile error I discovered that the default pom.xml that is created by gwt-maven-plugin had the scope for the validation-api dependency set to test.  Setting it to provided solved the problem. See: http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html for more information on scope.

<dependency>
<groupId>javax.validation</groupId>
<artifactId>validation-api</artifactId>
<version>1.0.0.GA</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>javax.validation</groupId>
<artifactId>validation-api</artifactId>
<version>1.0.0.GA</version>
<classifier>sources</classifier>
<scope>provided</scope>
</dependency>