Author: pgier
Date: Mon Feb 13 15:13:16 2012
New Revision: 1243555
URL: http://svn.apache.org/viewvc?rev=1243555&view=rev
Log:
[MENFORCER-128] Minor improvements to site doc for requireUpperBoundDeps.
Modified:
maven/enforcer/trunk/enforcer-rules/src/site/apt/requireUpperBoundDeps.apt.vm
Modified:
maven/enforcer/trunk/enforcer-rules/src/site/apt/requireUpperBoundDeps.apt.vm
URL:
http://svn.apache.org/viewvc/maven/enforcer/trunk/enforcer-rules/src/site/apt/requireUpperBoundDeps.apt.vm?rev=1243555&r1=1243554&r2=1243555&view=diff
==============================================================================
---
maven/enforcer/trunk/enforcer-rules/src/site/apt/requireUpperBoundDeps.apt.vm
(original)
+++
maven/enforcer/trunk/enforcer-rules/src/site/apt/requireUpperBoundDeps.apt.vm
Mon Feb 13 15:13:16 2012
@@ -16,14 +16,18 @@
~~ under the License.
-----
- Comparing against a specific artifact
+ Require Upper Bound Dependencies
-----
-----
2012-02-08
-----
- This rule requires that every dependency (including transitive dependencies)
is resolved to a version
- which is at least the specified version.
+ This rule requires that the version for each dependency resolved during a
build, is equal
+ to or higher than all transitive dependency declarations. The version of
each dependency
+ resolved during the build will normally be the version specified in the POM
or the
+ version with the least transitive steps (the "nearest" definition). For
more
+ information about Maven dependency resolution, see
+
{{{http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html}the
Maven site}}.
Here is a concrete example. This will cause a build to fail:
@@ -98,7 +102,7 @@ and
<id>enforce</id>
<configuration>
<rules>
- <RequireUpperBoundDeps/>
+ <requireUpperBoundDeps/>
</rules>
</configuration>
<goals>
