Andy, I'm answering to your request (which was ... err ... how shall I say ... in French we would say "cavaliere" ... which is a nice word for saying "not expressed in a very kind manner", especially as you're the one asking for a favor !).
I am answering from the point of view of Cactus. I am a Cactus committer. I have investigated the issue by first reproducing the problem, by grabbing the jars from 29th of Feburary. I could reproduce the pb fine. Then I have updated them, one at a time, grabbing the latest one (from 1st of February) ... for each new jar I reran the build and everytime it was still failing until I grabbed the latest xercesImpl.jar ... and then everything worked fine ... :-) Conclusion : - The problem with the Cactus build was caused by an issue with Xerces 2 and Stylebook. - It seems the issue was with Xerces 2 rather than with Stylebook as it now works with the latest Xerces 2 jars. I am not subscribed to the xerces-j mailing-list and have thus not followed the latest modifications made to Xerces 2. Does it make sense it is now working fine ? Could Sam or someone else rerun the build on Nagoya to verify everything is working ? Thanks -Vincent > -----Original Message----- > From: Andy Clark [mailto:[EMAIL PROTECTED]] > Sent: 28 January 2002 18:43 > To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; security- > [EMAIL PROTECTED]; [EMAIL PROTECTED]; cactus- > [EMAIL PROTECTED]; [EMAIL PROTECTED]; turbine- > [EMAIL PROTECTED] > Subject: [Xerces2] Stop the Release! -- ALL PROJECTS PLEASE READ > > Okay, perhaps "Stop the Release!" is a little harsh but I wanted to get > your attention. ;) > > After a long journey, Xerces 2.0.0 is scheduled to be released THIS > WEEK! Aren't you excited? I know I am. However... > > I believe that there are still a few things that need to be straightened > out *before* we release. First are the changes I have listed in my > previous message titled "[Xerces2] Missing API Changes". But also very > important is fixing (or getting a commitment to fix) the projects that > are still failing with the Xerces2 build as mentioned by Sam Ruby. Just > as a reminder, you can view the output of Gump using Xerces2 at the > following URL: > > http://nagoya.apache.org/~rubys/gump/xerces2/ > > I looked at a few of the offenders and, for the most part, it is more of > a simple oversight than a problem with Xerces2. (e.g. importing > org.apache.xerces.framework.XMLParser even though it no longer exists > and isn't even used in that source file.) This makes me feel better but > all of these reported failures are a big black eye that I would like to > be healed before we release. > > Therefore, I would like an immediate response from the following > projects regarding status, planned fix, etc. so that we can move forward > with the Xerces 2.0.0 (NON-BETA!!!) release: (These are the project > currently reporting errors from the latest Gump run. If the problem has > already been fixed, please disregard this message.) > > xml-batik > jakarta-turbine-torque > jakarta-turbine-2 > jakarta-avalon-cornerstone > jakarta-cactus-22 > jakarta-tomcat-4.0 > xml-security > > If you are involved with any of these projects, please look into the > errors reported by Gump and either fix it, if you can, or tell the > Xerces-J team what is wrong with the version 2 parser. And if you choose > the latter, please make your bug report correct and complete. Thanks! > > -AndyC > > P.S. Please reply to the [EMAIL PROTECTED] mailing list to > report status. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
