Return-Path: 
 <dev-return-81368-apmail-cocoon-dev-archive=cocoon.apache.org@cocoon.apache.org>
Delivered-To: apmail-cocoon-dev-archive@www.apache.org
Received: (qmail 16925 invoked from network); 3 Nov 2005 20:19:27 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 3 Nov 2005 20:19:26 -0000
Received: (qmail 60682 invoked by uid 500); 3 Nov 2005 20:19:23 -0000
Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org
Received: (qmail 60605 invoked by uid 500); 3 Nov 2005 20:19:22 -0000
Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:dev-help@cocoon.apache.org>
list-unsubscribe: <mailto:dev-unsubscribe@cocoon.apache.org>
List-Post: <mailto:dev@cocoon.apache.org>
Reply-To: dev@cocoon.apache.org
List-Id: <dev.cocoon.apache.org>
Delivered-To: mailing list dev@cocoon.apache.org
Received: (qmail 60594 invoked by uid 99); 3 Nov 2005 20:19:22 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Nov 2005 12:19:22 -0800
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=
X-Spam-Check-By: apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Received: from [128.131.2.110] (HELO mr.tuwien.ac.at) (128.131.2.110)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Nov 2005 12:19:16 -0800
Received: from [127.0.0.1] (chello062178078219.27.11.tuwien.teleweb.at
 [62.178.78.219])
	by mr.tuwien.ac.at (8.12.10/8.12.8) with ESMTP id jA3KIr7k004079
	for <dev@cocoon.apache.org>; Thu, 3 Nov 2005 21:18:55 +0100 (MET)
Message-ID: <436A70AD.6080805@student.tuwien.ac.at>
Date: Thu, 03 Nov 2005 21:18:53 +0100
From: Andreas Hochsteger <e9625392@student.tuwien.ac.at>
User-Agent: Thunderbird 1.4.1 (Windows/20051006)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: [M10N] new block layout
References: <dkd6q9$147$1@sea.gmane.org> <436A43A2.8050207@nada.kth.se>
In-Reply-To: <436A43A2.8050207@nada.kth.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-milter (http://amavis.org/)
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N


Daniel Fagerstrom wrote:
> Jorg Heymans wrote:
> 
>> A standard block layout can look like this :
>>
>> /cocoon-forms-block
>>     pom.xml
>>     /api
>>        pom.xml
>>     /impl
>>        pom.xml
>>     /samples
>>        pom.xml
>>
>>
>>  --> pom.xml
>> Is a multimodule pom containing
>>
>>  <modules>
>>    <module>api</module>
>>    <module>impl</module>
>>    <module>samples</module>
>>  </modules>
>>
>> as well as the dependencies for the block
>>    .....
>>    <dependency>
>>      <groupId>apache-cocoon</groupId>
>>      <artifactId>cocoon-ajax-impl</artifactId>
>>      <version>2.2-SNAPSHOT</version>
>>    </dependency>
>>    <dependency>
>>      <groupId>jakarta-oro</groupId>
>>      <artifactId>jakarta-oro</artifactId>
>>      <version>2.0.8</version>
>>    </dependency>
>>      .....
>>
>> Note: I'm not 100% sure yet about adding all dependencies at this level,
>> this still needs some thought. For now it will do.
>>  
>>
> Would prefer puting API dependencies in the API module and let the impl 
> depend on the api and the samples on the impl. Doesn't the tranistive 
> dependencies work well enough or what is the reasons for having 
> dependencies at parent level?

If you take everything into account, both API and implementation can 
have their own dependencies, e.g.:

* B (API) depends on A (API)
* C (impl of A) depends on A (API)
* D (impl of B) depends on B (API)
* D (impl of B) depends on C (impl of A)

or better readable with a bit of ASCII art:

API:  [ A ] <--- [ B ]
         ^          ^
         |          |
Impl: [ C ] <--- [ D ]

But as Daniel already mentioned, it looks good!

Andreas