<table class="resolver"> <tr><td class="title">Tag</td><td class="value">vfs</td></tr> <tr><td class="title">Handle latest</td><td class="value">depend on vfs capacity, usually yes</td></tr> <tr><td class="title">Handle publish</td><td class="value">depend on vfs capacity, usually yes</td></tr> </table> <br/> <span class="tagdoc" id="ivysettings.resolvers.vfs">This resolver is certainly the most capable, since it relies on <a href="http://jakarta.apache.org/commons/vfs/">Apache commons VFS</a>, which gives an uniform access to <a href="http://jakarta.apache.org/commons/vfs/filesystems.html">a good number of file systems</a>, including ftp, webdav, zip, ...</span> <span class="since">since 1.4</span> <i>Note: commons vfs has not released a stable version yet, hence Ivy relies on a nightly build. Stability should thus be considered carefully before using this resolver in a production environment</i> <h1>Attributes</h1> This resolver shares the <a href="../settings/resolvers.html#common">common attributes</a> of standard resolvers. <h1>Child elements</h1> <table class="ivy-children"> <thead> <tr><th class="ivy-chld">Element</th><th class="ivy-chld-desc">Description</th><th class="ivy-chld-card">Cardinality</th></tr> </thead> <tbody> <tr><td>ivy</td><td>defines a pattern for ivy files, using the pattern attribute</td> <td>0..n</td></tr> <tr><td>artifact</td><td>defines a pattern for artifacts, using the pattern attribute</td> <td>1..n</td></tr> </tbody> </table> <h1>Example</h1> <code type="xml"> <vfs name="vfs-resolver"> <ivy pattern="sftp://username:password@host/[organisation]/[module]/[revision]/ivy.xml" /> <artifact pattern="sftp://username:password@host/[organisation]/[module]/[revision]/[artifact].[ext]" /> </vfs> </code> Access ivy and artifacts files using sftp.