Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (asf.osuosl.org: domain of ap-cocoon-dev@m.gmane.org
 designates 80.91.229.2 as permitted sender)
To: dev@cocoon.apache.org
From: Jorg Heymans <jh@domek.be>
Subject: Re: [M10N] new block layout
Date: Fri, 04 Nov 2005 11:09:09 +0100
Lines: 31
Message-ID: <dkfc04$f7e$1@sea.gmane.org>
References: <dkd6q9$147$1@sea.gmane.org> <436A43A2.8050207@nada.kth.se>
 <436A70AD.6080805@student.tuwien.ac.at> <dke5tj$bp1$1@sea.gmane.org>
 <436AEA17.7060602@dslextreme.com> <436B3097.2010900@apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
In-Reply-To: <436B3097.2010900@apache.org>
Sender: news <news@sea.gmane.org>


Carsten Ziegeler wrote:

> Yepp, if no api, no sub project for it; the same for samples and perhaps
> impl as well.

no implementation for a block , is that realistic ?

> Apart from that: +1
> 
> We should also note that this is the "best-practice" layout which you
> should use. But of course you're not forced to use it. For example a

Indeed, it's the best practice layout. It is also the layout that will
be created when doing "mvn archetype:create cocoon-block ...". It is up
to the block developer then to remove the unnecessary parts and adjust
poms accordingly.

We should proactively encourage ie enforce following things though :

- the block root directory has a pom containing all the modules for that
block.
- if there is an api module then it should be called "api".
- "impl" is the preferred module name if there is only one
implementation. Otherwise you're free to choose but an "impl" suffix is
preferred. Same should go for "samples".


Jorg