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 62723 invoked from network); 19 Jan 2001 14:23:23 -0000 Received: from pcow008o.blueyonder.co.uk (HELO blueyonder.co.uk) (195.188.53.117) by h31.sny.collab.net with SMTP; 19 Jan 2001 14:23:23 -0000 Received: from mail pickup service by blueyonder.co.uk with Microsoft SMTPSVC; Fri, 19 Jan 2001 14:24:56 +0000 Content-Class: urn:content-classes:message From: To: Subject: RE: [VOTE] Re: [C1] and xalan2 Date: Fri, 19 Jan 2001 14:24:56 -0000 Message-ID: <04fc01c08223$98d647a0$ce8517ac@blueyonder.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft CDO for Windows 2000 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Thread-Index: AcCCI5jWCRP/n+0kEdSsRQCQJ04Bnw== X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N > Which versions should C1 now use? Options: >=20 > 1. Just upgrade to Xalan 1.2.2 and Xerces 1.2.3 (cocoon 1 is very = behind on=20 > this!), but tweak things (Steffen's patches) so Xalan2 can be used. = -1. >=20 > 2. As (1) but include a Xalan2Transformer so people can choose to use = Xalan1=20 > or Xalan2 in cocoon.properties. But we would not ship Xalan2 - it = would be=20 > an optional download, like FESI. +1. >=20 > 3. Switch over to Xalan2 completely. Bad idea since it is still in = beta and=20 > based on unstable APIs. -1. >=20 > 4. Don't upgrade anything. -1. I'm +1 for (2) as well - keep compatible now, allow for upgrading in the = future. Ross