Here's the current state of the Assembly and SCA-J CAA tests: To make it a bit easier to see whats going wrong I've just updated otests runners so that missing and incorrect error messages get logged to a file in the test runner target directory, and so that messages which start with an astrix don't fail the tests so its now easier to see the state by just looking in the tuscany-oasis-sca-tests-errors.properties files (ie anything starting with an * needs investigating).
Running all the tests gives: Assembly Tests Tests run: 136, Failures: 23, Errors: 0, Skipped: 0 59 *'d messages Java CAA Tests Tests run: 157, Failures: 40, Errors: 0, Skipped: 78 39 *'d messages So thats a total of 239 issues to fix (ie 23+59 +40+78+39), and at a guess of 30 minutes an issue that would take someone about a month! If anyone wants to help the README in the top level otest folder has details on how to use the test suites - https://svn.apache.org/repos/asf/tuscany/java/sca/otest/newlayout/README ...ant
