We are shipping Xerces 2.4.0; should consider an
upgrade to 2.5.0 which has been released.
Make that 2.6.0 now.
Who owns this module?! We should really have taken care of things like
this in time for every release.
Old Xerces might be responsible for issue #37994, not clear.
This is important; using an obsolete library greatly increases the
chances that we will clash with 3rd-party tools (see e.g. issue
#37994), as well as exposing us to bugs that the library vendor is not
going to have any interest in backporting fixes for.
1. I have tried to:
- replace NB's xerces with (renamed) xerces 2.6.0
- replace NB's xerces with (renamed) xerces from
RIT's lib directory, and this case seems to be
a workaround of the issue. I have not noticed any
side effects during 3-4 hours of work.
2. I have notified Anton (RIT) about the issue.
Sorry for comment here, it is for issue #37994
Trying it out in sources.
Created branch xerces_260_xalan_252 in libs module rooted from
BLD200312221900 to cover this change as well as issue #38301. Seems to
committed 1.11 libs/public.properties
committed 1.12 libs/external/.cvsignore
committed 1.15 libs/external/build.xml
removed 1.1 libs/external/xalan-2.5.1.jar.scrambled
committed 1.2 libs/external/xalan-2.5.2.jar.scrambled
removed 1.1 libs/external/xerces-2.4.0-1.jar.scrambled
committed 1.2 libs/external/xerces-2.6.0.jar.scrambled
committed 1.4 libs/xalan/manifest.mf
committed 1.6 libs/xerces/manifest.mf