On Fri, Jun 8, 2012 at 8:43 PM, Chris Ruffalo <chris.ruff...@gmail.com> wrote: >> I'm not sure about validation. Many people don't use it and I sorta >> think GWT's validation support ought to be split out of gwt-user into a >> separate jar. If there's no actual bug than I'm inclined to leave it >> alone for now. > > > This would absolutely kill compatibility with gwt-validation. > (https://code.google.com/p/gwt-validation/) > > That would make it almost impossible to get gwt-validation to work with > future versions of GWT because of the multiple classpath issues that would > be introduced. Further: most people don't use the javax.validation package > included with GWT. There are also a fair few people, around 100 I'd > estimate, that use gwt-validation and would have to investigate something > else if this change was made.
I'm afraid I don't understand. Let me sum up: - gwt-user depends on javax.validation, which is currently in a validation-api.jar in the SDK (there's also validation-api-sources.jar). - gwt-validation depends on javax.validation, and instruct users to put it in the classpath So where's the problem with either solution? (bundling it within gwt-user, or letting it as a separate JAR as today, and as Brian suggests it stays) Also, note that the gwt-user in Maven won't bundle javax.validation but instead declares a dependency javax.validation:validation-api (as is already the case today). No problem either. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
