<table class="resolver"> <tr><td class="title">Tag</td><td class="value">url</td></tr> <tr><td class="title">Handle latest</td><td class="value">yes with http urls (and apache server) and with file urls, no with other urls</td></tr> <tr><td class="title">Handle publish</td><td class="value">yes with http urls whose destination supports publishing (as of Ivy 2.0)</td></tr> </table> <br/> <span class="tagdoc" id="ivysettings.resolvers.url">This resolver is one of the most generic, in fact most of the previous resolvers can be obtained by a particular configuration of this one.</span> Indeed it uses urls to find ivy files and artifacts. The urls it uses are defined through ivy and artifact children, each giving a pattern to find ivy files or artifacts. <strong>Limitation</strong>: in m2compatible mode, this resolver is not able list available organizations. It means some features like [[ant:repreport]] are not available. <h1>Attributes</h1> This resolver shares the <a href="../settings/resolvers.html#common">common attributes</a> of standard resolvers. <table class="ivy-attributes"> <thead> <tr><th class="ivy-att">Attribute</th><th class="ivy-att-desc">Description</th><th class="ivy-att-req">Required</th></tr> </thead> <tbody> <tr><td>m2compatible</td><td>True if this resolver should be maven2 compatible, false otherwise <span class="since">since 1.3</span></td> <td>No, defaults to false</td></tr> </tbody> </table> <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"> <url name="two-patterns-example"> <ivy pattern="http://ivyrep.mycompany.com/[module]/[revision]/ivy-[revision].xml" /> <artifact pattern="http://ivyrep.mycompany.com/[module]/[revision]/[artifact]-[revision].[ext]" /> <artifact pattern="http://ivyrep.mycompany.com/[module]/[revision]/[artifact].[ext]" /> </url> </code> Looks for ivy files in one place and for artifacts in two places: with or without revision in name (revision being already in the directory structure).