cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Pogue <>
Subject Re: Can't build latest Snapshot...
Date Fri, 07 Jan 2000 22:50:48 GMT
Here I am replying to my own email...I like to talk to myself!  :-)
I'm posting this here for those Cocoon developers who hit the Xerces
build problem in the latest daily snapshot of Xerces, and who do not
regularly read the Xerces developer mailing list.

I checked, and the break in last night's snapshot of Xerces-J has been
fixed as of today, and should not be a problem in the next snapshot.  Of
course, it's always possible that another problem will arise in the new
snapshot, but at least this one has been fixed.  I don't know when the
system will automatically create the next daily snapshot.

Reminder:  the daily snapshots out of CVS are likely to be much less
stable than the regular published tarballs.  If you choose to use them,
and you find a problem, please report it on the appropriate list, so
somebody can fix it right away...  

There is only minimal testing done on the daily snapshots.  There is
lots of comprehensive testing, on many different OS/JDK/compiler
combinations (roughly 15-20 configurations for Xerces-J, 10 or so for
Xerces-C, if I remember right), done on the Xerces tarballs.  


Mike Pogue wrote:
> wrote:
> >
> > > Actually, It is xerces that won't build right now.  I
> > > have the latest snapshot.  Anyone else having trouble?
> >
> > Yes. Apparently since Xalan was updated to work with
> > Xerces, Xerces was updated with changes to DOM events
> > that do not build, correctly.
> >
> If this is the Xalan compile error that was posted to the Xerces list
> earlier this week, Scott Boag said on Wednesday that he was working to
> update Xalan to match the change to BaseSerializer.
> If this is something new, could somebody post the compile error to the
> Xerces list?
> Or send it to me, and I'll do it...Several of the Xerces developers
> don't read the Cocoon list.
> ...
> > I am sorry to be so long-winded. But last week I had a
> > prototype that was sufficiently functional that I was ready
> > to commit a development process to it. For a week, now,
> > I have been dead in the water.
> >
> > It is just a little bit frustrating.
> If I were you, I would be very reluctant to base any development process
> on the current daily snapshots, which are changing rapidly to catch up
> with the Schema and DOM L2 specs, and to fune tune the new Serializer
> code (on the Xerces side).  I'm sure there are many Xalan changes going
> in right now, too.
> Note: the tarballs are a lot more stable (and tested) than the daily
> snapshots.  I understand your frustration, though, because there's a
> time lag from when Xerces puts out a tarball, to when Xalan updates and
> does the same, and they match and can be used together.
> We are putting in place a bug tracking system, so that people can more
> easily submit these problems as they are discovered.  It's not ready
> yet, though.
> Mike

View raw message