svn commit: r732105 - /ant/ivy/core/branches/2.0.0/doc/use/cachepath.html

[ma...@apache.org]

Author: maartenc
Date: Tue Jan  6 12:40:22 2009
New Revision: 732105

URL: http://svn.apache.org/viewvc?rev=732105&view=rev
Log:
Updated the comment about not using ivy:cachepath in order to make the build process more independent from Ivy. It gave the wrong impression that this task shouldn't be used.

Modified:
    ant/ivy/core/branches/2.0.0/doc/use/cachepath.html

Modified: ant/ivy/core/branches/2.0.0/doc/use/cachepath.html
URL: http://svn.apache.org/viewvc/ant/ivy/core/branches/2.0.0/doc/use/cachepath.html?rev=732105&r1=732104&r2=732105&view=diff
==============================================================================
--- ant/ivy/core/branches/2.0.0/doc/use/cachepath.html (original)
+++ ant/ivy/core/branches/2.0.0/doc/use/cachepath.html Tue Jan  6 12:40:22 2009
@@ -29,7 +29,7 @@
 
 This is a [[ant:postresolvetask post resolve task]], with all the behaviour and attributes common to all post resolve tasks.
 
-Please prefer the use of retrieve + standard ant path creation, which make your build more independent from ivy (once artifacts are properly retrieved, ivy is not required any more).
+If you want to make your build more independent from Ivy, you could consider using the [[ant:retrieve retrieve task]]. Once the artifacts are properly retrieved, you can use standard Ant path creation which makes Ivy not necessary any more.
 
 Built path is registered in ant with a given id, and can thus be used like any other ant path using refid.