Thursday, April 14, 2016

gwt-dev and javax-validation:validation-api


I'm using Dropwizard and GWT in the same project. Problem is, Dropwizard relies on javax-validation:validation-api 1.1.0.Final and GWT uses an older version of the lib.

With dependencyManagement, I've got the project to compile & run correctly. BUT, at test time, I get the following lovely error:

java.lang.IncompatibleClassChangeError: Implementing class

This happens when a class is being deserialized from Json by jackson, and that class uses a @Valid annotation.

I've tried all sorts of exclusions and dependencyManagements, changing scopes, etc but nothing worked, however if I take out gwt-dev, then it magically starts working.


1) What's in gwt-dev which is causing validation-api to get included during tests (not at runtime) even when explicitly excluded?

2) It seems taking out gwt-dev causes SDM to not work, but other things continue working. Is it possible to exclude gwt-dev only for tests, but include it at dev time so SDM can work? (Right now, I've resorted to manually uncommenting gwt-dev when SDM needs to run but keeping it commented otherwise. Sooper hi tech)

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
To post to this group, send email to
Visit this group at
For more options, visit

No comments:

Post a Comment