<table class="resolver"> <tr><td class="title">Tag</td><td class="value">updatesite</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> <span class="since">since 2.3</span> <span class="tagdoc" id="ivysettings.resolvers.updatesite">This resolver is one of the resolver which supports <a href="../osgi.html">OSGi™</a> dependencies. It resolves modules (OSGi bundles) which are hosted in an Eclipse™ update site. This resolver supports old style Eclipse updatesite, based on simply a site.xml. It also supports Eclipse P2 repositories. <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>url</td><td>the URL of the Eclipse updatesite</td> <td>Yes</td></tr> <tr><td>requirementStrategy</td><td>defines how strict should be the OSGi resolution. Can be one of <tt>first</tt> or <tt>noambiguity</tt></td> <td>No, default to <tt>noambiguity</tt></td></tr> <tr><td>metadataTtl</td><td>the time in milliseconds the updatesite metadata are considered up to date</td> <td>No, default to 3600000 (1 hour)</td></tr> <tr><td>forceMetadataUpdate</td><td>force the update of the updatesite metadata without checking their freshness</td> <td>No, default to false</td></tr> </tbody> </table> The requirement strategy is defining how the resolver should behave in front of several choices. In the OSGi dependency model, an <tt>Import-Package</tt> requirement can be satisfied by several different bundles. So when resolving such requirement, Ivy will first look into the already resolved bundles if one provides that package. If it fails to find one, then two behaviours can occur: <ul> <li>if the requirement strategy is <tt>first</tt>, among the bundles statifying the requirement, it will shoose the first one. A warn will be logged ahout the choice Ivy has to arbitrarily do.</li> <li>if the requirement strategy is <tt>noambiguity</tt>, Ivy will make the resolution fail.</li> </ul> <h1>Examples</h1> <code type="xml"> <updatesite name="ivyde-updatesite" url="http://www.apache.org/dist/ant/ivyde/updatesite" /> </code> A simple repository configured to load the Apache IvyDE Eclipse update site.