On Wed, Sep 15, 2010 at 10:30 AM, ant elder <[email protected]> wrote: > On Wed, Sep 15, 2010 at 10:19 AM, Simon Laws <[email protected]> > wrote: >> I'm seeing lots of errors when trunk/compliance runs at the moment. >> However the only error I see when I run otest/newlayout is the >> JCA_11021 failure related to lack of holder support in the runtime >> (TUSCANY-3664). >> >> Firstly, I assume others see failures in trunk/compliance. If so can >> we now upgrade the versions of the otests that the trunk compliance >> directories use so that the latest versions get used? We can then >> mostly remove the exclusions from the trunk/compliance poms and have a >> more accurate record of whether we're breaking otests as we make >> changes. >> >> I'm posting rather than just getting on and doing it because we build >> zips of the tests, in lieu of OASIS publishing them at the moment, but >> these zips are help in Ant's p.a.o space [1]. They haven't been >> updated since May. >> >> > > I also see a lot of failures, i did have a quick look though and it > looked like they (or the few i looked at) were due to something else > using holding a port open which i'd guess was from one of the many > other earlier fails in the build i'm also seeing. > > Really we should move from having these artifacts on my p.a.o space to > being in the tuscany svn mvn repo, anyone could do that and update the > artifacts otherwise i will get to but need to finish the jms testcases > doc draft first which hopefully I'll get done today. > > ...ant >
Do you have the scripts/changes you used to generate the zips etc? Simon -- Apache Tuscany committer: tuscany.apache.org Co-author of a book about Tuscany and SCA: tuscanyinaction.com
