[weld-issues] [JBoss JIRA] Assigned: (CDITCK-204) TCK Harness property configuration broken
[ https://issues.jboss.org/browse/CDITCK-204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jozef Hartinger reassigned CDITCK-204: -- Assignee: Jozef Hartinger TCK Harness property configuration broken - Key: CDITCK-204 URL: https://issues.jboss.org/browse/CDITCK-204 Project: CDI TCK Issue Type: Bug Security Level: Public(Everyone can see) Components: Infrastructure Affects Versions: 1.0.4.CR2 Reporter: Sivakumar Thyagarajan Assignee: Jozef Hartinger As per http://docs.jboss.org/cdi/tck/reference/latest/en-US/html/test-harness-configuration.html#test-harness-properties, a custom ConfigurationBuilder or an implementation of the SPI class such as org.jboss.jsr299.tck.spi.Beans could be provided by the TCK executor through a system property specifying the FQCN of the implementation class. However while trying to plug in a custom Beans SPI implementation or a ConfigurationBuilder using the system property, the default PropertiesBasedConfigurationBuilder seems to collate [1] all the properties file in the classpath and include the default implementations (bundled in the porting package or harness) as well. [testng] Exception in thread main java.lang.IllegalArgumentException: More than one implementation of Beans specified by org.jboss.jsr299.tck.spi.Beans, not sure which one to use! [testng] at org.jboss.testharness.properties.PropertiesManager.getClassValue(PropertiesManager.java:159) [testng] at org.jboss.testharness.properties.PropertiesManager.getInstanceValue(PropertiesManager.java:169) [testng] at org.jboss.testharness.impl.PropertiesBasedConfigurationBuilder.getInstanceValue(PropertiesBasedConfigurationBuilder.java:62) This prevents configuration of the TCK to use a custom SPI class implementation and/or ConfigurationBuilder. The only workaround seems to be providing a modified version of the existing porting package class and ensuring that it is loaded ahead. [1] [1] http://grepcode.com/file/repository.jboss.org/nexus/content/repositories/releases/org.jboss.test-harness/jboss-test-harness/1.1.0-CR5/org/jboss/testharness/impl/ConfigurationFactory.java#17 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Commented: (CDITCK-209) TCK tests should not cleanup app context explicitly
[ https://issues.jboss.org/browse/CDITCK-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12594972#comment-12594972 ] Jozef Hartinger commented on CDITCK-209: Ales, does this apply to the Application context only? In other words, is it safe to destroy other contexts besides Application (Request, Session) explicitly in the test? TCK tests should not cleanup app context explicitly --- Key: CDITCK-209 URL: https://issues.jboss.org/browse/CDITCK-209 Project: CDI TCK Issue Type: Task Security Level: Public(Everyone can see) Components: Tests Affects Versions: 1.0.4.Final Reporter: Ales Justin Assignee: Jozef Hartinger Fix For: 1.1.0.CR1 Atm org.jboss.jsr299.tck.tests.context.DestroyForSameCreationalContext2Test cleans up app context, which breaks context lifecycle handling asymmetry. See WELD-858 for the use case. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Commented: (CDITCK-209) TCK tests should not cleanup app context explicitly
[ https://issues.jboss.org/browse/CDITCK-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12595008#comment-12595008 ] Pete Muir commented on CDITCK-209: -- Yes, others are fine. TCK tests should not cleanup app context explicitly --- Key: CDITCK-209 URL: https://issues.jboss.org/browse/CDITCK-209 Project: CDI TCK Issue Type: Task Security Level: Public(Everyone can see) Components: Tests Affects Versions: 1.0.4.Final Reporter: Ales Justin Assignee: Jozef Hartinger Fix For: 1.1.0.CR1 Atm org.jboss.jsr299.tck.tests.context.DestroyForSameCreationalContext2Test cleans up app context, which breaks context lifecycle handling asymmetry. See WELD-858 for the use case. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
