Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Ready for our yearly final daze?

> Stephan Herrmann <stephan@xxxxxxxxxxxxxxx>
> Can anyone please explain in a few sentences:
> - what happens if a repo does not define this attribute?


If this attribute is not present, then all artifacts will be installed directly from your "main" repository and never consult any mirrors. When the "main" repository is saturated, such as near releases, this often means installs will fail. Also, for users far from North America, it means they are downloading from eclipse.org in Ottawa rather than a potentially much closer mirror.

> - how exactly should the value for this attribute be constructed?


The format is:

http://www.eclipse.org/downloads/download.php?file=<repository path>&format=xml

Where <repository path> is the path of your repository in the eclipse downloads directory. For example here is the URL from the Eclipse platform Helios release repository:

http://www.eclipse.org/downloads/download.php?file=/eclipse/updates/3.6/R-3.6-201006080911&format=xml


> It would be phantastic, if s.o. could actually give a hint on how to test
> whether it works :)

The best way to verify the URL is to paste it into the location bar of your web browser. You should get back an XML document with a non-empty list of mirrors.  You can paste the above URL from the Eclipse project in your browser to see an example of what this looks like.

John

Back to the top