On Tuesday, April 12, 2016 at 11:21:39 AM UTC+2, Ali Akhtar wrote: > > gwt-user has a dependency to an older version of > javax-validation:validation-api. This is causing a lot of issues, and > causing builds to break with Dropwizard. See: > http://stackoverflow.com/questions/36568756/maven-dependency-management-being-ignored-at-test-time-works-at-runtime >
Split client-side and server-side code into distinct Maven modules. You want distinct classpaths for distinct build tasks, the way to make it happen with Maven is to use distinct modules. > Please upgrade to the latest version in snapshot. > That's not how things go. Many have asked already, and some have started providing patches, but nobody finished the work. You're welcome to try and go the last few miles if you feel brave enough; or just restructure your Maven project to follow Maven best practices. I think if we could, we'd remove the dependency altogether by splitting javax.validation support out into a third-party lib; but unfortunately javax.validation has crept into other parts of the codebase (request factory, editors, themselves now deeply interleaved with widgets). Splitting is possible, but demand some efforts, and it's easier to just use separate classpaths when invoking GWT to avoid conflicts with server-side dependencies. I'm still hopeful that we'll one day replace the build system with something easier to maintain and allowing more modularity, but for now I'm waiting for GWT 3 work to start (or at least have some visibility about what it could look like). -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
