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 includes SPF record at
 spf.trusted-forwarder.org)
Message-ID: <425A8EAF.7090502@apache.org>
Date: Mon, 11 Apr 2005 16:50:23 +0200
From: Reinhard Poetz <reinhard@apache.org>
User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Directory structure of blocks
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>
In-Reply-To: <425A8A7A.1030203@nada.kth.se>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

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?

-- 
Reinhard Pötz           Independent Consultant, Trainer & (IT)-Coach 

{Software Engineering, Open Source, Web Applications, Apache Cocoon}

                                        web(log): http://www.poetz.cc
--------------------------------------------------------------------