PROTECTED]
>Sent: Monday, December 01, 2003 9:44 AM
>To: Tomcat Developers List
>Subject: Re: [5.0] New Xerces release
>
>Jeanfrancois Arcand wrote:
>> -1 for 5.0.16
>>
>> Every release of Xerces is dangerous (buggy!), and to quote Rémy: "2.6
>> *apparently*
Jeanfrancois Arcand wrote:
-1 for 5.0.16
Every release of Xerces is dangerous (buggy!), and to quote Rémy: "2.6
*apparently* works" scares me ;-)
I did quickly test Xerces 2.6.0, but Xerces 2.5.0 is the build that I've
included in Tomcat 5.0.16.
Rémy
-
Dominik Drzewiecki wrote:
There's a new Xerce 2.6 release, but I still plan to include 2.5 in
tomorrow's tag (which works). 2.6 *apparently* works (without any
noticeable improvements either), but I fear possible schema related
regressions. So not upgrading for this ta
>There's a new Xerce 2.6 release, but I still plan to include 2.5 in
>tomorrow's tag (which works). 2.6 *apparently* works (without any
>noticeable improvements either), but I fear possible schema related
>regressions. So not upgrading for this tag is intentional, and I'll
>update build.propert
Costin Manolache wrote:
Remy Maucherat wrote:
There's a new Xerce 2.6 release, but I still plan to include 2.5 in
tomorrow's tag (which works). 2.6 *apparently* works (without any
noticeable improvements either), but I fear possible schema related
regressions. So not upgrading for this tag is i
Remy Maucherat wrote:
There's a new Xerce 2.6 release, but I still plan to include 2.5 in
tomorrow's tag (which works). 2.6 *apparently* works (without any
noticeable improvements either), but I fear possible schema related
regressions. So not upgrading for this tag is intentional, and I'll
upd
There's a new Xerce 2.6 release, but I still plan to include 2.5 in
tomorrow's tag (which works). 2.6 *apparently* works (without any
noticeable improvements either), but I fear possible schema related
regressions. So not upgrading for this tag is intentional, and I'll
update build.properties r
