Force.com IDE Past Releases

This page contains information about previous releases of the Force.com IDE. For information about the latest release, visit the release notes for the latest Force.com IDE .

Contents


Spring '10 (v18)

The Spring '10 release of the Force.com IDE adds support for Eclipse 3.5 and updates for the latest Force.com platform features.


What's New

The Spring '10 release of the Force.com IDE contains the following major new features:

  • Eclipse 3.5 Support
    • Use the Force.com IDE with Eclipse Platform 3.5 (Galileo).
  • New Metadata Support in Spring '10
    • Business Processes
    • Entitlement Templates
    • Data Category Groups
    • Enhancements to Schema, Dashboards, Reports, Workflow and more, including Action Overrides, Lookup Filters, and List Views on Standard Objects.
    • For a complete list of metadata enhancements, see the Salesforce.com Winter '10 Release Notes and Spring '10 Release Notes.
  • Documentation and User Assistance
    • All documentation has been updated with Spring '10 content, including the new Force.com Workbook based on the Warehouse application.


Supported platforms

The Force.com IDE supports the following Salesforce editions, Eclipse versions and operating systems:

  • Salesforce
    • Developer Edition
    • Free Force.com Edition
    • Enterprise Edition
    • Unlimited Edition
  • Eclipse Platform
    • Version 3.5.2 "Galileo"
      • Mac OS X users should download the "Mac OS X (Carbon)" build of Eclipse 3.5. The Cocoa-based implementation of Eclipse 3.5 has stability issues and is not supported by the Force.com IDE.
    • Version 3.4.2 "Ganymede"
    • Version 3.3.x (3.3.1.1 or 3.3.2) "Europa"
  • Operating systems
    • Windows XP
    • Windows Vista
    • Mac OS X 10.4 (Tiger)
    • Mac OS X 10.5 (Leopard)
    • Ubuntu 8.04 LTS Desktop Edition 32-bit and 64-bit


Installation

Follow these installation instructions based on your version of the Eclipse Platform:


Major and Minor Releases

The following Spring '10 releases are available on the Force.com IDE update site:

  • Spring '10 Generally Available (18.0.0) - April 19, 2010


Notes and Known Issues

Upgrading to Spring '10

  • After upgrading to the Spring '10 plug-in, projects created in a Winter '09 or later IDE can be upgraded to Spring '10 using the Project Upgrade wizard.
  
Note
Force.com IDE releases prior to Winter '09 were non-upgradeable "Developer Preview" releases. To migrate to the latest Force.com IDE, delete all Force.com projects from your workspace and uninstall the older IDE plug-in from Eclipse, then install the latest release.


Working with Force.com Projects

  • To create a Force.com project against a Salesforce organization, the user must have a profile with the Customize Application and Modify All Data and permissions (typically held only by System Administrators).
  • When adding a Force.com Nature to projects not created with the New Force.com Project wizard, the IDE's src folder may cause conflicts with other project directory structures containing src. If you have name clash problems, rename the non-Force.com folders so they are unique, or remove the Force.com Nature from the project.
  • After changing the Apex Code log level marker under Force.com project properties, the UI does not reflect the value change, even though the value is saved correctly and Apex Code executes with the correct logging level.


Working with Apex Code

  • Code assistance does not support Apex annotations such as @isTest.
  • Code assistance does not support Dynamic Apex.
  • Code assistance does not support certain runtime properties, such as Visualforce page names as static properties of the Page class.
  • Apex Code Editor syntax highlighting is case-sensitive even though the Apex language is case-insensitive.


Working with Metadata Files

  • Some advanced IDE features, such as creation wizards and Show in Salesforce Web, are not available on all metadata components.
  • Removing a <fields> tag from a custom object does not actually remove the custom field on save. Instead, use the Salesforce Web interface to delete the field.
  • Deleting a custom object from the IDE does not remove any corresponding .layout or .workflow files, even though these components are deleted from the server. These files must be deleted separately.
  • Deleting a metadata file while in Work Offline mode never deletes the file from the server, but deletes the file locally.
  • To delete a project resource from the server, you must use the Package Explorer. Deleting files using the Navigator view or from the local file system does not delete the server-side component.
  • Modifying components inside installed managed packages, under the Referenced Packages folder, is not supported.
  • You cannot delete a folder that contains documents. As a workaround, use the Salesforce user interface to delete the documents. Then you can delete the folder in the IDE.


Server Synchronization

  • If a file changes outside of the IDE, Eclipse doesn't automatically refresh the content. This can happen if you are using an external source-control client when a file is synchronized or reverted. To see the changes in the IDE, you must refresh the file using Eclipse's Refresh for file system changes and "Refresh from Server" or "Synchronize with Server."
  • Saving a resource while the Synchronize View is open can falsely identify the resource as out of synchronization. Refreshing the Synchronize View removes the conflict.
  • If a packaged object has a sharing reason, doing a Refresh from Server on that file alone does not update the file. If this is an unpackaged object, or if you refresh the entire project, then the file with the sharing reason is updated.


Deployment

  • If the Deploy to Server wizard times out or is canceled while waiting for the server to complete a deployment, the server continues the deployment but you are not notified of the results. You can still view the metadata deployment results from a browser by navigating to Setup | Deploy | Monitor Deployments.
  • The Deploy to Server wizard cannot deploy to an organization containing two packages with the same name. In this case, the IDE shows the error "Duplicate packages are installed. Cannot make the deployment plan." If you have more than one package with the same name, you need to uninstall (or for local packages, rename) the duplicates.
  • The Deploy to Server wizard only allows deployment of metadata components that are enabled in the destination environment. Disabled components are excluded from the deployment plan.
  • A deployment archive (archive of destination environment) is not generated if the deployment plan only contains deletes.


Schema Explorer

  • A syntax error in a malformed SOQL query is highlighted by the caret (^) symbol. However, the caret highlighted location is not accurate in the error dialog. Locate the syntax error by column and row number, instead of the caret.
  • SOQL queries that return no results do so without an accompanying message. It may appear as if the query did not run, but in fact there are no returned rows.
  • Malformed queries may return the error, "Unable to open Schema Explorer." If you receive this message make sure your query is correct.


Other

  • Proxy servers using NTLM and digest authentication are not supported by Eclipse.
  • If you are working with large (> 2.5MB) component content, Eclipse needs at least 512MB of memory. See the Force.com IDE FAQ.
  • Features that interact with a browser (Show in Salesforce Web, Force.com IDE Start Page) require a default browser to be installed. If the standard wizard toolkit (SWT) crashes while opening an artifact (menu items, dialogs, etc.) and Mozilla Firefox is your default browser, ensure that you have installed the correct Mozilla Runtime Environment (MRE) for your Eclipse version (32-bit/64-bit).

Winter '10 (v17)

There is no Force.com IDE release for Winter '10.


Summer '09 (v16)

The Summer '09 release of the Force.com IDE adds support for Eclipse 3.4, updates for the latest Force.com metadata types, and the ability to upgrade existing projects created in Spring '09 or Winter '09.


What's New

The Summer '09 release of the Force.com IDE contains the following major new features:

  • Eclipse 3.4 Support
    • Use the Force.com IDE with Eclipse Platform 3.4 (Ganymede) and take advantage of the all the latest Eclipse features.
    • Installation of the Force.com IDE is a breeze with Eclipse P2 installer support, which finds and downloads required dependencies automatically.
  • New Metadata Support in Summer '09
    • Analytic Snapshots
    • Enhancements to Schema Objects, Apex, Visualforce, and more.
  • Summer '09 Upgrade Wizard
    • Seamlessly upgrade the contents of any Force.com project created in the Spring '09 (v15) or Winter '09 (v14) IDE.
    • Projects will not be upgraded until you are ready, but until you upgrade a project you will be unable to synchronize files with the server.
  • Documentation and User Assistance
    • All documentation has been updated with Summer '09 content.


Supported platforms

The Force.com IDE supports the following Salesforce editions, Eclipse versions and operating systems:

  • Salesforce
    • Developer Edition
    • Free Force.com Edition
    • Enterprise Edition
    • Unlimited Edition
  • Eclipse Platform
    • Version 3.4.2 "Ganymede"
    • Version 3.3.x (3.3.1.1 or 3.3.2) "Europa"
  • Operating systems
    • Windows XP
    • Windows Vista
    • Mac OS X 10.4 (Tiger)
    • Mac OS X 10.5 (Leopard)
    • Ubuntu 8.04 LTS Desktop Edition 32-bit and 64-bit
  
Note
Beginning with the Summer '09 release of the Force.com IDE, Eclipse 3.2 is no longer a supported platform.


Installation

Follow these installation instructions based on your version of the Eclipse Platform:

Note: The Force.com IDE is not compatible with Eclipse 3.5 ("Galileo").


Major and Minor Releases

The following Summer '09 releases are available on the Force.com IDE update site:

  • Summer '09 Generally Available (16.0.0) - June 15, 2009


Notes and Known Issues

Upgrading to Summer '09

  • Beginning with the Winter '09 IDE, there is a simple upgrade path to later releases. After upgrading to the Summer '09 plug-in, projects created in a Winter '09 or later IDE can be upgraded to Summer '09 using the Project Upgrade wizard.
  
Note
Force.com IDE releases prior to Winter '09 were non-upgradeable "Developer Preview" releases. To migrate to the latest Force.com IDE, delete all Force.com projects from your workspace and uninstall the older IDE plug-in from Eclipse, then install the latest release.


Working with Force.com Projects

  • To create a Force.com project against a Salesforce organization, the user must have a profile with the Customize Application and Modify All Data permissions (typically held only by System Administrators).
  • When adding a Force.com Nature to projects not created with the New Force.com Project wizard, the IDE's src folder may cause conflicts with other project directory structures containing src. If you have name clash problems, rename the non-Force.com folders so they are unique, or remove the Force.com Nature from the project.
  • After changing the Apex Code log level marker under Force.com project properties, the UI does not reflect the value change, even though the value is saved correctly and Apex Code executes with the correct logging level.


Working with Apex Code

  • Code assistance does not support Apex annotations such as @isTest.
  • Code assistance does not support Dynamic Apex.
  • Code assistance does not support certain runtime properties, such as Visualforce page names as static properties of the Page class.
  • Apex Code Editor syntax highlighting is case-sensitive even though the Apex language is case-insensitive.


Working with Metadata Files

  • Some advanced IDE features, such as creation wizards and Show in Salesforce Web, are not available on all metadata components.
  • Removing a <fields> tag from a custom object does not actually remove the custom field on save. Instead, use the Salesforce Web interface to delete the field.
  • Deleting a custom object from the IDE does not remove any corresponding .layout or .workflow files, even though these components are deleted from the server. These files must be deleted separately.
  • Deleting a metadata file while in Work Offline mode never deletes the file from the server, but deletes the file locally.
  • To delete a project resource from the server, you must use the Package Explorer. Deleting files using the Navigator view or from the local file system does not delete the server-side component.
  • Modifying components inside installed managed packages, under the Referenced Packages folder, is not supported.
  • You cannot delete a folder that contains documents. As a workaround, use the Salesforce user interface to delete the documents. Then you can delete the folder in the IDE.


Server Synchronization

  • If a file changes outside of the IDE, Eclipse doesn't automatically refresh the content. This can happen if you are using an external source-control client when a file is synchronized or reverted. To see the changes in the IDE, you must refresh the file using Eclipse's Refresh for file system changes and "Refresh from Server" or "Synchronize with Server."
  • Saving a resource while the Synchronize View is open can falsely identify the resource as out of synchronization. Refreshing the Synchronize View removes the conflict.
  • If a packaged object has a sharing reason, doing a Refresh from Server on that file alone does not update the file. If this is an unpackaged object, or if you refresh the entire project, then the file with the sharing reason is updated.


Deployment

  • If the Deploy to Server wizard times out or is canceled while waiting for the server to complete a deployment, the server continues the deployment but you are not notified of the results.
  • The Deploy to Server wizard cannot deploy to an organization containing two packages with the same name. In this case, the IDE shows the error "Duplicate packages are installed. Cannot make the deployment plan." If you have more than one package with the same name, you need to uninstall (or for local packages, rename) the duplicates.
  • The Deploy to Server wizard only allows deployment of metadata components that are enabled in the destination environment. Disabled components are excluded from the deployment plan.
  • A deployment archive (archive of destination environment) is not generated if the deployment plan only contains deletes.


Schema Explorer

  • A syntax error in a malformed SOQL query is highlighted by the caret (^) symbol. However, the caret highlighted location is not accurate in the error dialog. Locate the syntax error by column and row number, instead of the caret.
  • SOQL queries that return no results do so without an accompanying message. It may appear as if the query did not run, but in fact there are no returned rows.
  • Malformed queries may return the error, "Unable to open Schema Explorer." If you receive this message make sure your query is correct.


Other

  • Proxy servers using NTLM and digest authentication are not supported by Eclipse.
  • If you are working with large (> 2.5MB) component content, Eclipse needs at least 512MB of memory. See the Force.com IDE FAQ.
  • Features that interact with a browser (Show in Salesforce Web, Force.com IDE Start Page) require a default browser to be installed. If the standard wizard toolkit (SWT) crashes while opening an artifact (menu items, dialogs, etc.) and Mozilla Firefox is your default browser, ensure that you have installed the correct Mozilla Runtime Environment (MRE) for your Eclipse version (32-bit/64-bit).


Spring '09 (v15)

The Spring '09 release of the Force.com IDE brings powerful new Apex editing features, support for the latest metadata types, and the ability to upgrade existing projects created with the previous release.


What's New in Spring '09

The Spring '09 release of the Force.com IDE contains the following major new features:

  • Apex Editor Code Assistance
    • Code completion provides in-line suggestions for system classes, user defined classes, method variables and parameters, and schema objects and fields (just hit Ctrl+Space).
    • As you type, parse errors are underlined in red and marked next to the scrollbar.
    • Apex Class outline view updates in real time, even before you save changes.
  • New Metadata Support in Spring '09
    • Force.com Sites
    • Customer Portals
    • Partner Portals
    • Enhancements to Schema Objects, Profiles, and Reports
  • Spring '09 Upgrade Wizard
    • Seamlessly upgrade the contents of any Force.com project created in the Winter '09 (v14) IDE.
    • Projects will not be upgraded until you are ready, but until you upgrade a project you will be unable to synchronize files with the server.
  • Documentation and User Assistance
    • The Force.com IDE Library now includes the Force.com Web Services Developer's Guide, featuring everything you need to know about creating Web Service API clients and writing SOQL queries.
    • All other documentation has been updated with Spring '09 content.


Supported platforms

The Force.com IDE supports the following Eclipse versions and operating systems:

  • Eclipse Platform
    • Version 3.3.x (3.3.1.1 or 3.3.2) "Europa"
    • Version 3.2.2
  • Operating systems
    • Windows XP
    • Windows Vista
    • Mac OS X 10.4 (Tiger)
    • Mac OS X 10.5 (Leopard)
    • Ubuntu 8.04 LTS Desktop Edition 32-bit and 64-bit


Installation

Follow these installation instructions based on your version of the Eclipse Platform:

Note: The Spring '09 Force.com IDE is not compatible with Eclipse 3.4.


Major and Minor Releases

The following Spring '09 releases are available on the Force.com IDE update site:

  • Spring '09 Maintenance Release (15.0.2) - April 20, 2009
    • Resolves issue with missing components in Choose Metadata Components dialog, when connecting to an organization containing folders installed via a managed package.
    • Improves compatibility with some third party Eclipse plugins.
  • Spring '09 Maintenance Release (15.0.1) - March 24, 2009
    • Execute Anonymous now uses proxy settings on all platforms.
    • Erroneous validation warnings in the Visualforce Editor for <apex:*> and <c:*> tags are now disabled.
    • The Apex Editor no longer includes an extra curly brace.
    • The Apex Editor now includes assist suppport for:
      • Collection templates (for example, List<Account>)
      • Trigger.new and Trigger.old maps in Apex triggers
      • Public fields on Apex system classes (e.g. DMLOptions.assignmentRuleHeader)
      • Enums on Apex system classes (for example, ApexPages.Severity.ERROR)
  • Spring '09 Generally Available (15.0.0) - February 18, 2009


Notes and Known Issues

Upgrading to Spring '09

  • Beginning with the Winter '09 IDE, there is a simple upgrade path to later releases. After upgrading to the Spring '09 plug-in, projects created in the Winter '09 IDE can be upgraded to Spring '09 using the Project Upgrade wizard.
  
Note
Force.com IDE releases prior to Winter '09 were non-upgradeable "Developer Preview" releases. To migrate to the latest Force.com IDE, delete all Force.com projects from your workspace and uninstall the older IDE plug-in from Eclipse, then install the latest release.


Working with Force.com Projects

  • To create a Force.com project against a Salesforce organization, the user must have a profile with the Modify All Data permission (typically held only by System Administrators).
  • When adding a Force.com Nature to projects not created with the New Force.com Project wizard, the IDE's src folder may cause conflicts with other project directory structures containing src. If you have name clash problems, rename the non-Force.com folders so they are unique, or remove the Force.com Nature from the project.
  • After changing the Apex Code log level marker under Force.com project properties, the UI does not reflect the value change, even though the value is saved correctly and Apex Code executes with the correct logging level.


Working with Apex Code

  • Code assistance does not support Apex annotations such as @isTest.
  • Code assistance does not support Dynamic Apex.
  • Code assistance does not support certain runtime properties, such as Visualforce page names as static properties of the Page class.
  • Backward compatibility with Eclipse 3.2.2 forces Apex Code Editor syntax highlighting to be case-sensitive even though the Apex language is case-insensitive.


Working with Metadata Files

  • Some advanced IDE features, such as creation wizards and Show in Salesforce Web, are not available on all metadata components.
  • Removing a <fields> tag from a custom object does not actually remove the custom field on save. Instead, use the Salesforce Web interface to delete the field.
  • Deleting a custom object from the IDE does not remove any corresponding .layout or .workflow files, even though these components are deleted from the server. These files must be deleted separately.
  • Deleting a metadata file while in Work Offline mode never deletes the file from the server, but deletes the file locally.
  • To delete a project resource from the server, you must use the Package Explorer. Deleting files using the Navigator view or from the local file system does not delete the server-side component.
  • Modifying components inside installed managed packages, under the Referenced Packages folder, is not supported.
  • You cannot delete a folder that contains documents. As a workaround, use the Salesforce user interface to delete the documents. Then you can delete the folder in the IDE.


Server Synchronization

  • If a file changes outside of the IDE, Eclipse doesn't automatically refresh the content. This can happen if you are using an external source-control client when a file is synchronized or reverted. To see the changes in the IDE, you must refresh the file using Eclipse's Refresh for file system changes and "Refresh from Server" or "Synchronize with Server."
  • Saving a resource while the Synchronize View is open can falsely identify the resource as out of synchronization. Refreshing the Synchronize View removes the conflict.
  • If a packaged object has a sharing reason, doing a Refresh from Server on that file alone does not update the file. If this is an unpackaged object, or if you refresh the entire project, then the file with the sharing reason is updated.


Deployment

  • If the Deploy to Server wizard times out or is canceled while waiting for the server to complete a deployment, the server continues the deployment but you are not notified of the results.
  • The Deploy to Server wizard cannot deploy to an organization containing two packages with the same name. In this case, the IDE shows the error "Duplicate packages are installed. Cannot make the deployment plan." If you have more than one package with the same name, you need to uninstall (or for local packages, rename) the duplicates.
  • The Deploy to Server wizard only allows deployment of metadata components that are enabled in the destination environment. Disabled components are excluded from the deployment plan.
  • A deployment archive (archive of destination environment) is not generated if the deployment plan only contains deletes.


Schema Explorer

  • A syntax error in a malformed SOQL query is highlighted by the caret (^) symbol. However, the caret highlighted location is not accurate in the error dialog. Locate the syntax error by column and row number, instead of the caret.
  • SOQL queries that return no results do so without an accompanying message. It may appear as if the query did not run, but in fact there are no returned rows.
  • Malformed queries may return the error, "Unable to open Schema Explorer." If you receive this message make sure your query is correct.


Other

  • Proxy servers using NTLM and digest authentication are not supported by Eclipse.
  • If you are working with large (> 2.5MB) component content, Eclipse needs at least 512MB of memory. See the Force.com IDE FAQ.
  • Features that interact with a browser (Show in Salesforce Web, Force.com IDE Start Page) require a default browser to be installed. If the standard wizard toolkit (SWT) crashes while opening an artifact (menu items, dialogs, etc.) and Mozilla Firefox is your default browser, ensure that you have installed the correct Mozilla Runtime Environment (MRE) for your Eclipse version (32-bit/64-bit).


Winter '09 (v14)

Winter '09 marks the first supported release of the Force.com IDE! Customers with Developer Support are now able to contact salesforce.com's Global Support organization for help with their Force.com IDE questions. Help is also available from the developer community on the developer.force.com discussion boards.

This release is not backwards compatible with previous Developer Preview releases of the Force.com IDE. Force.com projects created in previous releases do not work with the Winter '09 Force.com IDE. First uninstall the previous version, then install the latest release.


What's New in Winter '09

The Winter '09 release of the Force.com IDE contains the following major new features:

  • Generally Available
    • The Force.com IDE is now GA. Support for this developer tool is available to customers who have purchased Developer Support.
    • The Force.com IDE Update Site has moved to http://www.adnsandbox.com/tools/ide/install/. Direct upgrades from previous releases are not supported.
  • New Metadata Support in Winter '09
    • Analytics: Dashboards, Reports, and Report Types
    • User Interface: Custom Labels, Localized Translations, Standard Tab and Field Renaming
    • Apex: Inbound Email Handler and Test Class
    • Schema: Dependent Picklist Fields, List Views, Custom Row Sharing Causes, and Web Links on Objects
    • Attachments: S-Controls and Email Templates
  • Metadata Component Directory
    • You can now populate projects from a list of available metadata components in your organization
    • You can add and remove components from existing projects
    • You can download new components automatically through subscriptions
  • Simpler Project Structure
    • Resources are no longer organized into package folders
    • Each metadata component exists in exactly one place in your project
    • Package-centric projects automatically download all components in a package
  • Documentation and User Assistance
    • Online help now includes the following manuals:
      • Force.com IDE: The help is expanded with over 40 new topics on how to use the IDE and develop Force.com applications.
      • Force.com Platform Tutorials: Ten new tutorials on how to use the Force.com Platform can get you started developing, testing, and deploying applications.
      • Apex Developer's Guide: This guide includes new Apex features, a new quick start tutorial, and additions for version 14.0 of the Force.com API.
      • Visualforce Developer's Guide: This guide includes everything you need to know about creating custom user interfaces as a service.
      • Metadata API Developer's Guide: This guide includes updated reference material for version 14.0 of the Force.com API metadata components.
      • Force.com Migration Tool Guide: This guide includes instructions for installing and using the Java/Ant-based scripting tool for custom or repetitive deployments.
    • Context-sensitive (F1) help covers every dialog, wizard, and action in the IDE.
  • Usability Enhancements
    • The Developer Start Page provides fast access to reference materials for the Force.com IDE and Platform, along with the latest news and sample projects from the developer.force.com online community.
    • There is no longer a time limit for the Deploy to Server wizard. When the project timeout limit is reached, users are prompted whether to continue or abort.
    • A Deploy to Server button is now included in the toolbar.
    • The Force.com IDE includes improved error handling and clearer error messages.
    • The Force.com context menu now contains quick shortcuts to add and remove metadata components and edit project properties.
    • The Force.com IDE Log Viewer lets users monitor events and diagnose problems in the IDE. Note that this feature is only available in Eclipse 3.3 or higher.


Supported platforms

The Force.com IDE supports the following Eclipse versions and operating systems:

  • Eclipse Platform
    • Version 3.3.x (3.3.1.1 or 3.3.2)
    • Version 3.2.2
  • Operating systems
    • Windows XP
    • Windows Vista
    • Mac OS X 10.4 (Tiger)
    • Mac OS X 10.5 (Leopard)
    • Ubuntu 8.04 LTS Desktop Edition 32-bit and 64-bit


Major and Minor Releases

The following Winter '09 releases are available on the Force.com IDE update site:

  • Winter '09 Maintenance Release (14.0.2) - December 11, 2008
    • Resolves Eclipse 3.2 compatibility issues for "Choose Metadata Components" dialog
    • Provides progress feedback when retrieving list of metadata components from server
    • Minor usability enhancements in Add/Remove Metadata Components
    • Improved error handling
  • Winter '09 Dreamforce Edition (14.0.1) - November 3, 2008
    • Adds documentation for new features announced at Dreamforce '08 to online help and the IDE start page:
      • Sites Tutorial and online help
      • Force.com Fundamentals
      • Developer’s Guide to the Force.com Platform
      • Force.com Cookbook
  • Winter '09 Generally Available (14.0.0) - October 27, 2008


Notes and Known Issues

Upgrading
The Winter '09 release is not backwards compatible with previous Developer Preview releases of the Force.com IDE.

  • Force.com projects created in previous releases do not work with the Winter '09 Force.com IDE. You must recreate your projects after installing the Winter '09 Force.com IDE. Users utilizing a version control system may need to recreate or restructure source files and folders in their repository as well.
  • You must uninstall or disable any previous releases of the Force.com IDE in your existing Eclipse environment before installing the Winter '09 Force.com IDE.
  • The Force.com IDE Update Site has moved to http://www.adnsandbox.com/tools/ide/install/

Connectivity

  • To create a Force.com project against a Salesforce organization, the user must have the Modify All Data permission (typically held only by System Administrators).
  • Proxy servers using NTLM and digest authentication are not supported by Eclipse.

Working with Metadata Files

  • Some advanced IDE features, such as creation wizards and Show in Salesforce Web, are not available on all metadata components.
  • Removing a <fields> tag from a custom object does not actually remove the custom field on save. Instead, use the Salesforce Web interface to delete the field.
  • Deleting a custom object from the IDE does not remove any corresponding .layout or .workflow files, even though these components are deleted from the server. These files must be deleted separately.
  • Deleting a metadata file while in Work Offline mode never deletes the file from the server, but deletes the file locally.
  • To delete a project resource from the server, you must use the Package Explorer. Deleting files using the Navigator view or from the local file system does not delete the server-side component.
  • Modifying components inside installed managed packages, under the Referenced Packages folder, is not supported.

Server Synchronization

  • If a file changes outside of the IDE, Eclipse doesn't automatically refresh the content. This can happen if you are using an external source-control client when a file is synchronized or reverted. To see the changes in the IDE, you must refresh the file using Eclipse's Refresh for file system changes and "Refresh from Server" or "Synchronize with Server."
  • Saving a resource while the Synchronize View is open can falsely identify the resource as out of synchronization. Refreshing the Synchronize View removes the conflict.
  • If a packaged object has a sharing reason, doing a Refresh from Server on that file alone does not update the file. If this is an unpackaged object, or if you refresh the entire project, then the file with the sharing reason is updated.

Deployment

  • If the Deploy to Server wizard times out or is canceled while waiting for the server to complete a deployment, the server continues the deployment but you are not notified of the results.
  • The Deploy to Server wizard cannot deploy to an organization containing two packages with the same name. In this case, the IDE shows the error "Duplicate packages are installed. Cannot make the deployment plan." If you have more than one package with the same name, you need to uninstall (or for local packages, rename) the duplicates.
  • The Deploy to Server wizard only allows deployment of metadata components that are enabled in the destination environment. Disabled components are excluded from the deployment plan.
  • A deployment archive (archive of destination environment) is not generated if the deployment plan only contains deletes.

Schema Explorer

  • A syntax error in a malformed SOQL query is highlighted by the caret (^) symbol. However, the caret highlighted location is not accurate in the error dialog. Locate the syntax error by column and row number, instead of the caret.
  • SOQL queries that return no results do so without an accompanying message. It may appear as if the query did not run, but in fact there are no returned rows.
  • Malformed queries may return an error of "Unable to open Schema Explorer." If you receive this message make sure your query is correct.

Eclipse Issues

  • When adding a Force.com Nature to projects not created with the New Force.com Project wizard, the IDE's src folder may cause conflicts with other project directory structures containing src. If you have name clash problems, rename the non-Force.com folders so they are unique, or remove the Force.com Nature from the project.
  • Backward compatibility with Eclipse 3.2.2 forces Apex Code Editor syntax highlighting to be case-sensitive even though the Apex language is case-insensitive.
  • Mozilla Runtime Environment (MRE) installation depends on the correct Eclipse version (32-bit/64-bit). If the standard wizard toolkit (SWT) crashes while opening an artifact (menu items, dialogs, etc.), then make sure that the required MRE exists.

Other

  • After changing the Apex Code log level marker under Force.com project properties, the UI does not reflect the value change, even though the value is saved correctly and Apex Code executes with the correct logging level.
  • If you are working with large (> 2.5MB) component content, Eclipse needs at least 512MB of memory. See the Force.com FAQ.
  • You cannot delete a folder that contains documents. As a workaround, use the Salesforce user interface to delete the documents. Then you can delete the folder in the IDE.
Retrieved from "http://wiki.developerforce.com/index.php/Force.com_IDE_Past_Releases"