Hi guys anyone knows if that's normal to get some regression running tck for cdi 1.0?
On openejb I have: Tests run: 751, Failures: 19, Errors: 0, Skipped: 0 One is org.jboss.jsr299.tck.tests.implementation.producer.field.lifecycle.ProducerFieldLifecycleTest, fails because of new handling of specialization (remove the bean) the corresponding app doesn't deploy anymore cause parent is no more a Bean: public class TarantulaProducer { @Produces @Tame public Tarantula produceTarantula = new DefangedTarantula(); } and @Specializes public class SpecializedTarantulaProducer extends TarantulaProducer { @Produces public Tarantula produceTarantula = new DefangedTarantula(); } Not the same producer but first one is swallowed cause of the @Specializes handling in OWB trunk Here the full failure of tests: Failed tests: ProducerFieldLifecycleTest>AbstractTest.beforeClass:206->AbstractTest.deployArtifact:105->AbstractJSR299Test.handleDeploymentFailure:188 » DeploymentFailure ProducerFieldLifecycleTest.testProducerFieldForNullValueNotDependent » Test E... ProducerFieldLifecycleTest>AbstractTest.beforeClass:206->AbstractTest.deployArtifact:105->AbstractJSR299Test.handleDeploymentFailure:188 » DeploymentFailure ProducerFieldLifecycleTest>AbstractTest.beforeClass:206->AbstractTest.deployArtifact:105->AbstractJSR299Test.handleDeploymentFailure:188 » DeploymentFailure ProducerFieldLifecycleTest.testProducerFieldReturnsNullIsNotDependent » Test ... ProducerFieldLifecycleTest>AbstractTest.beforeClass:206->AbstractTest.deployArtifact:105->AbstractJSR299Test.handleDeploymentFailure:188 » DeploymentFailure ProducerFieldLifecycleTest>AbstractTest.beforeClass:206->AbstractTest.deployArtifact:105->AbstractJSR299Test.handleDeploymentFailure:188 » DeploymentFailure EnterpriseProducerMethodDefinitionTest>AbstractTest.run:259->testNonStaticProducerMethodInheritedBySpecializingSubclass:45 null ProducerMethodDefinitionTest>AbstractTest.run:244->testNonStaticProducerMethodInheritedBySpecializingSubclass:232 null SpecializingBeanExtendsEnterpriseBeanTest>AbstractTest.beforeClass:206->AbstractTest.deployArtifact:126 » Expected SimpleBeanSpecializationTest>AbstractTest.run:244->testProducerMethodOnSpecializedBeanCalledOnSpecializingBean:79 null ResolutionByNameTest>AbstractTest.beforeClass:206->AbstractTest.deployArtifact:105->AbstractJSR299Test.handleDeploymentFailure:188 » DeploymentFailure SessionBeanPolicyTest>AbstractTest.beforeClass:206->AbstractTest.deployArtifact:89->AbstractJSR299Test.handleDeploymentFailure:188 » DeploymentFailure PolicyAvailabilityTest>AbstractTest.beforeClass:206->AbstractTest.deployArtifact:105->AbstractJSR299Test.handleDeploymentFailure:188 » DeploymentFailure PolicyAvailabilityTest>AbstractTest.beforeClass:206->AbstractTest.deployArtifact:105->AbstractJSR299Test.handleDeploymentFailure:188 » DeploymentFailure PolicyAvailabilityTest>AbstractTest.beforeClass:206->AbstractTest.deployArtifact:105->AbstractJSR299Test.handleDeploymentFailure:188 » DeploymentFailure PolicyAvailabilityTest>AbstractTest.beforeClass:206->AbstractTest.deployArtifact:105->AbstractJSR299Test.handleDeploymentFailure:188 » DeploymentFailure PolicyAvailabilityTest>AbstractTest.beforeClass:206->AbstractTest.deployArtifact:105->AbstractJSR299Test.handleDeploymentFailure:188 » DeploymentFailure DirectlyExtendsSimpleBeanTest>AbstractTest.beforeClass:206->AbstractTest.deployArtifact:126 » Expected Main question is: should we still pass tck for cdi 1.0? Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau