Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 48253 invoked by uid 500); 11 Mar 2002 21:28:14 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 48224 invoked from network); 11 Mar 2002 21:28:13 -0000 From: "Steven Noels" To: Subject: RE: POI Serialization code committed Date: Mon, 11 Mar 2002 22:28:18 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal In-Reply-To: <708971104.1015879052906.JavaMail.SYSTEM@webmail> X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Andy wrote: > Steven wrote: > > > > So I am all unofficial +1 for having a separate module for Cocoon > > contributions, where we can add the POI integration work, if enough > > people step up as a maintainer. > > +1 if there are enough to justify it. > I hope the remainder of my arguments are not lost, however. This is suboptimal solution until POI admits it really should become part of their own codebase. Only the real Cocoon-specific classes should eventually go into the contrib section of Cocoon CVS. POI supporting XML is not in scope for Cocoon, neither. But anyway (tm). ;-) --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org