Mailing-List: contact users-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Users List" <users@maven.apache.org>
Received-SPF: pass (athena.apache.org: domain of waynefay@gmail.com designates
 209.85.212.41 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <OF8B196574.8442E706-ONC1257902.00431F95-C1257902.00443A51@tolina.com>
References: 
 <OF8B196574.8442E706-ONC1257902.00431F95-C1257902.00443A51@tolina.com>
From: Wayne Fay <waynefay@gmail.com>
Date: Wed, 7 Sep 2011 11:27:14 -0500
Message-ID: 
 <CALy+7UnthGTvUtsjObOCNpT0uvbbtbOyPgqD8YcrTNTv7SKK+A@mail.gmail.com>
Subject: Re: Dependency resolution problem
To: Maven Users List <users@maven.apache.org>
Content-Type: text/plain; charset=UTF-8

> P -> A (1.1.0) -> B (2.1.0)
> P -> B (1.3.0)
>
> should cause a build failure, a setup like
>
> P -> A (1.1.0) -> B (1.5.0)
> P -> B (1.3.0)
>
> should not, but we have to guarantee, that B (1.5.0) is resolved, not B
> (1.3.0), which is not the standard maven dependency resolution.

Locking down versions of dependencies with [x.y] should get you at
least some of the way there. You should also be using pluginManagement
and dependencyManagement to specify versions of things in one place
(in the parent P) to avoid some of this in the first place. The
versions plugin may also be something that you should look at.

Wayne

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org