<table class="resolver"> <tr><td class="title">Tag</td><td class="value">jar</td></tr> <tr><td class="title">Handle latest</td><td class="value">yes</td></tr> <tr><td class="title">Handle publish</td><td class="value">no</td></tr> </table><br/> <span class="since">since 2.3</span> <span class="tagdoc" id="ivysettings.resolvers.jar">This resolver uses a specified jar resolve ivy files and artifacts.</span> This kind of resolver helps the packaging of an entire repository. Since the entire "repository" jar is expected to be local at some point, the size of a such repository should be considered to be not too large if it is expected to be remote; hence the artifacts in a such repo should be little in size. The configuration of such a resolver is done via specifying the location of the jar, and through ivy and artifact patterns, indicating where ivy files and artifacts can be found in the jar. You can indicate a list of patterns which will be checked one after the other. Note that the patterns MUST NOT start with a slash. <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>file</td><td>the absolute path of the jar</td> <td>One of 'file' or 'url' is required</td></tr> <tr><td>url</td><td>the url of the jar</td> <td>One of 'file' or 'url' is required</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>Examples</h1> <code type="xml"> <jar name="my-local-jar-resolver" file="/home/me/myrepo.jar"> <ivy pattern="[organisation]/[module]/ivys/ivy-[revision].xml" /> <artifact pattern="[organisation]/[module]/[type]s/[artifact]-[revision].[type]" /> </jar> </code> A simple local jar repository. <hr /> <code type="xml"> <jar name="my-remote-jar-resolver" url="http://www.mywebsite.com/dist/myrepo.jar"> <ivy pattern="dir_in_jar/subdir_in_jar/[organisation]/[module]/ivys/ivy-[revision].xml" /> <ivy pattern="dir_in_jar/another_subdir_in_jar/[organisation]/[module]/ivys/ivy-[revision].xml" /> <artifact pattern="dir_in_jar/subdir_in_jar/[organisation]/[module]/[type]s/[artifact]-[revision].[type]" /> <artifact pattern="dir_in_jar/another_subdir_in_jar/[organisation]/[module]/[type]s/[artifact]-[revision].[type]" /> <artifact pattern="dir_in_jar/yet_another_subdir_in_jar/[organisation]/[module]/[type]s/[artifact]-[revision].[type]" /> </jar> </code> A remote jar repository with multiple ivy and artifact patterns, patterns pointing in some sub directories in the jar.