Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
Message-ID: <111CCE21E90FD511A7BE0002B325AFDEEC178C@MAIL>
From: Argyn Kuketayev <Argyn.Kuketayev@plateau.com>
To: "'cocoon-dev@xml.apache.org'" <cocoon-dev@xml.apache.org>
Subject: RE: [Proposal] Cocoon Organization
Date: Wed, 31 Jul 2002 14:14:35 -0400
MIME-Version: 1.0
Content-Type: text/plain

whatever you do, the option to have everything in one jar/war must be
preserved. I'd rather deal with one elephant, than 25 rhinos.

> -----Original Message-----
> From: Vadim Gritsenko [mailto:vadim.gritsenko@verizon.net]
> Sent: Wednesday, July 31, 2002 2:09 PM
> To: cocoon-dev@xml.apache.org; haul@dvs1.informatik.tu-darmstadt.de
> Subject: RE: [Proposal] Cocoon Organization

> If you to put esql and sql transformer into different 
> subprojects, then
> situation will just get worse. They must be in the same 
> subproject, and
> should be unified and integrated as much as possible, to reduce
> repetitive code and make maintainance / feature additions easy.

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org