On Fri, Mar 30, 2018 at 1:55 PM, Gunnar Morling <gunnar(a)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