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: [VOTE] RE: New "module" terminology: WAS: Extending the build
 system for modules
Date: Mon, 19 Aug 2002 16:09:57 +0200
Message-ID: <GMEBIBHGAOFGJCDPJANDMELMFBAA.cziegeler@s-und-n.de>
MIME-Version: 1.0
In-Reply-To: <3D60F8BE.30904@apache.org>
Importance: Normal
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset="US-ASCII"

Nicola Ken Barozzi wrote:
> > 
> > I suggest, that a volunteer starting with implementing it, chooses the
> > name. That's simple, requires no vote and no other activities.
> > So, any volunteers?
> 
> I volunteer, since I am doing the build extension for it.
> 
Great!!

> I want to call them "module"s, as with the Apache modules.
Even greater! :)

> 
> Carsten, how shall I proceed? Branch? Dir layout? Tips? Build targets?
I don't think we need a branch - the head is our dev branch.
I would start with the dir layout as discussed and then add write a test
build for one module and see how to integrate it. From that on it's more
or less 'copy/paste'.

> 
> I would be able to commit it in the weekend.
> 
Awesom.

Carsten

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