No, closest in the dependency graph means that the deepest dep is overriden
If A -> B -> C1.0 and A -> C2.0
then C2.0 wins because id closer to your project (A)
On 2/28/06, Ralph Goers <[EMAIL PROTECTED]> wrote:
> Carlos Sanchez said:
> > To be clear:
> > You never have two artifacts in the classpath with same
> > groupId:artifactId, maven uses the "nearer" version always, which is
> > the one closest to your project in the transitive dependency graph,
> > not the most recent version.
>
> Is that the same as saying it uses the first one it happens to run across?
> If dependencies are reordered in the parent could that cause a change in
> which version is used?
>
> Of course, this can't guarantee that two projects built separately with
> maven will actually use the same dependencies, which is really where the
> problem stems from.
>
> Ralph
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
