I guess I didn't make myself clear, I was agreeing. GWT's validation should *always* be in a separate module from gwt-user. What I should have said "Otherwise, this would completely kill..."
I don't think that moving javax.validation into gwt-user would be a good idea. Especially if it comes with the built in GwtValidation module. I guess it might be okay as a standalone but not that many people use javax.validation if everything I've read is to be believed. Maybe I jumped on this one a little hard. Sorry for not being 100% clear, Chris On Fri, Jun 8, 2012 at 2:50 PM, Stephen Haberman <[email protected]>wrote: > > > > think GWT's validation support ought to be split out of gwt-user > > > into a separate jar. > > > > This would absolutely kill compatibility with gwt-validation > > I know very little about gwt-validation and GWT's javax validation, but > wouldn't having GWT's validation in a separate jar make it easier for > users to provide their own validation logic, like gwt-validation? > > Or do you have dependencies on GWT's javax validation, and if so, > couldn't your users also depend on the hypothetical separate jar? > > - Stephen > -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
