Was this ever addressed elsewhere or is this still a known bug since 2013? This still appears to be an issue with 6.0.14.Final. I can provide a reproduction if necessary but it appears that enough information was provided in the original report. Just to confirm, according to the spec, should it be possible to have both class level constraints and property level constraints on an interface and to validate the property level constraints before the class level constraints utilizing @GroupSequence ? This works as expected when a class is used instead of an interface.