Saxon

Legacy ID: #8083698 Legacy Poster: Michael Kay (mhkay)

I've reproduced the problem and am investigating. Clearly some kind of build error. Rather embarrassing, it means that (a) I was wrong to assume that simple build errors would always be found within 24 hours of release, and (b) the "quick regression test" that I do for new maintenance builds is clearly insufficient.

Legacy ID: #8083893 Legacy Poster: Michael Kay (mhkay)

I've investigated this with the powershell listdependencies script (modified to show .exe files as well as .dlls) and there are certainly some nasty anomalies, as follows: In EE: saxon9ee-api refers to saxon9ee 9.3.0.1 (!) Transform.exe, Validate.exe, and Query.exe all refer to saxon9ee.dll 9.2.0.3 In PE: saxon9pe-api.dll refers to saxon9pe.dll 9.2.0.2 Transform.exe and Query.exe both refer to saxon9ee.dll 9.2.0.3 In HE: Transform.exe and Query.exe both refer to saxon9ee.dll 9.2.0.3 At present I'm mystified as to how these errors arose: I suspect it was through Ant running the steps of the build process in a different order from that expected, plus not clearing out contents of temporary directories used during the execution of the script. Anyway, it looks as if I'm going to have to do a re-build. Because the source in SVN has changed it makes most sense to do the new build on the latest source and call it 9.2.0.6. Sorry for the inconvenience.

Legacy ID: #8086427 Legacy Poster: Michael Kay (mhkay)

I've posted further details of the problem at https://sourceforge.net/tracker/?func=detail&aid=2952924&group_id=29872&atid=397617 I'm busy testing a build of 9.2.0.6 to fix the problem