ECF 3.0 Now Available (6/24/2009).
ECF 3.0 requires Eclipse 3.5RC2 or newer. See here to get
appropriate version of Eclipse. ECF UI requires parts or the SDK of EMF 2.2 or newer.
See New and Noteworthy for details of the contents of this release.
See ECF Wiki for further information about plans, sub-projects, project team meetings, etc.
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.5M7.
To uninstall ECF ...
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.
| File | Build Date |
|---|---|
| org.eclipse.ecf.sdk-3.0.0.v20090616-0832.zip | 6/24/2009 |
NOTE: For Eclipse 3.4/Ganymede, you must use this update site and not the other update sites given below.
http://download.eclipse.org/rt/ecf/2.1/3.4/updateSite/site.xml
| File | Build Date |
|---|---|
| org.eclipse.ecf.sdk-2.1.0.v20081224-1728.zip | 12/24/2008 |
| Daily Builds | |
|---|---|
| For 3.0 daily downloads go to ECF 3.0 Dailies | |
| For 2.1 daily downloads go to ECF 2.1 Dailies |
| Daily Update Sites | |
|---|---|
| The latest 3.0 daily update is at http://download.eclipse.org/rt/ecf/3.5dailies3.0-update/site.xml | |
| The latest 2.1 daily update is at http://download.eclipse.org/rt/ecf/3.4dailies2.1-update/site.xml |
For source code access to all ECF plugins, see the ECF developer resources page
ECF 'Extras' plugins are available via our site at the Oregon State University Open Source Lab.
|
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. |
|
|
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. |
|
|
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. |
|
|
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. |