[bv-dev] Questions on TCK SequenceResolutionTest

Gunnar Morling gunnar at hibernate.org
Fri Mar 30 08:57:39 EDT 2018

If not that, what else would you consider as a cycle in the context of
group sequence definitions then?

This sequence definition here says: "validate TimeConsumingChecks *before*
TestEntity" and "validate TimeConsumingChecks *after* TestEntity", aborting
after the first group found with violated constraints. There's no way to
implement this.

2018-03-30 14:47 GMT+02:00 Guillaume Smet <guillaume.smet at gmail.com>:

> On Fri, Mar 30, 2018 at 1:55 PM, Gunnar Morling <gunnar at hibernate.org>
> wrote:
>> I.e. you have a cycle between TimeConsumingChecks in the Complete group
>> sequence (once the re-defined default group sequence has been expanded).
>> In that light the method name is indeed a bit misleading, and I wonder
>> whether we have a simpler test in the TCK which just asserts that
>> @GroupSequence({ TimeConsumingChecks, TestEntity, TimeConsumingChecks })
>> triggers the exception. I didn't check the assignments of the assertion ids.
> I thinks that Matt and I aren't that convinced that it is a cyclic
> dependency. Sure one of the groups appears 2 times but it's not really
> cyclic.
> --
> Guillaume
> _______________________________________________
> beanvalidation-dev mailing list
> beanvalidation-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/beanvalidation-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/beanvalidation-dev/attachments/20180330/0fcf675e/attachment.html 

More information about the beanvalidation-dev mailing list