Nobody maintains the JSR303 emulation. Someone (Danilo) once volunteered,
started working on the upgrade, and then disappeared.
If you don't use client-side validation then you can compile with
javax.validation 1.0 and run with 1.1. The problem then is setting up those
rules in your build, and
Please consider making that hibernate upgrade a priority. We are hugely
behind on that upgrade, Hibernate 4 was ages ago. Today I'm experiencing
this problem, but a lot of people are going to experience this in future,
because every project is going to be on a newer version of validation-api.
If
> GWT is on 1.0.0.1.GA. Isn't that going to be mostly compatible with
> 1.1.0? It seems like this would just require changing the version in a
> pom, and the rest would work. I would be really surprised if there are any
> breaking changes between these versions.
>
Upgrading Validation API
It would make my workflow very complicated to have them in separate
modules, as then I'd also need a 3rd project for shared code. It so happens
that mostly DTOs would be in the shared code, and the DTOs would need to be
annotated w/ Validation annotations. Where do they get these annotations,
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:
>
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
Please
