On Wed, Oct 13, 2010 at 12:44 PM, Simon Laws <[email protected]> wrote: > On Wed, Oct 13, 2010 at 12:39 PM, Simon Laws <[email protected]> > wrote: >> On Wed, Oct 13, 2010 at 12:31 PM, ant elder <[email protected]> wrote: >>> Whats the status of the compliance tests in trunk? I've managed to get >>> a build through all the way to the java-ci tests without failing which >>> is further than its got for ages, that fails with missing dependencies >>> and compile errors and looking at the pom.xml its still using the old >>> feature (which doesn't exist) not the base-runtime but updating to >>> that gets compile errors and looking in tuscany-otests-sca-j-ci-tests >>> it looks like its missing a lot of things. Has that got extra changes >>> that need to be published? >>> >>> ...ant >>> >> >> Not as far as I know. I've getting a clean build at the moment. I see >> what you mean about the feature. I didn't spot that so I must be >> running of a version cached in my local repo. I'll change it here also >> and see what happens. >> >> Simon >> >> -- >> Apache Tuscany committer: tuscany.apache.org >> Co-author of a book about Tuscany and SCA: tuscanyinaction.com >> > > I committed an updated pom. Can you give that a spin and see what > happens for you before I fix the rest of them. > > Simon >
That helps but it turns out the problem is that the tuscany-otests-* jars in the tuscany svn repo aren't updating even with mvn -U so i had to delete them from my local repo to get the up to date ones downloaded. The java-ci tests are run ok for me now. ...ant
