Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
From: "Carsten Ziegeler" <cziegeler@s-und-n.de>
To: <cocoon-dev@xml.apache.org>
Subject: RE: Regarding Excalibur XMLUtil and Store
Date: Mon, 12 May 2003 00:16:23 +0200
Message-ID: <LKENJPKDAIKAPKHEOCMMEEBBDJAA.cziegeler@s-und-n.de>
MIME-Version: 1.0
In-Reply-To: <20030510152230.GA7130@expresso.localdomain>
Importance: Normal
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset="us-ascii"

Hi,

here is my -1 to move XMLUtil or Store or any other common component 
back to Cocoon.
I think Jeff and Nicola Ken have already given some good arguments
against the move.

I really think the answer is plain simple: common components do belong
to a project (or subproject) or Avalon. And nowhere else.

I'm really wondering what's the purpose of moving things is? A long time
ago many in Cocoon and Avalon gave their +1 for moving common components
to Avalon. Now some of them want to move them back. Strange. There was
no -1 at that time.

And everytime you mention Avalon the first question you get is: "What
components are already available?" - So a common repository for 
components which is somehow part of Avalon is very important. Noone
wants to first download Avalon and then some parts of Cocoon and some
parts of Struts or James or whatever to get common components. This
absolutely doesn't make sense for me.

And yes, many users are using xmlutil and store outside of cocoon.

I think, we should really avoid rediscussing such things and keep
our focus on the important issues. We have a long todo list and
again renaming and moving things is really not helpfull here.

And it's not a matter of who has write access to a repository and
which emails are send.

Carsten