> But since the merge fixup was still in progress, it wasn't all that
> surprising that we saw some failures.
No problem. I was just trying to gage whether the current state was "we
think it is close, and indications of problems are helpful" or "we know it
will be broken for a short while, please leave us alone until we are
ready".
>>Most of the projects are also now experiencing problems with Stylebook.
>
>We think we've just found and fixed that one. The change may have fixed
>other problems as well. Try it again with the current code.
Sorry to report, but it doesn't look that way to me. Started an update of
xalan at 1:30 pm, it finished at just after 2:00. Attempted a clean build
of xalan2 and avalon. Errors for Avalon are different that those reported
on the 14th (it looks like it might have gotten further), but still not
successful.
Reproduction is simple. Extract jakarta-avalon. Execute "build xdocs" to
see the correct operation. Copy the latest xalan.jar over the
tools\lib\xalan-2.1.0.jar, and execute "build xdocs" again.
- Sam Ruby
