Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (hermes.apache.org: local policy)
Mime-Version: 1.0 (Apple Message framework v619.2)
In-Reply-To: <425A8EAF.7090502@apache.org>
References: <20050409083134.46541.qmail@minotaur.apache.org>
 <425A36D5.4010809@nada.kth.se> <425A3A7B.5030203@apache.org>
 <425A6B42.1040009@nada.kth.se> <425A7094.8040906@apache.org>
 <425A8A7A.1030203@nada.kth.se> <425A8EAF.7090502@apache.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <255a9c1e1ee0934507a1f5447f3ef066@betaversion.org>
Content-Transfer-Encoding: 7bit
From: Pier Fumagalli <pier@betaversion.org>
Subject: Re: Directory structure of blocks
Date: Tue, 12 Apr 2005 10:20:32 +0100
To: dev@cocoon.apache.org

On 11 Apr 2005, at 15:50, Reinhard Poetz wrote:
> Daniel Fagerstrom wrote:
>
>> Ok, I had some remembrance that we had decided to have a particular 
>> directory structure on the COBs, but I couldn't find any 
>> documentation on that, do you have any link or example?
>
> no. But AFAIK there aren't many rules. Those that I know of are:
>
> Blocks have a block.xml descriptor and a COB-INF directory, that can 
> contain a directory "classes" and "lib".
> The block's root sitemap (if there exists any) is defined by the 
> block.xml.
>
> I don't know why we named it "COB-INF" but there was (still is?) a 
> good reason for this because I remember some long discussion. Apart 
> from this I'm not sure where to put "block.xml". In analogy to WAR 
> files it should be "COB-INF/block.xml".
>
> If the reasons for COB-INF vanished in the meantime, I propose 
> following directory structure:
>
> --------------------------------------------------------------
> [cocoon block] [DIR]
>  |
>  +-- BLOCK-INF [DIR]
>       +-- block.xml
>       +-- classes [DIR]
>       +-- lib [DIR]
> --------------------------------------------------------------
>
> WDYT?

Again, to sound stupid, but why in the world a cocoon block would 
contain classes and libraries? Those should be external "components" 
_required_ by the block, right???

	Pier