summaryrefslogtreecommitdiffstats
path: root/otest/newlayout/tuscany-test-runner (follow)
Commit message (Expand)AuthorAgeFilesLines
* Changes to make the otest dev environment run from a completely clean reposlaws2011-07-051-1/+1
* Fixes to match latest OASIS changesslaws2011-01-132-8/+1
* TUSCANY-3709 Do not aggregate schema types into facade WSDL, check local inli...bdaniel2010-10-281-2/+2
* fix for name changeslaws2010-10-141-1/+1
* switch to new distro structureslaws2010-10-121-45/+9
* Disable dependency on org.oasis-open.sca as these artifacts are not published...slaws2010-10-051-0/+4
* Fix up existing pom to generate jar to be used by trunk compliance. Removes t...slaws2010-09-161-3/+74
* Catch up with schema changes which affect the schema validation error messagesslaws2010-08-201-2/+2
* TUSCANY-3642 Allow policy information on interfaces to apply to services and ...bdaniel2010-08-051-0/+1
* make ASM10003 test case pass by updating expected error message in line with ...kelvingoodson2010-07-271-1/+1
* coreq commit for r979633 -- error message updateskelvingoodson2010-07-271-2/+2
* message definition catchupkelvingoodson2010-05-171-2/+2
* error message updates for ci/pojo otestskelvingoodson2010-05-141-7/+7
* fix up expected assembly test messageskelvingoodson2010-05-121-13/+13
* TUSCANY-3530 - new failure messages for 5038 and 5039slaws2010-05-061-2/+2
* TUSCANY-3531 - add expected error message for ASM_5040slaws2010-04-091-1/+1
* Correct expect message for ASM_13002 following OASIS schema changesslaws2010-04-081-1/+1
* Add expected message for ASM_6039slaws2010-04-081-1/+1
* Add expected message for ASM_6036slaws2010-04-081-1/+1
* TUSCANY-3527 add expected error message for ASM_9005slaws2010-04-081-1/+1
* TUSCANY-3526 - added commented out line that will launch with OSGi for testin...slaws2010-04-071-0/+2
* Updates following OASIS schema change and latest round of test changes. slaws2010-03-251-6/+12
* TUSCANY-3503 - fix up error messages to take account of removal of automatic ...slaws2010-03-181-2/+2
* Properly handling how to retrieve runtime/execution error messageslresende2010-03-131-3/+14
* Remove reference to specific lines/columnsslaws2010-03-091-10/+10
* TUSCANY-3486 correct error messages to catch up with runtime changesslaws2010-03-081-1/+1
* Fix up OSGi version of the bridge alsoslaws2010-03-041-20/+7
* Fix assembly error messages to catch up with Tuscany code changesslaws2010-03-041-3/+3
* Fix tuscany runtime bridge to match recent OASIS changesslaws2010-03-041-22/+7
* update messages with conformance statementskelvingoodson2010-03-031-9/+9
* update messages with conformance statementskelvingoodson2010-03-031-8/+8
* update messages with conformance statementskelvingoodson2010-03-031-12/+12
* update messages with conformance statementskelvingoodson2010-03-021-9/+9
* Correct error message by *** line number of errorantelder2010-03-011-1/+1
* Correct ws binding to point to the new versionslaws2010-02-231-1/+1
* fix white space mis-matches in expected messageskelvingoodson2010-02-121-8/+8
* further update expected messages to match new problem determination infokelvingoodson2010-02-121-2/+2
* update expected messages to match new problem determination infokelvingoodson2010-02-121-12/+12
* Remove the calls to Node.destroyrfeng2010-02-092-3/+0
* Update to match OASIS version. New namespace and a few other changes that we ...slaws2010-01-081-54/+55
* Fix error messagesrfeng2009-12-091-2/+2
* match expected outputs to updated error messageskelvingoodson2009-11-271-2/+2
* match expected outputs to updated error messageskelvingoodson2009-11-271-3/+3
* match expected outputs to updated error messageskelvingoodson2009-11-261-3/+3
* Catch up with a change in context processing for the policy testsslaws2009-11-251-2/+2
* match expected output for DuplicateReference errors to include conformance st...kelvingoodson2009-11-241-6/+6
* match expected output for ASM_4008 to updated error messagekelvingoodson2009-11-241-3/+3
* Update error messages to take account of slight clarification in message for ...slaws2009-11-231-1/+1
* Add conformance number to start of 10001 error messageslaws2009-11-111-1/+1
* Update error message to take account of the slight extension to the duplicate...slaws2009-11-111-1/+1