Closed jamezp closed 11 months ago
I seem to be wrong about being able to use excludes in the maven-surefire-plugin
as the tests use TestNG and the suiteXmlFiles
configuration parameter. With that set, the excludes
are ignored. We'd need to modify the cdi-lite-tck-suite.xml
to get this working. This is definitely possible, but a new release of the Jakarta EE 10 Core Profile would be preferred.
Thanks @jamezp
The initial Core Profile 10.0.3 TCK is staged at http://download.eclipse.org/ee4j/jakartaee-tck/jakartaee10/staged/eftl//jakarta-core-profile-tck-10.0.3.zip
Relevant Information
jakarta.ee.tck.coreprofile:cdi-lite-tck-suite:10.0.1
org.jboss.cdi.tck.tests.implementation.simple.lifecycle.SimpleBeanLifecycleTest
org.jboss.cdi.tck.tests.context.DestroyForSameCreationalContextTest
org.jboss.cdi.tck.tests.definition.bean.types.ManagedBeanTypesTest
The
cdi-lite-tck-suite.xml
is out of sync with CDI'stck-tests.xml
. These tests should be excluded in thecdi-lite-tck-suite.xml
:The latter (
org.jboss.cdi.tck.tests.definition.bean.types.ManagedBeanTypesTest
) causes issues with the TCK passing on Java 21.If we cannot get this merged and a new Jakarta EE 10 Core Profile TCK released, we're asking that we can explicitly exclude these tests in our test configuration. In our case it will be on the
maven-surefire-plugin
section of ourpom.xml
for the CDI Lite TCK tests.Additional context The CDI TCK Challenge issues: