ECF Downloads

[new] ECF 3.1 Now Available (10/12/2009).

ECF 3.1 requires Eclipse 3.5 (Galileo) or newer. See here to get appropriate version of Eclipse. See New and Noteworthy for details of the contents of this release. See ECF Wiki and/or the ecf dev at eclipse.org mailing listfor further information about plans and ongoing project activities.

ECF 3.1 Install via P2 Repository -- for use with Eclipse 3.5/3.5.1

NOTE: For Eclipse 3.5/Galileo, you must use this update site and not the other update sites given below. These instructions have been tested with Eclipse 3.5 and 3.5.1.

  • In Eclipse 3.5/Galileo, choose Help -> Install New Software...
  • Click on the Add button.
  • Type in the following URL into the Location Textbox. For some versions of Eclipse, you can drag and drop the following URL from your browser to the Location textbox.
    http://download.eclipse.org/rt/ecf/3.1/3.5/repo
  • Type in a name in the Name textbox. For example, type ECF.
  • Click OK.
  • Select the Eclipse Communication Framework (ECF).
  • Click on Next.
  • Follow through the remaining dialog to complete the installation.

To uninstall ECF ...

  • Choose Help -> Install New Software...
  • Click on already installed
  • Click on Installed Software
  • Click on Eclipse Communication Framework (SDK)
  • Click on Uninstall ...

The method described above uses the new P2 update mechanism. Eclipse by default does not enable the classic update mechanism, but you can do that manually. To do so, go to Preferences .... On the Mac, this is under the Eclipse menu. Then, go to General -> Capabilities and click on Classic Update. Note, however, that this method does not automatically take care of prerequisites for you. If you use the classic method to install ECF on a freshly installed Eclipse, you will most likely get an error message that tells you what you must install before the ECF installation can be successful.

ECF 3.1 Install via Zip -- for use with Eclipse 3.5

  • The ECF SDK zip contains all ECF plugins from the Eclipse Foundation, as well as source code. The zip is a p2 update site. When you unzip it, you will have a local p2 update site.

    File    Build Date   
    org.eclipse.ecf.sdk-3.1.0.v20091012-1618.zip  10/12/2009

ECF Dailies

ECF 2.1 Install via Update Site -- for use with Eclipse 3.4

NOTE: For Eclipse 3.4/Ganymede, you must use this update site and not the other update sites given below.

  • In Eclipse 3.4/Ganymede, 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/rt/ecf/2.1/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 both the two ECF features.
  • Click Install...
  • Follow through remaining dialogs to complete install.

ECF 2.1 Install via Zip -- for use with Eclipse 3.4

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] 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 (sometimes over day, depending on your time zone) from whatever has been released into the HEAD stream of the CVS repository. They are completely untested and may have major problems. They may not work at all. These drops are intended primarily for developers actually working on the ECF project.

Note: The goal is to produce nightly builds (also called dailies) every day, but there is no guarantee or commitment.
[Adarrow] Maintenance Builds
Periodically builds for maintenance of the current release will be performed. They will not necessarily be stable builds. When the maintenance 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.