Hi Edwin,
Just saw your commit message; so we've crossed the rubicon on this one. :
-)
Cheers,
Neil
Neil Graham
XML Parser Development
IBM Toronto Lab
Phone: 905-413-3519, T/L 969-3519
E-mail: [EMAIL PROTECTED]
Neil Graham
10/15/2001 05:41 PM
To: [EMAIL PROTECTED]
cc:
From: Neil Graham/Toronto/IBM@IBMCA
Subject: Re: [xerces1]: 1.4.4 release, anyone? (Document link: Neil
Graham)
Hi Edwin,
Thanks for fixing the xml-commons code to eliminate the crimson reference.
I agree that, eventually, we'll want to take the source from the
xml-commons module. This is probably a midterm goal for Xerces2, I'd
imagine. I suspect it would be too much of a change for the Xerces1
codebase at this stage though.
Are you planning to copy the code over to Xerces1? I'm still not entirely
sure that large a change is the best thing, but if you're confident enough
that it'll fix many more bugs than it might introduce then I suppose
there's no reason not to do it.
Cheers,
Neil
Neil Graham
XML Parser Development
IBM Toronto Lab
Phone: 905-413-3519, T/L 969-3519
E-mail: [EMAIL PROTECTED]
Edwin Goei <[EMAIL PROTECTED]> on 10/12/2001 08:52:17 PM
Please respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc:
Subject: Re: [xerces1]: 1.4.4 release, anyone?
Edwin Goei wrote:
>
> How about if I start working on the copying task right now? Not sure if
> I'll be able to finish before I have to leave work.
Another option would be to just manually copy the javax.xml.parser code
from xml-commons, which is what Shane Curcuru did recently for Xalan
(but different package probably??).
What I was planning to do was to provide an automatic way of syncing the
code. I was planning to prototype something and provide a patch to see
what you all thought. One difference is that it will require two CVS
trees to be present for a build. I suppose ant has a CVS checkout task,
but I wasn't planning on using that.
-Edwin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
