But there is another reason for this mail: Now with the current XSLTC we can switch to it as default processor in 2.0 too, can't we?
And what about the using the treeprocessor as default in Cocoon 2.0? If it's on the same status as in 2.1, it seems to be stable enough - even for non-development/milestone releases.
Joerg
[EMAIL PROTECTED] wrote:
joerg 2003/06/04 13:50:51
Modified: lib jars.xml lib/core xml-apis.jar Added: lib/core xalan-2.5.1.jar xercesImpl-2.4.0.jar Removed: lib/core xalan-2.3.1.jar xercesImpl-2.0.0.jar Log: updating to latest Xalan 2.5.1 and Xerces 2.4.0 releases