>> >> A full build to test the 2022 changes has made 2016 work somewhat >> mysteriously. > > 2016 is one of the ones i'd fixed > >> mysteriously. I'm still not seeing failures in 5001 so would be >> interested in hearing if anyone else is. >>
I only meant that I thought that I had the latest code, including all your fixes, and I was still seeing 2016 fail in my previous post. However I must have been doing something wrong as it subsequently worked. > > 5001 is still failing for me on the very latest otest and trunk code. > I'll do some debugging. > > ...ant > Ok, splendid. Simon -- Apache Tuscany committer: tuscany.apache.org Co-author of a book about Tuscany and SCA: tuscanyinaction.com
