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.
