uration]Re: CODE FREEZE
Hi Elena,
Since you have annonded the CODE FREEZE. I am not committing the fix
but have attatched with this mail :-)
Problem is pretty serious because DTD pipeline is not set properly.
Therefore any DOM based parser parsing XML document containin DOCTYPE
delcarations won
ROTECTED]>
Subject: Re: Important [Bug in XIncludeParserConfiguration]Re: CODE FREEZE
Hi Elena,
Since you have annonded the CODE FREEZE. I am not committing the fix
but have attatched with this mail :-)
Problem is pretty serious because DTD pipeline is not set properly.
Therefore any DOM b
Hi Elena,
Since you have annonded the CODE FREEZE. I am not committing the fix
but have attatched with this mail :-)
Problem is pretty serious because DTD pipeline is not set properly.
Therefore any DOM based parser parsing XML document containin DOCTYPE
delcarations wont be able to get the
be
sending the fix in few minutes.
Thanks
Neeraj
Elena Litani wrote:
Code freeze starts NOW till further notice.
Committers can only commit minor doc changes (e.g. last minute fixes for
releases.xml).
If anyone finds a serious bug, please post a message to the mailing list
and we will postpone
Code freeze starts NOW till further notice.
Committers can only commit minor doc changes (e.g. last minute fixes for
releases.xml).
If anyone finds a serious bug, please post a message to the mailing list
and we will postpone the release.
Otherwise, we plan to go ahead and build and
Hi all,
I plan to build and release next Xerces release on Thursday (July 30),
therefore
please DO NOT COMMIT any code until the release.
If you have any concerns, please let me know ASAP.
Thank you,
--
Elena Litani / IBM Toronto
--
Elena Litani wrote:
Do you think this release should be a point release (2.3.1) or a release
(2.4) given the XNI changes..?
Any API changes that impact applications (i.e. outside
of the implementation) should be done in a dot release.
Therefore, I would suggest using "2.4.0" for this
release, regar
Hi all,
We plan to build and release next Xerces release on Wednesday (March
26), therefore
we ask you NOT TO COMMIT any code starting on Tuesday 11:59PM Eastern
until further notice.
If you have any concerns, please let us know ASAP.
Do you think this release should be a point release (2.3.1)
> Running domunit 0.0.6 showed a whole slew of null pointer
> exceptions occurring with the deferred DOM implementation.
> However, I fixed all of these yesterday which probably
> were committed after Gump extracted the sources and ran
> the latest rounds of tests.
I just run domunit against a CV
Andy Clark wrote:
>
> Running domunit 0.0.6 showed a whole slew of null pointer
> exceptions occurring with the deferred DOM implementation.
> However, I fixed all of these yesterday which probably
> were committed after Gump extracted the sources and ran
> the latest rounds of tests.
>
> So with
Sam Ruby wrote:
> Reproduction is a simple as trying to build jakarta-struts. Similar
> problems can be seen building xml-fop, dom4j, jakarta-cactus,
> avalon-phoenix, tomcat 4.0, and the ant test run-tests target.
I haven't tried extracting the projects having problems,
setting them up to build
Andy Clark wrote:
> As I mentioned in a response to Arun's message, I have a very
> serious DOM bug in the deferred case (the default DOM, btw)
Fixed. Why is it that the smallest errors take the longest
time to find? Oh well.
--
Andy Clark * IBM, TRL - Japan * [EMAIL PROTECTED]
---
No problem here.
- Original Message -
From: "Elena Litani" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Wednesday, October 24, 2001 12:44 PM
Subject: Xerces2] Beta3 Release Plan - (THURSDAY CODE FREEZE)
Elena Litani wrote:
>
> Ted, Edwin, please, let us know as soon as possible if you have any
> concerns about the current plan.
Can others express an opinion too. ;-) Not that you can stop me. ;-)
I would suggest that the following error be looked into prior to shipping.
http://nagoya.apache.o
Elena Litani wrote:
> The package reorganization is scheduled for Thursday morning [25 Oct]
> and we ask you NOT TO COMMIT any code starting on Thursday 7AM Eastern
> time until further notice.
I have noticed a lot of problems with the DOM implementation
in Xerces2 which don't get excercised beca
Arun Yadav alerted me to some serious DOM issues in the
current code that I'm trying to rectify now. I'll either
solve the problem and check it in ...or... I will not
commit the changes that cause even more problems. :(
Either way, I'll follow up on this message and let you
know how it goes.
--
Elena Litani wrote:
>
> The package reorganization is scheduled for Thursday morning [25 Oct]
> and we ask you NOT TO COMMIT any code starting on Thursday 7AM Eastern
> time until further notice.
OK, sounds good.
-Edwin
-
To u
We will attempt to build Beta3 on Thursday afternoon and post the
release on Friday.
Beta3 will include alpha support for XML Schema 1.0 REC, and thus we
plan to do some package reorganization to move schema related code out
of v2 directory.
The package reorganization is scheduled for Thursday m
As scheduled, I will proceed with the change in CVS to move X1 on a
branch and X2 on the trunc.
Please, DO NOT COMMIT any changes until further notice.
Thanks.
--
Arnaud Le Hors - IBM, XML Standards Strategy Group / W3C AC Rep.
---
19 matches
Mail list logo
