Return-Path: Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 64559 invoked from network); 5 Jan 2000 21:12:19 -0000 Received: from charcot.informed.net (HELO notes.informed.net) (205.167.80.72) by 63.211.145.10 with SMTP; 5 Jan 2000 21:12:19 -0000 To: cocoon-dev@xml.apache.org Bcc: Subject: Re: can't build latest CVS X-Mailer: Lotus Notes Release 5.0a May 4, 1999 Message-ID: From: mclinden@informed.net Date: Wed, 5 Jan 2000 15:47:05 -0500 X-MIMETrack: Serialize by Router on notes.informed.net/informed dot net(Release 5.0.2 |November 4, 1999) at 01/05/2000 03:48:32 PM, Serialize complete at 01/05/2000 03:48:32 PM MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" The problem is not with Xalan but with the change in the Serializer in Xerces. If you do a CVS update of your Xerces tree, you'll get class compile errors in Xalan and Cocoon. I had to back off to an older Xerces to make Coccon compile, but now I get: java.lang.RuntimeException: Error loading logicsheet: resource://org/apache/cocoon/processor/xsp/util-java.xsl. java.io.IOException: Resource not found: org/apache/cocoon/processor/xsp/util-java.xsl at org.apache.cocoon.processor.xsp.XSPProcessor.init(XSPProcessor.java:267) So I guess that the XSP stuff checked in, today, isn't quite ready, either. Sean Seth Ladd 01/05/00 04:01 PM Please respond to cocoon-dev To: cocoon-dev@xml.apache.org cc: Subject: Re: can't build latest CVS > Note that the current Xalan CVS does not build, either. That's weird... it compiled for me today. The docs didn't compile, but I think was an external problem. I just got the CVS source earlier this morning. Seth