ManagedBeanTypesTest not compatible with JDK 21

[arjantijms]

ManagedBeanTypesTest in the CDI TCK Passes on JDK 17, but on JDK 21 (ea30) contains an extra collection, resulting in the assertion error:

Set 

[
class java.lang.Object, 
class org.jboss.cdi.tck.tests.definition.bean.types.Flock, 
java.util.List<org.jboss.cdi.tck.tests.definition.bean.types.Vulture<java.lang.Integer>>, 

interface java.util.SequencedCollection<org.jboss.cdi.tck.tests.definition.bean.types.Vulture<java.lang.Integer>>, 

interface java.util.Collection<org.jboss.cdi.tck.tests.definition.bean.types.Vulture<java.lang.Integer>>, 
interface java.lang.Iterable<org.jboss.cdi.tck.tests.definition.bean.types.Vulture<java.lang.Integer>>
] (6) 

does not match array 

[
class java.lang.Object, 
class org.jboss.cdi.tck.tests.definition.bean.types.Flock, 
java.util.List<org.jboss.cdi.tck.tests.definition.bean.types.Vulture<java.lang.Integer>>, 

java.util.Collection<org.jboss.cdi.tck.tests.definition.bean.types.Vulture<java.lang.Integer>>, 
java.lang.Iterable<org.jboss.cdi.tck.tests.definition.bean.types.Vulture<java.lang.Integer>>
] (5)

[manovotn]

I've moved this issue into the TCK repo.

[Ladicek]

Yeah, this would be expected with the addition of sequenced collections into the JDK. It would probably be best if the test used dedicated types instead of JDK types, as those are not under the TCK's control.