Just this in the POM. These are required to use RequestFactory, but not
required otherwise, so we should probably note that in the POM, too.
<dependency>
<groupId>org.json</groupId>
<artifactId>json</artifactId>
<version>20090211</version>
</dependency>
<dependency>
<groupId>javax.validation</groupId>
<artifactId>validation-api</artifactId>
<version>1.0.0.GA</version>
</dependency>
<dependency>
<groupId>org.hibernate</groupId>
<artifactId>hibernate-validator</artifactId>
<version>4.0.2.GA</version>
<exclusions>
<exclusion>
<groupId>javax.xml.bind</groupId>
<artifactId>jaxb-api</artifactId>
</exclusion>
<exclusion>
<groupId>com.sun.xml.bind</groupId>
<artifactId>jaxb-impl</artifactId>
</exclusion>
</exclusions>
</dependency>
On Tue, Feb 8, 2011 at 11:48 AM, <[email protected]> wrote:
> On 2011/02/07 23:01:25, drfibonacci wrote:
>
>> From a maven perspective, this is a much better solution than bundling
>> validation classes in gwt-user.jar. However, will the changes to
>>
> .classpathsrc
>
>> and/or the gwtc ant target affect the GWT compiler when called from
>>
> the maven
>
>> plugin?
>>
> Nothing in this change modifies the pom.xml produced by webAppCreator.
> What would we need to add the validation classes and sources to the
> pom.xml?
>
>
> http://gwt-code-reviews.appspot.com/1342803/show
>
--
David Chandler
Developer Programs Engineer, Google Web Toolkit
w: http://code.google.com/
b: http://googlewebtoolkit.blogspot.com/
t: @googledevtools
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
