Return-Path: 
 <dev-return-94171-apmail-cocoon-dev-archive=cocoon.apache.org@cocoon.apache.org>
Delivered-To: apmail-cocoon-dev-archive@www.apache.org
Received: (qmail 12190 invoked from network); 10 Apr 2007 17:33:07 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 10 Apr 2007 17:33:06 -0000
Received: (qmail 54267 invoked by uid 500); 10 Apr 2007 17:33:13 -0000
Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org
Received: (qmail 53809 invoked by uid 500); 10 Apr 2007 17:33:11 -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 53798 invoked by uid 99); 10 Apr 2007 17:33:11 -0000
Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Apr 2007 10:33:11 -0700
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 (herse.apache.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; Tue, 10 Apr 2007 10:33:04 -0700
Received: from list by ciao.gmane.org with local (Exim 4.43)
	id 1HbKCw-0003gQ-NY
	for dev@cocoon.apache.org; Tue, 10 Apr 2007 19:32:42 +0200
Received: from d5153ca7c.access.telenet.be ([81.83.202.124])
        by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
        id 1AlnuQ-0007hv-00
        for <dev@cocoon.apache.org>; Tue, 10 Apr 2007 19:32:42 +0200
Received: from jheymans by d5153ca7c.access.telenet.be with local (Gmexim 0.1
 (Debian))
        id 1AlnuQ-0007hv-00
        for <dev@cocoon.apache.org>; Tue, 10 Apr 2007 19:32:42 +0200
X-Injected-Via-Gmane: http://gmane.org/
To: dev@cocoon.apache.org
From: Jorg Heymans <jheymans@apache.org>
Subject: Re: building trunk.
Date: Tue, 10 Apr 2007 19:32:41 +0200
Lines: 38
Message-ID: <evghni$cht$1@sea.gmane.org>
References: <4619E0E5.8000202@dslextreme.com>
 <4619EA81.2000106@dslextreme.com> <461A62C9.50103@apache.org>
 <461AF48D.5090203@dslextreme.com> <461B2EBF.3020801@apache.org>
 <461B393B.1070704@dslextreme.com> <461B3D27.5030706@apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Complaints-To: usenet@sea.gmane.org
X-Gmane-NNTP-Posting-Host: d5153ca7c.access.telenet.be
User-Agent: Thunderbird 2.0b2 (Macintosh/20070116)
In-Reply-To: <461B3D27.5030706@apache.org>
Sender: news <news@sea.gmane.org>
X-Virus-Checked: Checked by ClamAV on apache.org

Reinhard Poetz wrote:

> I'm asking because I don't understand who the customers of creating a 
> <dependencyMangement> section in Cocoon are? Is it the Cocoon project 
> alone or also all projects that use Cocoon?

AFAICT dependencyManagement does not come into play unless you're 
inheriting from the pom that declares it, so it would be only useful to 
us internally.

> 
> In the first case I doubt that there is much value in doing all this 
> work as long as the build runs through, isn't it?

Agreed.

> Or is the idea  that the user looks into our released parent pom and 
> copies our <dependencyMangement> section into his own project or even 
> inherits from our root pom?

I don't think any of these options is desired. Our main goal should be 
to keep our own dependency tree as clean as possible, ie <exclude> 
transitive dependencies in 3rd party libs that are clearly 
wrong/optional etc.

In any case, why wouldn't maven apply proper dependency resolution and 
selection when presented with multiple versions of the same artifact ?

Example: say i have a webapp pom that includes
- cocoon-core (which has CL 1.1)
- cocoon-thread-impl (which has CL 1.0.4)

then maven will just select CL 1.1 for inclusion, not both. If i however 
define in my webapp pom CL 1.0.4 then it will select only that.


Regards,
Jorg