Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Received-SPF: pass (athena.apache.org: domain of elecharny@gmail.com
 designates 209.85.219.212 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:content-type:content-transfer-encoding;
        b=xaXXM7N+se1N7v0xnVwRamcjxuIaQl7oUXRe5l4bnLrQpLA+3roIt2iD7kdjzFnbaL
         f8uzYRYonnZmLOOvbvEOW8ZLA5z/6oBAmNoHQx+tXTurEvYx/8OTrSK8LuJuHhUtT+6j
         5xKHwh+/0aEm5bC2B6ZOWkRG/jUR1bOCR0MZo=
Message-ID: <4B48EE03.5060208@gmail.com>
Date: Sat, 09 Jan 2010 21:58:43 +0100
From: =?UTF-8?B?RW1tYW51ZWwgTMKOY2hhcm55?= <elecharny@gmail.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Apache Directory Developers List <dev@directory.apache.org>
Subject: Re: Dependency cleanup
References: <4B48E72A.8020004@apache.org>
In-Reply-To: <4B48E72A.8020004@apache.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

Stefan Seelmann a écrit :
> Hi,
>
> I'd like to cleanup the dependencies of shared and apacheds.
>
> 1st I think we should remove unused external dependencies.
>
> In apacheds each module defines its own dependencies to several shared 
> projects. I had the idea to create a "shared-all" module that 
> aggregates all shared modules and to use this single "shared-all" in 
> apacheds. We could add it as dependency to apachds parent pom and 
> remove all other dependencies to shared. At the end I think we use all 
> shared modules somewhere in apacheds, this would help to avoid lot of 
> dependency declarations.
At some point in the near future, we may want to see shared as a single 
jar (instead of having many of them). It makes totally sense to define 
such a module, as we did for apcheds-all sub-module, and not only to 
avoid those numerous dependencies to be included in the jars.

So  +1, absolutely.
>
> For internal dependencies I think it makes sense to use Mavens 
> transitive dependency resolution. E.g apacheds-core depends on 
> apacheds-api depends on apacheds-entry, in that case we can remove the 
> direct dependency apacheds-entry from apacheds-core.
I *think* we don't include too many transitive dependencies in the 
pom.xml files, AFAICT after having done some inversigation. But as we 
have around 50 sub-projetcs, I may perfectly be wrong.

In any case, +1 too.