Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 76519 invoked by uid 500); 1 May 2003 07:04:01 -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 76375 invoked from network); 1 May 2003 07:03:56 -0000 Received: from smtp-relay02.x-mailer.co.uk (212.69.217.31) by daedalus.apache.org with SMTP; 1 May 2003 07:03:56 -0000 Received: from [212.69.205.254] (helo=codeconsult.dsvr.co.uk) by smtp-relay02.x-mailer.co.uk with esmtp (Exim 4.12) id 19B86u-0001OK-00 for cocoon-dev@xml.apache.org; Thu, 01 May 2003 08:04:04 +0100 Received: from codeconsult.ch (lsb-catv-1-p211.vtxnet.ch [212.147.5.211]) by codeconsult.dsvr.co.uk (8.11.6/8.11.6) with ESMTP id h41742824518 for ; Thu, 1 May 2003 08:04:04 +0100 Date: Thu, 1 May 2003 09:04:00 +0200 Mime-Version: 1.0 (Apple Message framework v552) Content-Type: text/plain; charset=US-ASCII; format=flowed Subject: Is a separate cocoon.xconf for "build docs" really needed? From: Bertrand Delacretaz To: cocoon-dev@xml.apache.org Content-Transfer-Encoding: 7bit Message-Id: <15A3CB15-7BA3-11D7-81EB-000393CFE402@codeconsult.ch> X-Mailer: Apple Mail (2.552) X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N See http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19507 for details. Currently src/documentation/cocoon.xconf has invalid component declarations, I could probably fix them but why not use the standard src/webapp/WEB-INF/cocoon.xconf for docs as well? Having one .xconf would make maintenance easier IMHO. -Bertrand