Eclipse updatesite

Handle latestyes
Handle publishno
since 2.3 This resolver is one of the resolver which supports OSGi™ 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.


This resolver shares the common attributes of composite resolvers.
urlthe URL of the Eclipse updatesite Yes
requirementStrategydefines how strict should be the OSGi resolution. Can be one of first or noambiguity No, default to noambiguity
metadataTtlthe time in milliseconds the updatesite metadata are considered up to date No, default to 3600000 (1 hour)
forceMetadataUpdateforce the update of the updatesite metadata without checking their freshness No, default to false
The requirement strategy is defining how the resolver should behave in front of 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 statifying the requirement, it will shoose the first one. A warn will be logged ahout the choice Ivy has to arbitrarily do.
  • if the requirement strategy is noambiguity, Ivy will make the resolution fail.


<updatesite name="ivyde-updatesite" url="" />
A simple repository configured to load the Apache IvyDE Eclipse update site.