You are viewing a plain text version of this content. The canonical link for it is here.
Posted to site-commits@maven.apache.org by bu...@apache.org on 2015/03/22 17:23:43 UTC
svn commit: r944677 - in /websites/staging/maven/trunk/content: ./
maven-site-1.0-site.jar pom.html
Author: buildbot
Date: Sun Mar 22 16:23:43 2015
New Revision: 944677
Log:
Staging update by buildbot for maven
Modified:
websites/staging/maven/trunk/content/ (props changed)
websites/staging/maven/trunk/content/maven-site-1.0-site.jar
websites/staging/maven/trunk/content/pom.html
Propchange: websites/staging/maven/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sun Mar 22 16:23:43 2015
@@ -1 +1 @@
-1668400
+1668402
Modified: websites/staging/maven/trunk/content/maven-site-1.0-site.jar
==============================================================================
Binary files - no diff available.
Modified: websites/staging/maven/trunk/content/pom.html
==============================================================================
--- websites/staging/maven/trunk/content/pom.html (original)
+++ websites/staging/maven/trunk/content/pom.html Sun Mar 22 16:23:43 2015
@@ -279,7 +279,7 @@ Karl Heinz Marbaise" />
<ol style="list-style-type: decimal">
<li><a href="#Dependencies">Dependencies</a>
<ol style="list-style-type: decimal">
-<li><a href="#Dependency_Version_Specification">Dependency Version Specification</a></li>
+<li><a href="#Dependency_Version_Requirement_Specification">Dependency Version Requirement Specification</a></li>
<li><a href="#Exclusions">Exclusions</a></li></ol></li>
<li><a href="#Inheritance">Inheritance</a>
<ol style="list-style-type: decimal">
@@ -447,7 +447,7 @@ Karl Heinz Marbaise" />
<li><b>groupId</b>, <b>artifactId</b>, <b>version</b>:<br />You will see these elements often. This trinity is used to compute the Maven coordinate of a specific project in time, demarcating it as a dependency of this project. The purpose of this computation is to select a version that matches all the dependency declarations (due to transitive dependencies, there can be multiple dependency declarations for the same artifact). The values should be:
<ul>
<li><b>groupId</b>, <b>artifactId</b>: directly the corresponding coordinates of the dependency,</li>
-<li><b>version</b>: a <b>dependency version specification</b>, ie requirement, that will be used to compute the dependency's effective version.</li></ul>
+<li><b>version</b>: a <b>dependency version requirement specification</b>, that will be used to compute the dependency's effective version.</li></ul>
<p>Since the dependency is described by Maven coordinates, you may be thinking: "This means that my project can only depend upon Maven artifacts!" The answer is, "Of course, but that's a good thing." This forces you to depend solely on dependencies that Maven can manage. There are times, unfortunately, when a project cannot be downloaded from the central Maven repository. For example, a project may depend upon a jar that has a closed-source license which prevents it from being in a central repository. There are three methods for dealing with this scenario.</p>
<ol style="list-style-type: decimal">
<li>Install the dependency locally using the install plugin. The method is the simplest recommended method. For example:
@@ -471,8 +471,8 @@ Karl Heinz Marbaise" />
<li><b>optional</b>:<br />Marks optional a dependency when this project itself is a dependency. Confused? For example, imagine a project <tt>A</tt> that depends upon project <tt>B</tt> to compile a portion of code that may not be used at runtime, then we may have no need for project <tt>B</tt> for all project. So if project <tt>X</tt> adds project <tt>A</tt> as its own dependency, then Maven will not need to install project <tt>B</tt> at all. Symbolically, if <tt>=></tt> represents a required dependency, and <tt>--></tt> represents optional, although <tt>A=>B</tt> may be the case when building A <tt>X=>A-->B</tt> would be the case when building <tt>X</tt>.
<p>In the shortest terms, <tt>optional</tt> lets other projects know that, when you use this project, you do not require this dependency in order to work correctly.</p></li></ul>
<div class="section">
-<h5><a name="Dependency_Version_Specification">Dependency Version Specification</a></h5>
-<p>Version specifications used for dependencies' <tt>version</tt> element have the following syntax:</p>
+<h5><a name="Dependency_Version_Requirement_Specification">Dependency Version Requirement Specification</a></h5>
+<p>Dependencies' <tt>version</tt> element define version requirements, used to compute effective dependency version. Version requirements have the following syntax:</p>
<ul>
<li><tt>1.0</tt>: "Soft" requirement on 1.0 (just a recommendation, if it matches all other ranges for the dependency)</li>
<li><tt>[1.0]</tt>: "Hard" requirement on 1.0</li>