On Wed, Dec 8, 2010 at 9:06 AM, ant elder <[email protected]> wrote: > The versions of the xsd's that are planned to be final ones have just been > published by OASIS so we should move up to them which would also help test > them for OASIS, see: > http://lists.oasis-open.org/archives/sca-assembly/201012/msg00000.html > > ...ant > > On Wed, Dec 8, 2010 at 6:42 AM, Raymond Feng <[email protected]> wrote: >> >> I'm trying to fix it ... >> ________________________________________________________________ >> Raymond Feng >> [email protected] >> Apache Tuscany PMC member and committer: tuscany.apache.org >> Co-author of Tuscany SCA In Action book: www.tuscanyinaction.com >> Personal Web Site: www.enjoyjava.com >> ________________________________________________________________ >> On Dec 7, 2010, at 10:15 PM, Raymond Feng wrote: >> >> After debugging into the problem, I found out the OASIS OpenCSA XSDs for >> SCA specs (pulled into Tuscany under assmbly-xsd project) are inconsistent. >> For example, >> sca-core-1.1-cd05-rev1.xsd includes sca-policy-1.1-cd03-rev1.xsd >> sca-policy-1.1-cd03-rev1.xsd includes sca-core-1.1-cd06.xsd (doesn't >> exist) >> Any chance to fix the XSDs? >> [1] http://tools.oasis-open.org/version-control/svn/sca-assembly/SCA_XSDS/ >> On Dec 7, 2010, at 4:54 PM, Apache Hudson Server wrote: >> >> See >> <https://hudson.apache.org/hudson/job/Tuscany-2x/org.apache.tuscany.sca$tuscany-compliance-test-assembly/9/> >> >> >> >> > >
And why did it just start failing last night? Did we change something? Simon -- Apache Tuscany committer: tuscany.apache.org Co-author of a book about Tuscany and SCA: tuscanyinaction.com
