Re: [jboss-dev] Re: Big AS testsuite regression

I tested locally Emanuel's latest jboss-metadata 1.0.0.Beta8 (thanks1), using Adrian's new smoke test (thanks2) and I'm getting only 3 failures. Before that most tests would fail: [junit] Running org.jboss.test.ejb3.test.SimpleSessionUnitTestCase [junit] Tests run: 1, Failures: 0, Errors: 2, Time elapsed: 0.188 sec [junit] Test org.jboss.test.ejb3.test.SimpleSessionUnitTestCase FAILED ... [junit] Tests run: 10, Failures: 0, Errors: 1, Time elapsed: 9.11 sec [junit] Test org.jboss.test.naming.test.SimpleUnitTestCase FAILED ... [junit] Running org.jboss.test.web.test.WebIntegrationUnitTestCase [junit] Tests run: 37, Failures: 1, Errors: 1, Time elapsed: 24.203 sec [junit] Test org.jboss.test.web.test.WebIntegrationUnitTestCase FAILED I've switched trunk to this latest metadata release to see what gives. While there, the JIRA project of jboss metadata could use some housekeeping: http://jira.jboss.com/jira/browse/JBMETA - The issues that appear resolved for CR1 should really be assigned to Betas that are already out - I've made a new Beta8 release that would supposedly need to include JBMETA-42 then marked as released The right approach when creating a new release would be to rename CR1 to that release and introduce a new CR1. Alexey Loubyansky wrote: