Author: brett
Date: Mon Aug 20 22:57:12 2007
New Revision: 567968
URL: http://svn.apache.org/viewvc?rev=567968&view=rev
Log:
[MNGSITE-22] update docs for dependency mediation
Submitted by: Herve Boutemy
Modified:
maven/site/trunk/src/site/apt/guides/introduction/introduction-to-dependency-mechanism.apt
Modified:
maven/site/trunk/src/site/apt/guides/introduction/introduction-to-dependency-mechanism.apt
URL:
http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/guides/introduction/introduction-to-dependency-mechanism.apt?rev=567968&r1=567967&r2=567968&view=diff
==============================================================================
---
maven/site/trunk/src/site/apt/guides/introduction/introduction-to-dependency-mechanism.apt
(original)
+++
maven/site/trunk/src/site/apt/guides/introduction/introduction-to-dependency-mechanism.apt
Mon Aug 20 22:57:12 2007
@@ -44,7 +44,8 @@
versions of an artifact are encountered. Currently, Maven 2.0 only
supports using the "nearest definition" which means
that it will use the version of the closest dependency to your project in
the tree of dependencies.
You can always guarantee a version by declaring it explicitly in your
project's POM.
- Note that if two dependency versions are at the same depth in the
dependency tree it's not defined which one will win.
+ Note that if two dependency versions are at the same depth in the
dependency tree, until Maven 2.0.4 it was not defined which one would win,
+ but since Maven 2.0.5 it's the order in the declaration that counts: the
first declaration wins.
* "nearest definition" means that the version used will be the closest
one to your project in the tree of dependencies,
eg. if dependencies for A, B, and C are defined as A -> B -> C -> D
2.0 and A -> E -> D 1.0,
