Return-Path: 
 <dev-return-85838-apmail-cocoon-dev-archive=cocoon.apache.org@cocoon.apache.org>
Delivered-To: apmail-cocoon-dev-archive@www.apache.org
Received: (qmail 24095 invoked from network); 27 Mar 2006 16:29:09 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 27 Mar 2006 16:29:09 -0000
Received: (qmail 56036 invoked by uid 500); 27 Mar 2006 16:29:07 -0000
Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org
Received: (qmail 55758 invoked by uid 500); 27 Mar 2006 16:29:06 -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 55746 invoked by uid 99); 27 Mar 2006 16:29:06 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Mar 2006 08:29:06 -0800
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (asf.osuosl.org: domain of ap-cocoon-dev@m.gmane.org
 designates 80.91.229.2 as permitted sender)
Received: from [80.91.229.2] (HELO ciao.gmane.org) (80.91.229.2)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Mar 2006 08:29:05 -0800
Received: from list by ciao.gmane.org with local (Exim 4.43)
	id 1FNuZu-00061j-PU
	for dev@cocoon.apache.org; Mon, 27 Mar 2006 18:28:26 +0200
Received: from d51a5268a.access.telenet.be ([81.165.38.138])
        by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
        id 1AlnuQ-0007hv-00
        for <dev@cocoon.apache.org>; Mon, 27 Mar 2006 18:28:26 +0200
Received: from jh by d51a5268a.access.telenet.be with local (Gmexim 0.1
 (Debian))
        id 1AlnuQ-0007hv-00
        for <dev@cocoon.apache.org>; Mon, 27 Mar 2006 18:28:26 +0200
X-Injected-Via-Gmane: http://gmane.org/
To: dev@cocoon.apache.org
From: Jorg Heymans <jh@domek.be>
Subject: Re: Questions on cleaning up trunk
Date: Mon, 27 Mar 2006 18:28:49 +0200
Lines: 38
Message-ID: <e093qk$93q$1@sea.gmane.org>
References: <442796C3.3060308@apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Complaints-To: usenet@sea.gmane.org
X-Gmane-NNTP-Posting-Host: d51a5268a.access.telenet.be
User-Agent: Thunderbird 1.5 (Macintosh/20051201)
In-Reply-To: <442796C3.3060308@apache.org>
Sender: news <news@sea.gmane.org>
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N


Reinhard Poetz wrote:

> * What's the right version for cocoon-core dependencies: 2.2.0-SNAPSHOT
> or 2.2-SNAPSHOT?
> 
> 2.2.0-SNAPSHOT - we should use the 3-digits pattern IMO
>
+1

>   - Solution 3: Include them in cocoon-mocks/src/mock/java (possibly
> prefered, since it already exists?)

+1

Having a separate block level module just for a few mock classes is
overkill.

> If mocks are specific for a particular block, we should put the classes
> into a separate module. How do we express the dependency so that it
> compiles with the mocks but runs with the implementation?

<scope>provided</scope>


> * Copy/move status.xml
>   - There are some inconsistencies for the current new blocks
>   - Some are located in the parent block, some in the impl block
>   - Where should they be located?
>   - May there be more than one? e.g. for impl, sample, ...

Perhaps you could just keep them at the module level for now and split
them up later when the need arises (eg different implementations for one
block)


Regards
Jorg