Page History

...

In the site.xml file, the file describing the mirrors is declared by the mirrorsURL.
The IvyDE Eclipse mirror configuration is there: http://ant.apache.org/ivy/ivyde/updatesite/eclipse-update--xml.cgi^{Image Removed}
It declares that the plugins are also available on other updasite. Actually, Eclipse consider that the entire updatesite is mirrored. The only files that doesn't need to be mirrored is the mirrors configuration.

...

The update site is deployed in two places.There is the antry point, the URL the end users write in their Eclipse configurationon the Apache dist servers which are automatically mirrored. So the end user url for the updatesite is: http://antwww.apache.org/ivydist/ant/ivyde/updatesite^{Image Removed}
In that updatesite is only maintained the mirror configuration file, and the files that allows Eclipse to boot the updater:

...

Only one file is hosted on the website. It is the file that declare the Apache mirrors: http://ant.apache.org/ivy/ivyde/updatesite/eclipse-update--xml.cgi

...

Eclipse behaviour:

1. Eclipse get the site.xml for the www.apache.org/dist server
2. Eclipse then get the list of the mirrors via http://

...

1. ant.apache.org/

...

1. ivy/ivyde/updatesite/

...

1. eclipse-update--xml.cgi
2. Eclipse

...

1. 3.2 and 3.3

...

1. present then a list of mirrors to the end user.

...

1. Eclipse 3.4 and 3.5 is selecting one without asking
2. Then every operation will be done on the selected mirror, downloading the digest.zip, the jars, etc...