Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
Date: Fri, 09 May 2003 21:32:56 +0200
From: Jeremias Maerki <dev.jeremias@greenmail.ch>
To: cocoon-dev@xml.apache.org
Subject: Re: Regarding Excalibur XMLUtil and Store
In-Reply-To: <3EBBDA44.4090207@apache.org>
References: <1182B3F1-8234-11D7-9120-000393B61B56@apache.org>
 <3EBBDA44.4090207@apache.org>
Message-Id: <20030509213059.973C.DEV.JEREMIAS@greenmail.ch>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit


On 09.05.2003 18:41:40 Nicola Ken Barozzi wrote:
> 
> 
> Peter Royal wrote, On 09/05/2003 17.36:
> > On Thursday, May 8, 2003, at 09:11  PM, Stefano Mazzocchi wrote:
> > 
> >>> These two components are scheduled for the Excalibur Phase III
> >>> release.  The problem is that the documentation for them is non-
> >>> existant.  Since these components originated from Cocoon, can
> >>> we have some volunteers to write up some docs for them?
> >>>
> >>> We will be happy to commit anything we get.  I think it will be
> >>> better if the folks who use them the most wrote the docs than
> >>> those of us who do not use it as often.
> >>
> >>
> >> Better yet: put it back where they belong: here!
> >>
> >> Anybody against this?
> 
> -0
> 
> Anybody against having Cocoon committers access the Avalon Component 
> CVS? Or is moving things around just a way to /feel/ better?

It shouldn't be that difficult to come up with an "Avalon Commons" I
would believe.

> Originated from != used only by
> 
> > I'm -0.
> > 
> > My only request is that, wherever the components live, that they be 
> > buildable as discrete components, available outside of cocoon.jar
> > -pete
> 
> Same here.

and here.


Jeremias Maerki