ECF Downloads

[new] ECF 2.0.0M7a now available (5/11/2008).

NOTE: For Eclipse 3.4M6 and later it is necessary to use a distinct update site. See ECF Install via Update Site below.

If you are using Eclipse 3.3 or Eclipse 3.4M1-M5, please use the ECF Install via Update Site -- version 2.0.0M5 install below.

Note that ECF 2.0.0 requires Eclipse 3.3 or newer (3.3 or 3.4 streams). See here to get appropriate version of Eclipse.

See New and Noteworthy for details of the contents of this release.

See ECF Wiki for further information about plans, sub-projects, meetings, etc.

ECF Install via Update Site -- for use with Eclipse Platform 3.4M6 or later

NOTE: For Eclipse 3.4M6 and greater, you must use this update site and not any of the other update sites given below. The reason for this is that in Eclipse M6 a new install/update mechanism was introduced, and a long with it four bundles from ECF are included. This makes it necessary for us to distribute only the ECF bundles that are not included with the platform, and so the rest of ECF for M6 must be made available via this update site.

  • In Eclipse M6, choose Help -> Software Updates...
  • Click on Available Features tab.
  • Click on Manage Sites... button.
  • Drag and drop the following URL from your browser to the list in the Manage Sites window:

    http://download.eclipse.org/technology/ecf/2.0/3.4/updateSite/site.xml

  • As a result of the drag and drop, you should see the above URL appear as an update site in the list.
  • Click OK in the Manage Sites window
    • .
  • You should see the Eclipse Communication Framework (ECF) category in the Available Features window.
  • Open the category and select the two ECF features.
  • Click Install...
  • Follow through remaining dialogs to complete install.

ECF Install via Zip -- for use with Eclipse Platform 3.4M6 or later

ECF Install via Update Site -- for use with Eclipse Platform from 3.3.0 to 3.4M5

For detailed instructions on using the Eclipse install/update mechanism to install ECF see here. See below for quick install.

  • In Eclipse, choose Help -> Software Updates -> Find and Install...
  • Choose Search for New Features to Install -> Next
  • Choose New Remote Site

ECF Install via Update Site -- Daily Build. NOTE: The daily builds are not guaranteed to be stable.

Note that these daily updates only apply to versions of Eclipse 3.4M5 and below. For Eclipse 3.4M6 and above, follow the directions in "ECF Install via Update Site -- version 2.0.0M6" on this page.

For detailed instructions on using the Eclipse install/update mechanism to install ECF see here. See below for quick install.

  • In Eclipse, choose Help -> Software Updates -> Find and Install...
  • Choose Search for New Features to Install -> Next
  • Choose New Remote Site

ECF Install via Zip -- for use with Eclipse Platform from 3.3.0 to 3.4M5

  • The following files are the latest ECF Daily builds. If there is a change to the ECF code, a daily build is performed, and the zip files placed here for download. These zips are more recent than the released files, but not as thoroughly tested.

    Daily Builds      
    For daily downloads go to ECF Dailies  These downloads only apply to Eclipse 3.4M5 and below.

To install from zip files:
  • Close Eclipse (if running) and unzip into your Eclipse installation directory (e.g. C:\eclipse)
  • Launch Eclipse
  • Problems? Check the FAQ and file a bug report.

ECF Source Code

For source code access to all ECF plugins, see the ECF developer resources page

ECF Extras Plugins at OSU Open Source Lab

ECF 'Extras' plugins are available via our site at the Oregon State University Open Source Lab.

ECF Build Types

[Adarrow] Releases
Releases are builds that have been declared major releases by the ECF development team - for example "R1.0". Releases are the right builds for people who want to be on a stable, tested release, and don't need the latest greatest features and improvements. Release builds always have an "R" at the beginning of the name i.e. R1.0, R2.0 etc. Non-release builds are named according to the date of the build - for example 20050710 is the build from July 10, 2005.
[Adarrow] Stable Builds
Stable builds are integration builds that have been found to be stable enough for most people to use. They are promoted from integration build to stable build by the architecture team after they have been used for a few days and deemed reasonably stable. The latest stable build is the right build for people who want to stay up to date with what is going on in the latest development stream, and don't mind putting up with a few problems in order to get the latest greatest features and bug fixes. The latest stable build is the one the development team likes people to be using, because of the valuable and timely feedback.
[Adarrow] Integration Builds
Periodically, component teams version off their work in what they believe is a stable, consistent state, and they update the build configuration to indicate that the next integration build should take this version of the component. Integration builds are built from these stable component versions that have been specified by each component team as the best version available. Integration builds may be promoted to stable builds after a few days of testing. Integration builds are built whenever new stable component versions are released into the build.
[Adarrow] Nightly Builds
Nightly builds are produced over night from whatever has been released into the HEAD stream of the CVS repository. They are completely untested and will almost always have major problems. Many will not work at all. These drops are normally only useful to developers actually working on the ECF project.

Note: Nightly builds are produced only as requested, and not necessarily every night, by developers to build what was in HEAD.
[Adarrow] Maintenance Builds
Periodically builds for maintenance of the current release will be performed. They will not necessarily be stable builds. When the maintenace is finalized and released, it will be moved up to a Release build. If the build name starts with an "M" i.e. M200500810,then it has not been tested for stability. If it is a release candidate, i.e. 0.5.0.1RC1, then it is a stable maintenance build.