# Eclipse updatesite
Tag | updatesite
Handle latest | yes
Handle publish | no
[since 2.3] This resolver is one of the resolvers which support OSGi™ dependencies. It resolves modules (OSGi bundles) which are hosted in an Eclipse™ update site. This resolver supports old style Eclipse updatesite, based on a single file, site.xml. It also supports Eclipse P2 repositories. ## Attributes This resolver shares the common attributes of composite resolvers.
Attribute | Description | Required
--- | --- | ---
url | the URL of the Eclipse updatesite | Yes
requirementStrategy | defines how strict should be the OSGi resolution. Can be one of `first` or `noambiguity` | No, default to `noambiguity`
metadataTtl | the time in milliseconds the updatesite metadata are considered up to date | No, default to 3600000 (1 hour)
forceMetadataUpdate | force the update of the updatesite metadata without checking their freshness | No, default to false
The requirement strategy is defining how the resolver should behave when facing several choices. In the OSGi dependency model, an `Import-Package` 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: if the requirement strategy is `first`, among the bundles satisfying the requirement, it will choose the first one. A warning will be logged about the choice Ivy has to arbitrarily do. if the requirement strategy is `noambiguity`, Ivy will make the resolution fail. ## Examples
    <updatesite name="ivyde-updatesite" url="http://www.apache.org/dist/ant/ivyde/updatesite"/>
A simple repository configured to load the Apache IvyDE Eclipse update site.