Author: aheritier
Date: Mon Oct 31 15:33:14 2005
New Revision: 329932

URL: http://svn.apache.org/viewcvs?rev=329932&view=rev
Log:
PR: MAVEN-1720
Submitted by : Lukas Theussl
Reviewed by : Arnaud Heritier
Better documentation of SNAPSHOT dependencies, following confusion on the user 
list.

Modified:
    maven/maven-1/core/trunk/xdocs/using/managing-dependencies.xml

Modified: maven/maven-1/core/trunk/xdocs/using/managing-dependencies.xml
URL: 
http://svn.apache.org/viewcvs/maven/maven-1/core/trunk/xdocs/using/managing-dependencies.xml?rev=329932&r1=329931&r2=329932&view=diff
==============================================================================
--- maven/maven-1/core/trunk/xdocs/using/managing-dependencies.xml (original)
+++ maven/maven-1/core/trunk/xdocs/using/managing-dependencies.xml Mon Oct 31 
15:33:14 2005
@@ -115,7 +115,16 @@
         <p>
           Assuming that project is publishing a version called 
<code>SNAPSHOT</code> (which happens when the
           <code>jar:deploy-snapshot</code> goal is called), then each time you 
build Maven will check the remote
-          repository for changes in that JAR and download it again if a newer 
version is available.
+          repository for changes in that JAR and download it again if a newer 
<code>SNAPSHOT</code> is available.
+        </p>
+
+        <p>
+          <b>Note:</b> It seems to be a common misconception that Maven would
+          replace <code>SNAPSHOT</code> by the most current version of a 
project
+          that is available in the repository. This is not the case: using a
+          <code>SNAPSHOT</code> dependency requires that the project that you
+          depend on has actually published a <code>SNAPSHOT</code>,
+          and only this <code>SNAPSHOT</code> will get updated automatically.
         </p>
 
         <p>


Reply via email to