<table class="resolver"> <tr><td class="title">Tag</td><td class="value">chain</td></tr> <tr><td class="title">Handle latest</td><td class="value">depends on sub resolvers</td></tr> <tr><td class="title">Handle publish</td><td class="value">delegates to first sub resolver in chain</td></tr> </table> <span class="tagdoc" id="ivysettings.resolvers.chain">This resolver is only a container of a chain of other resolvers.</span> The sub resolvers can be any resolver, including a chain. An attribute enable to indicate if the chain must be iterated after the first found or not (at least when asking for a latest revision). If the chain is iterated, then it's the latest among the ones found that is returned. If the chain is not iterated, then it's the first found which is returned. <h1>Attributes</h1> This resolver shares the <a href="../settings/resolvers.html#common">common attributes</a> of composite 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>returnFirst</td><td>true if the first found should be returned.</td> <td>No, defaults to false</td></tr> <tr><td>dual</td><td>true if the chain should behave like a dual chain. <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>any resolver</td><td>a sub resolver to use</td> <td>1..n</td></tr> </tbody> </table> <h1>Examples</h1> <code type="xml"> <chain name="test"> <filesystem name="1"> <ivy pattern="${ivy.settings.dir}/1/[organisation]/[module]/ivys/ivy-[revision].xml"/> <artifact pattern="${ivy.settings.dir}/1/[organisation]/[module]/[type]s/[artifact]-[revision].[ext]"/> </filesystem> <ivyrep name="2"/> </chain> </code> Both a filesystem and ivyrep will be used to look for ivy files. If a dynamic revision is required, then both the filesystem and ivyrep will be queried to find the most recent revision among the two resolvers. Once the most recent revision is found in one resolver, it's the same resolver which will be used to download artifacts. <hr/> <code type="xml"> <chain name="test" returnFirst="true"> <filesystem name="1"> <ivy pattern="${ivy.settings.dir}/1/[organisation]/[module]/ivys/ivy-[revision].xml"/> <artifact pattern="${ivy.settings.dir}/1/[organisation]/[module]/[type]s/[artifact]-[revision].[ext]"/> </filesystem> <ivyrep name="2"/> </chain> </code> Same as before, except that if a revision is found in the filesystem then ivyrep will not be queried: its the filesystem which will be used for both the ivy file and the artifacts. <hr/> <code type="xml"> <chain name="test" dual="true"> <filesystem name="1"> <ivy pattern="${ivy.settings.dir}/1/[organisation]/[module]/ivys/ivy-[revision].xml"/> <artifact pattern="${ivy.settings.dir}/1/[organisation]/[module]/[type]s/[artifact]-[revision].[ext]"/> </filesystem> <ivyrep name="2"/> </chain> </code> Same as first example, except that once a module is found by either filesystem or ivyrep, then it's the whole chain which will be queried to download the artifacts. So in this case ivy file and artifacts may be split across the two resolvers for the same module.