On Thu, May 13, 2010 at 11:48 AM, kelvin goodson <[email protected]> wrote: > I've been tying my brain in knots recently, and I believe causing > others some difficulties when updating error messages, and the > expected error messages that come from running the otests. These > latter messages are stored in files called xxxx.errors.properties and > if you have an eclipse workspace set up like mine there will be 4 of > these files, but each replicated 4 times in the workspace. > > To complicate matters the naming conventions differ. > > I've created a table for myself and some rules so that I can be sure > not to cause issues with inconsistent updates. I thought I'd share > this for anyone else who may need to deal with the files. > > Below I have labelled the files I find in my workspace as A,B,C or D, > and with an rw, ro or eph annotation as seen from a tuscany developers > perspective (eph = ephermeral -- artifact of build process) > > A = assembly (which, in otest projects without a type in their name, > is the implicit test set) > B = CAA (aka SCA-J aka Common Annotations and APIs) > C = ci (aka POJO aka Component Implementation) > D = Policy > > In a wholly consistent workspace, each copy of A,B,C or D should be > identical to any other A, B, C or D. However, there is often a > discrepency between files in Oasis svn and tuscany svn, because we > have to feed back any message changes for oasis to update. > > > > My rules for a consistent modification are > > - that for any commit touching a file "X" from those labelled > {Arw,Brw,Crw,Drw}, all other X must be updated at the same time to > match > - never update a file from {Aro, Bro, Cro, Dro, Aeph,Beph,Ceph,Deph) > (I'm setting permissions in eclipse to ensure I don't make that error > when doing a search across files for a message) > > OASIS SVN > Test_Client:src/main/resources/tuscany-oasis-sca-tests-errors.properties > Aro > Test_Client_JavaCAA:src/main/resources/tuscany-oasis-sca-tests-errors.properties > Bro > Test_Client_JavaPOJO:src/main/resources/tuscany-oasis-sca-tests-errors.properties > Cro > Test_Client_Policy:src/main/resources/tuscany-oasis-sca-tests-errors.properties > Dro > > Apache SCA trunk > svn: > tuscany-compliance-test-assembly:src/test/resources/tuscany-oasis-sca-tests-errors.properties > Arw > svn: > tuscany-compliance-test-java-caa:src/test/resources/tuscany-oasis-sca-tests-errors.properties > Brw > svn: > tuscany-compliance-test-java-ci:src/test/resources/tuscany-oasis-sca-tests-errors.properties > Crw > svn: > tuscany-compliance-test-policy:src/test/resources/tuscany-oasis-sca-tests-errors.properties > Drw > > Apache SVN for otests > eph: > tuscany-otests-asm-tests:src/main/resources/tuscany-oasis-sca-tests-errors.properties > Aeph > svn: > tuscany-otests-asm-tests:test/resources/tuscany-oasis-sca-tests-errors.properties > Arw > > eph: > tuscany-otests-policy-tests:src/main/resources/tuscany-oasis-sca-tests-errors.properties > Deph > svn: > tuscany-otests-policy-tests:test/resources/tuscany-oasis-sca-tests-errors.properties > Drw > > eph: > tuscany-otests-sca-j-caa-tests:src/main/resources/tuscany-oasis-sca-tests-errors.properties > Beph > svn: > tuscany-otests-sca-j-caa-tests:test/resources/tuscany-oasis-sca-tests-errors.properties > Brw > > eph: > tuscany-otests-sca-j-ci-tests:src/main/resources/tuscany-oasis-sca-tests-errors.properties > Ceph > svn: > tuscany-otests-sca-j-ci-tests:test/resources/tuscany-oasis-sca-tests-errors.properties > Crw > > > Kelvin. >
Here my understanding of how these work: There should be only one error properties file for each test suite location, the ones in src/main/resources/ i believe are not used and we should delete them. There are two places where we run the test suites, the ones in the in the otests tree and the ones in the 2.x trunk compliance-tests tree. The difference between these are that the otests work against the very latest test source from the OASIS SVN head whereas the ones in 2.x trunk compliance-tests work against fixed copies of the test source that Tuscany takes from known revisions of the OASIS SVN. Using the known revision of the test source for the 2.x trunk means that no matter what changes happen in the OASIS SVN the Tuscany build will be stable and we can move up to OASIS changes when we choose so the trunk build does not break. ...ant
