This site contains information about the artifacts created by the Eclipse project.
The Eclispe project also publish unreleased versions of its artifacts. Committers and early adopters, look below for unversioned repositories.
Eclipse Project builds are stored in p2 repositories that are produced as part of the Eclipse project build process. This page provides an overview of the different repositories maintained by the Eclipse project, and their corresponding location and retention policy. See also meaning of kinds of builds.
See Adding a new software site for instructions on how to add a new update site to your Eclipse installation.
The following is the list of actual and planned statble update sites for releases.
For the current development release you also find integration update sites, the following site points to the current integration update site:
Last 7-days I-builds are retained along with every weeks Monday's I-builds until a milestone is available; they will be removed once a milestone is available.
To be explicit, only about four integration builds are left in the composite I-build repository, even though the simple repositories are retained until the release is avail
Below are special composite repository URLs that are primarily intended for committers and early adopters. They are each a composite that simply points to the current version of the repositories listed below. Those using these non-versioned URL do not need to change their software repository lists or scripts. In other words, the contents are identical to their current, versioned counterparts, but the URL stays the same.
These repos go well together with the latest release train repo: http://download.eclipse.org/releases/latest
| Repository | Repository URL | Retention Policy |
|---|---|---|
| Current Integration builds | http://download.eclipse.org/eclipse/updates/I-builds | See above |
| Latest Release | https://download.eclipse.org/eclipse/updates/latest | See above |
p2's ability to provision complete products from repositories has made the concept of repositories a first-class citizen of the eclipse ecosystem. People can now use repositories during the build, at development time to setup their target and find missing bundles or simply to setup their IDE. Consequently, repository users expect the content of these repositories to be stable, and it is important to make the retention policy of each repository clearly available.
The following document describes the retention policy used by the Eclipse project:
- Release repositories: the repository contains all the metadata and artifact of a given release and no content is ever removed from it. When a new SR is made available the metadata and the artifacts are appended to the existing repository.
- Integration build repositories: content is expected to stay until the milestone is complete, but can be disposed at any time. They may be deleted but usually only if it is known to be a "bad" I-build (that is, will hurt something if installed).
- Nightly build repositories: content can be disposed at any time.
Though specific to the Eclipse platform team, these rules are general enough that we encourage any other team producing repositories to follow them.